RepairLink 5 — Booking + Handoff

Appointment Booking Script Pack

Give humans and automated systems practical, low-friction language for moving an appointment-ready prospect into a specific scheduled next step — supporting both staff-assisted booking and self-service scheduling…

Id

RLR-28

Link

Link Name

Booking + Handoff

Role

script

Loop Step

Repair

Purpose

Design Principles

Favor a concrete next action over vague invitations.
Prefer a specific two-option time offer ('Would Tuesday at 2:00 or Wednesday at 10:30 work better?') over open-ended language ('Let us know when you'd like to meet') — but do NOT force the two-option pattern where self-scheduling is operationally better.
Reduce friction: fewest steps, clearest path, obvious next step.
Preserve context carried from Link 3/4 so the prospect never has to re-explain.
Be concise and specific.
Avoid artificial urgency, unsupported urgency claims, and promised outcomes.
Support both staff-assisted and self-service booking.

Editable Variables

[First Name]
[Service]
[Appointment Type]
[Date]
[Time]
[Timezone]
[Advisor/Attorney/Provider/Rep]
[Location]
[Booking Link]
[Phone Number]

Variable Guidance

Use generic field names where vertical-specific wording would be inappropriate. [Advisor/Attorney/Provider/Rep] is a single role slot the operator sets once per deployment; never hard-code a profession.

Scripts

Phone booking transition

Id: phone_booking_transition
Channel: phone
Objective: Move a live, ready conversation directly into a reserved time.
Script: Great, [First Name] — the next step is a [Appointment Type] with [Advisor/Attorney/Provider/Rep]. I can get you in [Date] at [Time] [Timezone], or would later that week be easier? I'll lock it in now so you don't have to do anything else.
Notes: Book on the call rather than promising to 'send something over.' Confirm the slot verbally, then trigger the confirmation (RLR-29).

SMS booking invitation

Id: sms_booking_invitation
Channel: sms
Objective: Offer a concrete slot or link in a single, scannable message.
Script: Hi [First Name], it's [Advisor/Attorney/Provider/Rep] from [Service]. Ready to set your [Appointment Type]. Does [Date] at [Time] [Timezone] work? Reply YES to confirm, or pick another time here: [Booking Link]
Notes: One clear yes-path plus one self-serve fallback. Respect opt-out and quiet-hours rules.

Chat booking transition

Id: chat_booking_transition
Channel: chat
Objective: Convert an engaged chat into a booked time without leaving the thread.
Script: Perfect — I can book your [Appointment Type] right here. I have [Date] at [Time] [Timezone] open, or you can see all times at [Booking Link]. Want me to grab that slot for you?
Notes: Offer to book on the prospect's behalf; only fall back to the link if they prefer to self-schedule.

Email booking invitation

Id: email_booking_invitation
Channel: email
Objective: Give a ready prospect a clear, specific path to book asynchronously.
Script: Subject: Let's set your [Appointment Type] Hi [First Name], You're all set to move forward with [Service]. The next step is a [Appointment Type] with [Advisor/Attorney/Provider/Rep]. Would [Date] at [Time] [Timezone] work? If so, just reply and I'll confirm. Prefer to pick your own time? Book here: [Booking Link]. Talk soon, [Advisor/Attorney/Provider/Rep] [Phone Number]
Notes: Lead with one specific offer, then the self-serve link — not a link alone.

Direct time-option script

Id: direct_time_option_script
Channel: any
Objective: Offer two concrete times to remove decision friction.
Script: Would [Date] at [Time] or [Date] at [Time] [Timezone] work better for your [Appointment Type]?
Notes: The canonical two-option pattern. Use when a human is guiding the booking; skip when self-scheduling is genuinely easier for the prospect.

Booking-link script

Id: booking_link_script
Channel: any
Objective: Hand off to self-service scheduling cleanly when that is the better path.
Script: You can pick the time that works best for your [Appointment Type] here: [Booking Link]. It takes about a minute, and you'll get a confirmation right away.
Notes: Use when the prospect prefers self-scheduling or when staff cannot book live. Always pair with confirmation (RLR-29).

Urgency-sensitive booking language

Id: urgency_sensitive_booking
Channel: any
Objective: Match a genuinely time-sensitive need to the soonest real slot.
Script: Since this is time-sensitive for you, the soonest I can get you in is [Date] at [Time] [Timezone]. Want me to reserve that now?
Notes: Reference only genuine, prospect-stated urgency and real availability. No fabricated scarcity or 'only slot left' claims.

Alternative-time script

Id: alternative_time_script
Channel: any
Objective: Recover a near-miss when the first offer doesn't fit.
Script: No problem — if [Date] doesn't work, I also have [Date] at [Time] or [Date] at [Time] [Timezone]. Which is easiest?
Notes: Always offer a concrete alternative rather than asking the prospect to propose one from scratch.

Scheduling-objection response

Id: scheduling_objection_response
Channel: any
Objective: Address a hesitation without pressure and keep a path open.
Script: Totally understand, [First Name]. The [Appointment Type] is just [brief, honest description of what happens] — no obligation. If now isn't right, I can hold [Date] at [Time] [Timezone] tentatively, or send the link so you can choose when you're ready.
Notes: Acknowledge, clarify what the appointment actually is, and offer a low-commitment path. Never promise an outcome.

Unable-to-book-now response

Id: unable_to_book_now_response
Channel: any
Objective: Preserve the opportunity when the prospect can't commit to a time yet.
Script: No worries — I'll keep your details so you don't have to start over. When you're ready, just reply here or use [Booking Link], and I'll get you straight in for your [Appointment Type].
Notes: Do not drop the prospect. Set a follow-up (Link 4) and, if appropriate, a tentative hold. Record disposition.

Manual scheduling fallback

Id: manual_scheduling_fallback
Channel: staff
Objective: Book on the prospect's behalf when self-scheduling fails or isn't suitable.
Script: I'll take care of the scheduling for you. I have you down for a [Appointment Type] on [Date] at [Time] [Timezone] with [Advisor/Attorney/Provider/Rep] at [Location]. You'll get a confirmation shortly — anything you'd like me to note for [Advisor/Attorney/Provider/Rep] before then?
Notes: Used when links break, mobile fails, or the prospect prefers a person. Immediately create the booking record and trigger confirmation.

Appointment recap message

Id: appointment_recap_message
Channel: any
Objective: Close the booking with a clear, correct recap that seeds the confirmation.
Script: You're booked, [First Name]. [Appointment Type] with [Advisor/Attorney/Provider/Rep] on [Date] at [Time] [Timezone], [Location]. I'll send a confirmation and a reminder before then. Need to change it? Just reply or use [Booking Link].
Notes: The recap becomes the seed for RLR-29's confirmation content and includes the reschedule path.

Prohibited Patterns

fake scarcity or 'last slot' claims not backed by real availability
promising specific outcomes or results from the appointment
guilt or pressure language
vague closes like 'let us know when you're free' when a concrete offer is possible
ignoring opt-out or quiet-hours signals

Handoff From Link4

Note: Scripts consume Link 4 output — prospect readiness, booking intent, preferred timing, owner, prior context — and never re-run qualification or follow-up logic.
Consumes: prospect_readiness; booking_intent; preferred_timing_if_known; owner; prior_follow_up_context

Handoff To Link6

Note: Booked outcomes from these scripts feed Link 6 without authoring Link 6 content.
Exposes: booked_status; booked_date; appointment_type; assigned_owner

Compliance Guardrail

Every script respects opt-outs, do-not-contact requests, channel permissions, quiet-hours rules, and the business's approved communication policy and consent controls. No script invents legal requirements or bypasses provider restrictions; jurisdiction- and industry-specific rules are applied by the operator.

What To Measure

Whether the scripts move ready prospects into booked, confirmed appointments — tracked via ready-to-booked rate, booking abandonment, and staff-assisted vs self-service booking mix (RLR-27 metrics).

Data Required

Which script/channel was used per opportunity, the booking outcome, and time-to-book, joined to the RLR-27 audit record.

How To Interpret

Rising ready-to-booked rate and falling abandonment after adopting concrete-offer scripts indicate the language is reducing friction. If self-service still outperforms staff-assisted for a segment, favor the booking-link path there rather than forcing the two-option pattern.

Action That Follows

Standardize the winning scripts per channel and segment, deprecate vague-close language, and pair every booking with the confirmation sequence (RLR-29).

Owner

The intake/booking team owns staff-assisted scripts; RevOps owns the self-service link path. Ownership per state is defined in RLR-32.

How To Implement

Insert the variables for the deployment, load staff-assisted scripts into the CRM/telephony and self-service copy into the booking flow, and connect the appointment recap to trigger RLR-29.

How To Test

Run a booking as a prospect on each channel (desktop and mobile), confirm the concrete offer works, the link resolves to the correct calendar/owner, and the recap and confirmation fire.

When To Remeasure

Re-check ready-to-booked and abandonment 14 and 30 days after rollout via RLR-27.

How To Know It Improved

The scripts helped only when re-measured ready-to-booked rate rises and booking abandonment falls on real records — not because new copy was written.

How to implement

Install the change exactly as the playbook describes; log it on the Repair Plan.

How to verify

Installing a workflow is implementation, not closure. QA the repair before you trust it.

Rather not do this part yourself?

You can repair your Revenue Chain yourself with this Kit — or bring in ShiFt at any point. You do not need to finish the DIY path first.

Done with you

Revenue Leak Scan

A ShiFt specialist runs the diagnosis with you and hands you a prioritized repair plan.

Get My Revenue Leak Scan

Done for you

ShiFt RevenueOS

ShiFt installs and operates the full Revenue Chain system for you — ConvertOS included.

See RevenueOS

Id