> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/crm/crm-common-questions/mirroring-customer-service-in-crm.md).

# Mirroring Customer Service in CRM

In this tutorial, we will demonstrate how to structure the mirroring between the operational stages of Customer Service (SAC) and the stages of the CRM funnel, enabling a continuous flow of data and actions between support and sales.\
This setup enables integrated customer relationship management, makes it easier to visualize the full interaction cycle, and enables strategic automations based on shared statuses.

This video is ideal for teams seeking standardization between support and CRM platforms, or wanting to scale operations based on consistent data and consolidated historical records.\
\
Check out the video below:

{% embed url="<https://youtu.be/jgjQEsXvEMQ>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/general/crm/crm-common-questions/mirroring-customer-service-in-crm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.