> For the complete documentation index, see [llms.txt](https://help.sipgate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.com/documentation/en/use-cases/sales-teams.md).

# Sales Teams

The agent for sales teams is suitable when incoming sales calls are to be prequalified and routed in a targeted way. It collects relevant lead information, prioritizes requests, and ensures that prospects do not have to wait and no sales opportunity is lost.

### **What exactly does the agent handle?**

The agent answers calls and clarifies the reason, such as product interest, price inquiry, or request for consultation. It collects relevant information such as contact details, areas of interest, or desired callback times. Depending on the outcome, it forwards qualified inquiries directly to the appropriate employees or announces a callback. After each conversation, all information is available in structured form, as a call log or by email. This allows the sales team to get started right away without follow-up questions.

### **Briefly explained: How to set up the use case**

{% stepper %}
{% step %}
**Create agent & refine profile**

Create an agent and describe in the **company profile** (configuration area) your products and your value proposition. The more precisely the agent knows what you sell, the better it can answer initial questions.
{% endstep %}

{% step %}
**Create qualification playbooks**

Under Playbooks, create guides to filter leads (prequalification). Define what information you need to assess the quality of a lead.

* **Playbook "New Prospect":**
  * Condition: "Caller is interested in product XY"
  * Task: "Ask for company size & industry"
  * Task: "Ask about the timeframe for implementation"
  * Closing action: transfer (to the sales hotline) or announce a callback (if you work asynchronously).
    {% endstep %}

{% step %}
**Store knowledge**

So that the agent not only asks, but also convinces, it needs information.

* **Knowledge base:** Upload product brochures or price lists as a PDF.
* **Customer questions:** Store answers to objections ("Why are you more expensive than provider X?") or detailed questions ("Is there an API?").
  {% endstep %}

{% step %}
**Notifications & CRM integration**

* **Email summary:** Enter under *Configuration > Recipients* the email address of the sales team.
* **MCP connection:** Use MCP to hand over qualified leads, including all captured answers, directly to your CRM or connected systems.
* **Webhooks:** Alternatively, use webhooks if no MCP connection is available.
  {% endstep %}

{% step %}
**Assign phone number**

During the test phase, you will receive free phone numbers from us for testing. But so that your agent can also be reached after the trial period, you still need to assign it a phone number.
{% endstep %}
{% endstepper %}

**Advantages at a glance**

Your sales team is relieved and can focus on already qualified inquiries instead of spending time on initial calls and preliminary clarifications. The structured capture makes it visible when and on which topics prospects call and which inquiries are particularly promising. This makes it possible to plan sales times better and improve processes in a targeted way.


---

# 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://help.sipgate.com/documentation/en/use-cases/sales-teams.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.