> 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/sac-360/sac-360-tutorial-videos/sac-360-automation-starting-service-always-for-the-same-attendant-salesperson-in-sprinthub.md).

# SAC 360° Automation - Starting Service always for the same Attendant/Salesperson in SprintHub

Have you ever had the problem of a Lead being assigned to a salesperson, that salesperson closing the sale, and then when this customer comes back some time later, they end up being assigned to another salesperson? This is frustrating for the salesperson who managed to win over the customer and close the first sale. With this method, you will define an “OWNER” for the Lead and every time this Lead gets in touch, it will always be assigned to this owner.

{% embed url="<https://www.youtube.com/watch?v=b2EjNvGIXRc>" %}


---

# 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/sac-360/sac-360-tutorial-videos/sac-360-automation-starting-service-always-for-the-same-attendant-salesperson-in-sprinthub.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.