Library · Booking Scripts
Four booking scripts. One controlled source.
Organize inbound and outbound scripts for lead generation and database reactivation, adapt them by campaign Theme, and track every reviewable revision.
Already have a workspace? Sign in
- Plans from $99/month
- Built for multi-client agencies
- Your brand across the console
Library · Booking Scripts
AI booking agent script library for agencies
A booking agent needs more than one generic talk track. A new lead calling about an offer, a team following up with an inbound lead, and a reactivation call to an existing contact each need a different conversation. The Booking Scripts workspace in AI Marketing Dashboard keeps those scripts together as a complete, versioned set for every client and campaign Theme, so strategists, reviewers and clients can work from one controlled source instead of disconnected documents.
Draft to client
Four scripts, reviewed one at a time
Each of the four keeps its own revisions and its own review, so a finished script never waits on a slower one.
Draft the four scripts
One set per client and Theme: lead generation and database reactivation, each inbound and outbound. Objectives, sections, objections, variables and guardrails all have their own fields.Send each for agency review
Submitting freezes that revision and opens a review task in Projects. A reviewer approves it or requests changes, and the decision records who acted.Publish the approved revision
Publishing makes that revision the one in use. Later edits start a new draft, so the published wording never changes underneath the campaign.Share it and ask the client
Share an approved script read-only, or ask the client to approve it or request changes. They see published wording only.Scale and Enterprise plans
What it is
A controlled source for what a booking agent should say
The library owns the script and its history. Delivering the conversation is a separate job, done in whatever tool your team calls with.
Who sees what
Shared or internal, section by section
Mark a section internal to guide your own team. A client reviewing a script sees only the sections and wording you published for them, never your notes.Revisions
Approved wording stays put
A requested change opens a new draft. The published revision stays exactly as it was.Themes
Copy a set to another Theme
The copy arrives as four clean drafts with review and sharing history reset. The source set is untouched.The boundary
Authoring and review, not calling
This workspace keeps the scripts and their history. It does not place calls, provision phone numbers or run a voice agent; that work belongs to whatever tool your team calls with.
Give every booking campaign one controlled script
Set up the four scripts for a client, review them with your team and share the approved wording when it is ready.
Plans start at $99/month.
On this page
Four scripts cover the full booking campaign
Lead generation and database reactivation, each inbound and outbound
Every script set has four clear slots: Lead Generation Inbound, Lead Generation Outbound, Database Reactivation Inbound and Database Reactivation Outbound. The coverage matrix shows what is drafted, in review or approved, so an account lead can spot a missing conversation before the campaign handoff.
The distinction matters. Inbound conversations begin with the caller's intent and need responsive qualification. Outbound conversations need a permission-based opening, a reason for the call and careful fallback handling. Lead generation focuses on a current inquiry, while database reactivation acknowledges an existing relationship and a different level of context.
Scripts stay grounded in the campaign Theme
Adapt the conversation without losing the original
A weight-management campaign and a hair-restoration campaign may share the same booking goal, but the questions, value framing and objections are not interchangeable. Each set belongs to a real client and one of that client's campaign Themes, alongside the positioning angle, audience and message pillars that give the script its context.
Duplicate a complete set to another Theme when the strategy changes. The new copy starts as four clean drafts with sharing and review history reset, while the source set remains intact. This makes adaptation fast without pretending that a search-and-replace creates a reviewed, campaign-ready script.
A structured conversation, not an ungoverned text blob
Objectives, sections, objections, variables and guardrails in one editor
Each revision separates the pieces a booking conversation depends on: objective, agent role and tone, ordered conversation sections, sample lines, objections and responses, declared merge variables, guardrails, transfer behavior and the booking close. Outbound scripts also make room for permission, disclosure, do-not-contact and voicemail handling; inbound scripts cover greeting, intent capture, after-hours behavior and handoff.
Sections can be marked shared or internal. That gives the agency space for operational direction that should guide its own team without exposing those notes in a client-facing review. Merge variables follow a visible, validated format, so a placeholder is declared and reviewable instead of hiding as an unexplained token inside a long document.
Approved scripts do not change underneath the campaign
Independent revision history for every one of the four scripts
The four scripts in a set can move at different speeds. An inbound lead-generation script may be approved while the database-reactivation outbound script still needs work. Each slot therefore keeps its own numbered revisions, review state and published version rather than forcing the whole set through one all-or-nothing status.
Submitting a draft freezes that revision for review. Requested changes become a new draft while the previously published revision remains available and unchanged. Review decisions record who acted and when, giving the agency a reliable answer when someone asks which wording was approved for a campaign.
Agency approval first, optional client review second
Keep editorial control while giving clients a focused decision
Agency review is the required quality gate. Once a revision is approved, the team can publish it internally, share it read-only with the client, or request a client decision. Client reviewers see the published content intended for them, not internal notes or internal-only sections, and can approve it or request changes with feedback.
Because review is tied to the exact revision, feedback cannot drift onto a later draft by accident. Withdrawing a pending client review and unsharing a script are explicit actions, so visibility changes do not erase the record of what was previously reviewed.
The Library owns the script; execution stays separate
Reusable campaign assets today, clean handoff points for future calling tools
Booking Scripts sits in the Library because it is the authored, reusable source material for a campaign. It is organized by the same client and Theme model as copy, creative, forms and landing pages, while its richer conversation structure and approval history remain purpose-built for booking calls.
This workspace does not place calls, provision phone numbers or claim to run an AI voice agent. Providers, calendars, queues, consent enforcement, recordings and CRM outcome writes belong to a separate deployment flow. Keeping that boundary clear lets teams manage approved scripts now without confusing authoring with live execution.
How the four conversations differ: inbound, outbound, leads, reactivation
A set holds four scripts, one for each pairing of two campaign purposes with two call directions, and each asks for the configuration its direction needs.
| Script | Who the contact is | What the opening has to do | Direction-specific fields |
|---|---|---|---|
| Lead Generation, Inbound | Someone who reached out | Welcome the caller and confirm what they called about | Greeting, intent capture, after-hours behavior |
| Lead Generation, Outbound | A recent inquiry the team is following up | Identify the agent and the client, give the reason for the call and ask for a moment | Permission opener, disclosure, do-not-contact handling, voicemail |
| Database Reactivation, Inbound | An existing contact who came back | Acknowledge the relationship, then find out what brought them back | Greeting, intent capture, after-hours behavior |
| Database Reactivation, Outbound | A past customer the team is re-engaging | Reconnect warmly and ask permission before anything else | Permission opener, disclosure, do-not-contact handling, voicemail |
A structured starter builds all four at once around a four-stage flow: discovery or reconnection, light qualification, education, then questions and objections. Around that flow it adds response routing, the booking step, edge cases, a handoff rule for inbound scripts, a voicemail rule for outbound ones and a close. Treat the starter as a draft to edit with facts from the client profile.
The parts of a script document and what each one is for
Each revision is structured data rather than one long text, so every part can be reviewed, shared or kept internal on its own.
- Objective
- The outcome a successful call produces, stated once so every section serves it.
- Agent role and tone
- Who the agent is on the call and how it sounds, written so a reviewer can judge the voice.
- Sections
- Ordered parts of the conversation, such as opening, discovery, qualification, objection handling, booking, voicemail, compliance and closing, each with instructions and sample lines. A script needs an opening, a booking and a closing.
- Variables
- Merge fields such as {{contact.first_name}}. Each is declared with a label, a description and an example before a section may use it.
- Objections and responses
- A concern a contact is likely to raise, paired with the approved reply. Each pair can be marked internal.
- Guardrails
- Rules the agent must keep, grouped as hard rules, sensitivity rules and claims rules about what it must never say.
- Promotion
- Whether an offer exists (none, single, choice, tiered or multiple), how it may be raised and how often per call. Reactivation offers are normally conditional, raised only when a barrier such as cost comes up.
- Transfer
- When a person should take over and how, within the transfer hours you set.
- Booking details
- The goal, the fields that must be collected before booking and the confirmation wording.
- Fallbacks and contact details
- What to do when nobody answers, when the agent is unsure, when a callback is requested or the line drops, plus office phone, hours and languages.
What the editor checks before a script can go to review
Submitting runs a validation pass and stops on the first problem, so the reviewer starts from a complete document.
| Problem | What the editor says | The fix |
|---|---|---|
| A merge token nobody declared | Declare the variable before using it | Add the variable with a label, description and example. |
| A malformed or repeated variable key | Keys must be lowercase identifiers or dot paths; a key can be declared only once | Rename or remove the variable. |
| No opening, booking or closing section | Add the missing conversation section | Add the section and its instructions. |
| Transfer switched on without criteria | Add at least one transfer criterion | State when a person should take over. |
| No booking fields | Add at least one booking field | List what must be collected before booking. |
| A choice or tiered promotion with one option | A promotion of that kind needs at least two options | Add an option, or change the kind. |
| Missing direction behavior | Inbound or outbound call behavior is required | Fill the greeting or permission fields. |
| No Theme chosen | Choose an existing Theme before submitting | Pick the Theme the set belongs to. |
Some findings only warn. The editor flags an aggressive sales intensity on a reactivation script and a promotion that may be raised more often than standard practice. A warning leaves the decision with the team.
From draft to published to shared: who can do what
Each script moves on its own, and every step is a separate permission so one person cannot quietly do all of them.
| Step | Permission | The rule |
|---|---|---|
| Submit | Edit | Passes validation, names a reviewer other than the submitter and freezes the revision. |
| Approve or request changes | Approve | Only the chosen reviewer or an organization admin can decide, and the decision records who acted and when. |
| Publish | Publish | Makes the approved revision the one in use. |
| Share and ask the client | Share | Shows the published wording read-only, and can ask the client to approve or request changes. |
| Withdraw or unshare | Share | Pulls a pending client review or the share back without erasing the record. |
| Start a revision | Edit | Opens a new draft while the published revision stays exactly as published. |
Note
A set can be archived
An archived set stays on record but its workflow is locked. Restore it before changing a review state.
Sets, Themes and who sees which version
A set belongs to one client and one campaign Theme, and each revision keeps a snapshot of that Theme's positioning as it stood.
Agency owners
Check coverage at a glance
The coverage view lists each of the four slots with its state, so a missing conversation shows up before the campaign hands off. Where a lead should book without a call, a booking page in the landing page builder offers a calendar instead.
- Each set belongs to one client and one Theme
- Duplicate a set to another Theme as four clean drafts
Your team
Write and revise
Writers edit the current draft, submit it, and start a new revision when wording changes. Revision numbers rise while the published one stays put, and submitting opens a review task in Projects.
- Mark a section or objection internal to keep it in-house
- Each revision records the Theme it was written for
Your clients
Read the published wording
In the client portal a client sees shared, published content only: no internal sections, no internal notes and no deployment detail.
- Approve it or request changes with feedback
- Withdrawing a request keeps the history
Plan
Plans for Booking Scripts
Booking Scripts, with agency review and publishing, are available from the Studio plan, priced at $99 a month. Sharing a script with the client and asking for their review needs the client portal on the Scale plan at $699 or Enterprise.
Frequently asked questions
What is an AI booking agent script?
It is the written source a booking agent follows: an objective, a role and tone, ordered conversation sections with sample lines, objections with responses, declared variables and guardrails. In this library the script is authored, reviewed and versioned. Delivering it through a calling tool is a separate job done elsewhere.
What is the difference between inbound and outbound booking scripts?
Inbound scripts start from the caller's intent, so they cover a greeting, intent capture and after-hours behavior. Outbound scripts start from a reason for calling, so they add a permission opener, a disclosure, do-not-contact handling and voicemail rules. Each slot in a set asks for the fields that suit its direction.
What is database reactivation?
Database reactivation re-engages people who already have a relationship with the client but have gone quiet. Its scripts reconnect warmly, listen for why the contact stepped away and keep any offer conditional. Lead generation follows up a current inquiry instead. The library holds a script for each campaign type, in both directions.
Can the library place calls or run a voice agent?
No. The library holds the words and their review history. Calling, phone numbers, calendars, consent checks and recordings happen in the tool your team uses to make the calls, so an approved script is something to hand to that tool, not a running agent.
Who can approve a booking script revision?
The reviewer chosen at submission, or an organization admin. The chosen reviewer must be someone other than the submitter, but an organization admin can decide any review, and the decision records who acted and when. Publishing and sharing are separate permissions, so approving a script does not by itself put it in front of the client.
Can clients see internal notes or internal-only sections?
No. A client sees only the sections and wording published for them. Sections, objections and guardrails marked internal, the internal notes on a revision and deployment details are removed from what the client receives. The client can approve a published revision or request changes with feedback.
How do I change a script that is already published?
Start a new revision. It opens as a draft and goes through review again, while the published revision keeps serving unchanged until you publish its replacement. Earlier revisions and decisions remain on record, so you can always answer which wording was approved for a campaign.