> 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 should be prequalified and routed purposefully. It collects relevant lead information, prioritizes inquiries, and ensures that prospects do not have to wait and that no sales opportunity is lost.

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

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

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

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

Create an agent and describe in **Company profile** (Configuration section) 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 about company size & industry"
  * Task: "Ask about timeframe for implementation"
  * Closing action: forward (to the sales hotline) or announce a callback (if you work asynchronously).
    {% endstep %}

{% step %}
**Store knowledge**

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

* **Knowledge base:** Upload product brochures or price lists as 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 sales team's email address.
* **MCP connection:** Use MCP to pass qualified leads, including all recorded answers, directly to your CRM or connected systems.
* **Webhooks:** Alternatively, use webhooks if no MCP integration is available.
  {% endstep %}

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

To get started, you will receive a phone number for 7 days, via which your agent can be reached immediately. After that, port your existing phone number to sipgate or book a free phone number. The free phone number is not automatically in your account; you book it manually under **Phone numbers**.
{% endstep %}
{% endstepper %}

**Benefits at a glance**

Your sales team is relieved and can focus on already qualified inquiries instead of spending time on initial conversations and preliminary clarification. 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sipgate.com/documentation/en/use-cases/sales-teams.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
