Branching Call Scripts with the Script Diagram in Call
How to draw a call script as steps and branches in Call, plan answers, check before saving, restore old versions and keep every place that uses it in step.
Text scripts are fine for short, linear calls. But real conversations branch. The customer says yes, or no, or "not now", or asks something unexpected. A paragraph of text hides those branches; a diagram puts them in front of you. That makes gaps visible: the question with no answer, the objection with no reply, the path that never reaches an ending.

This guide explains when to use a diagram, how to build one in Call, how to check and save it safely, and how to keep it healthy over time. Start with Writing and Using Call Scripts in Call if you are new to scripts, and see Mapping Your IVR as a Flow Before You Build It for a similar discipline applied to phone menus.
When a diagram beats text
Choose a diagram when
- The call branchesThe next step depends on the answer.
- Several people editA picture makes changes easy to review.
- An AI agent follows itClear steps and branches give the agent structure to follow.
- You need to spot gapsDead ends and missing endings show up immediately.
For a short reminder call, text is quicker. For a lead-qualification call with five possible outcomes, a diagram is clearer.
The building blocks
A diagram is made of steps joined by connections. Each step has a type, and choosing the right type is most of the craft.
| Step | What it does |
|---|---|
| Greeting | Where the call starts |
| Question | Something the agent asks |
| Branch on answer | Splits the call by the answer, with each answer named on its way out |
| Answer from knowledge | The agent answers from your knowledge base |
| Objection | How to handle a pushback, such as no time |
| Transfer | Puts the caller through to one of your lines |
| Voicemail | What happens on voicemail |
| End | Ends the call, with a result code |
Each end step carries a result code, which becomes the outcome you report on. Plan the codes first; they decide what you can measure.
Building a diagram in Call
Drawing the flow
- Open itIn Campaigns, then Scripts, press Diagram on a script, or New diagram.
- Add stepsUse Add step, or Add a next step in the side panel. Double-click a step to edit what the agent says.
- Connect themDrag from the lower dot of one step to another, or use Connect to.
- Name the answersOn a Branch on answer step, label each way out, for example yes or not interested.
Press Auto-layout to line the steps up from top to bottom. Undo and Redo take back any change. You can also use the keyboard: Tab to a step, Enter or Space to select it, arrow keys to move it, Delete to remove it, Escape to cancel. On a phone, the diagram appears as a numbered list of steps with their answers; tap a step to edit.
Limits to know
- A diagram holds up to sixty steps and one hundred fifty connections.
- Each step's text can be up to six hundred characters.
- The agent says each step in its own words; the diagram is guidance, not a recording.
- Saving changes this workspace only.
Drafting with AI, and call types
Built by AI can draft a diagram. It starts by asking what kind of call the script is for, then offers a short interview about your business. It uses your agent's profile, knowledge base, products and hours; a fact it does not have is left out or marked Fill in, and calls skip a step marked that way until you fill it in. Nothing is saved until you press Save, and you can use or discard the draft.
Outbound types open with your business name, the caller as an AI assistant and the purpose, and have a refusal path that ends the call as do not call. Payment reminders, billing questions and bookings carry extra rules: no invented amounts, no payment taken on the call, and a booking is only ever a request a person confirms. Read what the draft says before you trust it.
Worked example: a lead-qualification branch
To see why diagrams help, imagine a hypothetical training provider qualifying leads who downloaded a brochure. The greeting names the provider and asks if it is a good moment. A question asks what the person is hoping to learn. A Branch on answer step then splits three ways: interested in a course, just browsing, or not interested.
- Interested: ask one follow-up about timing, then offer to pass the request to a person who will confirm details. End with a result code such as request taken.
- Just browsing: thank them, offer to send general information through their preferred channel, and end with a result code such as information only.
- Not interested: thank them, ask whether they would like to be left off future calls, and end with the matching code.
Drawn this way, the owner can see at once that all three paths end properly, that nobody is promised a booking, and that the refusal path exists. Add an objection step for "I am too busy" that offers a better time, and a Transfer step for callers who ask for a person. In text, those same ideas would be buried in paragraphs and easy to break during an edit.
A diagram also helps training. New starters can follow the paths with a finger, and a manager can ask "what happens if they say this?" and point to the answer. It turns a script from a document to be read into a map to be walked.
Checking and saving safely
Before saving, fix anything listed under Check before saving. Typical problems are steps with no way out, branches with unlabelled answers and endings with no result code. When you press Save, the confirmation lists every place that uses the script. Press Save and update all only if every one of them should change.
If one line or campaign needs different wording, split it off with Duplicate for this one only rather than editing the shared script. Calls already in progress keep the version they started with.
Review a diagram with someone who did not draw it. Ask them to trace three paths aloud: the happy path, a refusal and an unexpected answer. If they get lost, the diagram is too complicated, and it is better to split it into two scripts than to keep adding steps.
Versions and history
Open a script's diagram and press History to see every saved version. Press Compare to see what changed since a version. Press Restore, then Restore and update all, to bring an older version back. The restored version is saved again as the newest, and the versions in between are kept.
Diagram health check
- Every path reaches an End with a result code.
- Every Branch on answer has labelled ways out, including "something else".
- There is an objection step for the most common pushback.
- Outbound scripts include a path for someone who asks not to be called.
- A person has tested it with practice calls.
- The version history shows who changed what, and why.
Frequently asked questions
What is the script diagram?
It shows a call script as steps and branches that you can move, connect and edit, then save once for every line, agent and campaign that uses it.
How many steps can a diagram have?
Up to sixty steps and one hundred fifty connections, with each step's text up to six hundred characters.
Does the agent read the diagram word for word?
No. The agent says each step in its own words, so the diagram is guidance rather than a recording.
Can I undo a bad change?
Yes. Undo and Redo work while you edit, and History lets you compare and restore saved versions without deleting those in between.
What is the Fill in marker?
When built by AI lacks a fact, it marks the step Fill in. Calls skip such a step until you fill it in.
Who can draft with AI?
Only an owner, admin or manager can draft, and there is an hourly limit on drafts per organisation.