Playbooks
Playbooks define how your agent responds to specific concerns and which steps are carried out in the process. They are used when conversations should not only be answered, but handled in a targeted way, for example to capture information, check requests, or pass content on to your team.
This makes playbooks the basis for structured and automated conversation workflows.
What are playbooks used for?
Playbooks are suitable for requests where a clear, structured process is necessary:
Record callback requests with complete contact details
Document support or service requests in a structured way
Categorize and forward billing or contract questions
Capture appointment requests when no calendar integration is connected
A playbook consists of individual tasks. You define what the AI agent should do in the conversation:
Ask for information, for example customer numbers, contact details, or problem descriptions
Pass on instructions, for example instructions or information for callers
Map simple if-then workflows, for example ask an additional question depending on an answer
Highlight important details in the summary, so they are directly visible for follow-up processing
Tasks can be created as mandatory or optional. This allows the conversation flow to be tailored specifically to the respective request.
You can find more information under Summaries & Transcripts.
Playbooks from the library
In the library, you will find preconfigured playbooks from sipgate for common use cases, for example recording incident reports or retrieving orders. The library is continuously expanded.
The playbooks are already preconfigured and editable in parts:
Add your own information: Fill in the designated fields with your information.
Connect tools: Connect the required tools.
Triggers and workflow: These are fixed and cannot be changed.
You can find the library in the sidebar of the agent overview. Drag and drop the desired playbook onto your agent Drag and drop onto your agent.
No suitable playbook included? Then create your own.
Custom playbooks
You create a custom playbook from scratch and configure it completely yourself. You define how your agent handles a conversation:
Ask for information: For example customer numbers, problem descriptions, or contact options.
Confirm details: The agent confirms the captured information.
Pass on results: For example by email, webhook, or as a summary in the sipgate app.
Newly created playbooks are initially deactivated. Only after activation will your agent use them for suitable requests. Deactivated playbooks are ignored and do not need to be deleted.
How many playbooks you can create depends on your plan:
sipgate sona Free: Up to three playbooks.
All other plans: Unlimited playbooks.
Name and describe playbook
Title and description help your agent select the right playbook. Make both specific and clearly distinguish the topics from one another. Test the selection with different requests and adjust the details if necessary.
Set conditions
Define keywords, phrases, or specific requeststhat should trigger the playbook. Check regularly whether the conditions work and adjust them if necessary.
Use tasks
With tasks, you define what your agent should do in the conversation:
Ask for information, such as customer numbers or contact details.
Ask follow-up questions, if certain information is available. To do this, use optional tasks.
Provide hints and instructions.
Mark important tasks to highlight them in the conversation summary . More on this under Summaries & Transcripts.
Reference MCP tools in tasks
You can reference MCP tools in the instructions of a task. Type @ into the instruction field — a selection menu with the available tools will appear.
Select the desired tool. It appears under Linked tools in the task and is used by your agent in the conversation.

Connections
As soon as a playbook references an MCP tool, you can see under Connections in the playbook overview which tools are connected and whether the connection is active.
Connection interrupted: If an MCP server is no longer reachable, sipgate automatically deactivates all active playbooks that use tools from this server. Restore the MCP connection and then manually activate the playbook via Activate.
Define closing action
Choose a Forward to a phone number or a channel or a callback as the closing action.
Channels do not need their own routed phone number. In the analytics dashboard, you can see which channel was forwarded to.
Obtain the consent of callers through a task and, if necessary, define alternatives, such as ending the conversation if no callback is desired.
Interaction with knowledge and customer questions
Playbooks control the workflow. The knowledge base and the customer questions provide the information for your agent's answers.
Last updated

