Use this template
Use this pattern when callers contact a public support number to ask about one defined service. The agent should answer common questions, state rates carefully, and transfer callers who need a person. This is an Inbound Single Stage agent. It keeps stable instructions and a representative knowledge set in one prompt so you can see the complete pattern before adapting it to your organization.Text such as
[Company name] inside the prompt examples is a manual placeholder. Replace every square-bracketed placeholder before saving the agent. Runtime variables use double braces, such as {{transcript}}, and are filled by AgentCallback.Why this structure works
The role and scope appear before the knowledge content, so the agent knows when it should answer and when it should escalate. Pronunciation rules make phone numbers, email addresses, and service codes easier to understand over voice. A separate transfer section prevents the agent from promising a human handoff without calling the transfer tool. The FAQ and rate rows below are representative examples. Replace them with reviewed information and retest the agent whenever prices or policies change.Review variables
This template does not require pre-call variables. An inbound caller may be unknown when the call begins, and the agent can answer general questions without contact data. If your phone routing supplies trusted customer information before the call, add only the variables you need and explain how the agent may use them. Do not assume a caller’s identity from their phone number alone. This template also has no state variables. It does not collect structured information during the call.Configure tools
Add and enable the SIP cold transfer tool:
Store the real connection details only in the dashboard’s tool configuration. Never paste SIP credentials into the system prompt or public documentation.
The route’s
nameOverride exposes the tool to the agent as Transfer_to_support. Refer to that exposed name in the system prompt, not the underlying sipColdTransfer configuration name.
Define outcomes
Add these call outcomes. Keep the category names identical to the names in the evaluation prompt.Build the system prompt
Start by limiting the agent to one service and one trusted knowledge source:Add the conclusion prompt
Add the evaluation prompt
The evaluation prompt distinguishes a successful transfer from a call that merely needed escalation.Complete dashboard-ready template
Create an Inbound Single Stage agent, leave variables and state variables empty, add the transfer tool and outcomes above, then copy the following finished prompts.Configuration
Use the transfer settings from Configure tools and the category descriptions from Define outcomes when completing the dashboard configuration.