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.
Library · Booking Scripts
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.
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.
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.
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.
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 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.
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.
