Receptionist Call Script for a Small Business

A small-business receptionist call script should identify the business, invite the caller's reason in their own words, gather only what the next owner needs, confirm the correct route, and end with a specific next step. The script should not turn every call into a lead, force a rigid questionnaire, make technical or professional decisions, invent availability, or claim a handoff happened before a person or system accepts it.

TaskChad builds and sells AI receptionist, call-routing, and lead-response systems for small businesses. We have a commercial interest and are not a neutral evaluator. The scripts below are adaptable operating examples, not promises of TaskChad performance. This page is not legal advice, medical advice, financial advice, trade-safety advice, or industry-specific professional advice.

The core opening

Thank you for calling [Business Name]. This is [Name or Assistant Identity]. How can I help you today?

Use the real public business name and an identity description approved by the operator. If the caller reaches a specific location, department, or after-hours line, include that context. Avoid a long promotional greeting before the person can speak.

The opening does three jobs: confirms destination, identifies the answering role, and invites unstructured intent. Do not begin with "Are you a new customer?" because current customers, vendors, employees, wrong numbers, emergencies, and complaints also call.

The first clarification

When the initial reason is unclear:

I want to send this to the right person. Is your call about a new service, an existing appointment or job, billing, a vendor matter, or something else?

Keep "something else" available. The goal is not to force the caller into a sales queue; it is to reduce misrouting. Preserve the person's original words beside the selected class.

If the caller gives a clear reason, do not ask the menu again. Move directly to the relevant branch. A script is a decision aid, not a requirement to repeat information.

New-service branch

I can help get that request to our [team]. May I have your name, the best callback number, and a short description of the service you need?

Then collect the minimum operating facts, such as location or ZIP, property or customer type, desired timing, and contact preference, only when they determine the route. Do not ask a long list before checking whether the business serves the request.

Thank you. I have [brief neutral recap]. I am sending this to [role or team]. The next step is [verified next step] during [verified coverage].

Do not say "someone will call right away" unless a responsible owner accepted that timing. Use speed-to-lead to measure time to owner acceptance rather than time to greeting.

Existing-customer branch

I can route an existing appointment, job, or account question. Do you have a reference number, service address, or the name on the record?

Follow the business's identity and privacy process before exposing status. A matching caller ID or familiar name may help routing but should not automatically reveal account details.

Ask for the broad request: schedule change, job status, service question, billing, warranty, document, complaint, or other. Send it to the authoritative owner. Do not mark an existing customer's call as a new lead just because it entered the main line.

Appointment request branch

I can check the approved appointment options for [service or location]. Before I do, may I confirm [minimum required facts]?

Offer only slots returned by the live scheduling source. Repeat the service, location, date, time, timezone when relevant, and any approved preparation information. Then wait for a durable confirmation receipt.

Your appointment is confirmed for [verified details]. Your confirmation reference is [reference]. If you need to change it, use [approved route].

If the receipt fails:

I do not have a confirmed appointment yet. I have saved your request for [team] to review, and the next step is [approved fallback].

The AI appointment booking automation guide covers concurrency, duplicate protection, rescheduling, cancellation, and failed confirmations.

Estimate or quote branch

I can help start an estimate request. What service are you looking for, and where is the work located?

Collect only facts the estimator uses for initial routing. Avoid diagnosing the work, interpreting coverage, setting technical scope, or promising price. If the company requires a site visit or professional review, state that process accurately.

I have recorded [neutral summary] for [estimator or team]. This is a request for review, not a final quote. The next verified step is [step].

Once a real estimate exists, the separate AI estimate follow-up automation guide owns proposal-state follow-up.

Urgent or safety-uncertainty branch

Every business needs industry-approved words for danger, urgent uncertainty, or situations it cannot evaluate by phone. A generic structure is:

I am not able to determine whether that situation is safe. I will preserve what you told me and follow our approved escalation process. If you believe there is immediate danger, use the emergency resources appropriate to your situation.

Qualified owners and advisors must write the actual branch. The receptionist should not diagnose, minimize, tell someone to enter an unsafe area, or promise that a technician or professional is already responding.

Capture the caller's wording, location if freely provided and appropriate, callback, time, and assigned human. Escalate when the first owner does not accept the record.

Fully booked branch

Our next verified standard availability for [service] is [window]. I can record your request for the next opening, check an approved alternative, or arrange a staff follow-up. Which would you prefer?

Do not say the whole business is full when only one resource or service is constrained. Keep current customer, serious uncertainty, cancellation, and billing routes open. The full what to say when fully booked guide includes waitlist and capacity controls.

Caller asks for price

If an approved fixed price exists:

The current published price for [defined service] is [price], subject to [approved conditions]. I can send the source or help with the next step.

If professional review or inspection is required:

The final price depends on [approved factual factors], so I cannot quote it accurately from this call alone. I can collect the request for [owner] to review.

Do not invent a range, hide required fees, or turn a starting price into a final quote. Maintain prices in an authoritative catalog with effective dates and owners, not in free-form prompt text.

Caller asks for a specific person

May I have your name and a brief reason for the call so I can route it appropriately?

Do not confirm a person's schedule, location, customer relationship, or employment details beyond approved public facts. Use transfer, voicemail, or callback rules based on the person's current status.

If unavailable:

[Person or role] is not available through this line right now. I can take a message for [owned destination] or help identify another appropriate team.

Complaint branch

I am sorry you had to call about this. I want to preserve the issue accurately. Please tell me what happened in your own words, and I will route it to [responsible team].

Do not argue, assign blame, promise an outcome, or label the customer difficult. Capture the relevant service or location, safe callback, desired resolution in the caller's words, and any urgency. Serious safety, privacy, discrimination, legal, or regulatory concerns follow protected escalation.

Close with a real receipt:

I have created reference [ID] for [team]. The current next step is [verified step].

Vendor and sales-call branch

Is this about an existing order or service relationship, or are you offering a new product or service?

Existing vendors can provide a purchase order, job, or contact reference through the approved route. New solicitations should reach a designated inbox or form without occupying customer scheduling queues.

Do not share employee contact details, schedules, internal systems, or buying plans. Mark repeated unwanted solicitations under the business's call policy rather than inventing a confrontation.

Wrong number and unclear intent

Wrong destination:

You have reached [Business Name]. It sounds like you may be trying to reach a different organization. I do not have enough information to direct you safely.

Unclear intent after one clarification:

I do not want to send this to the wrong place. I will create a review task for [team] with your message and callback information.

Do not guess at another company's number or keep the caller inside an endless menu.

The warm-transfer script

Before transfer:

I am connecting you with [role] for [neutral reason]. If the transfer does not complete, the fallback is [verified fallback].

To the receiving person:

I have [caller] on the line regarding [brief factual summary]. I collected [key facts]. Are you able to accept the call?

After explicit acceptance, complete the bridge. If no one accepts, return to the caller or create the promised fallback. The AI sales handoff automation guide explains why a transfer attempt is not an accepted handoff.

The voicemail close

I can record a message for [team]. Please share the best callback number and what you would like them to know. Do not include payment details or sensitive personal information.

Read back a short neutral summary and confirm destination. Do not promise a callback time without coverage evidence. Store audio, transcript, summary, and owner according to the business's privacy and retention policy.

The call-ending script

To confirm, the next step is [verified action] with [owner or team] during [verified timing]. Your reference is [ID] if available. Is there anything about that next step I should correct before we finish?

This close catches routing errors while the caller is present. Avoid "we have handled everything" when only a task exists.

Convert the script into a governed system

For every branch, store purpose, eligible callers, required fields, prohibited decisions, authoritative sources, human owner, fallback, coverage, message version, approval, and review date. Keep fixed business facts separate from conversational phrasing.

NIST's AI Risk Management Framework resources, checked August 13, 2026, provide govern, map, measure, and manage functions for AI risk. Use them to identify affected people, failure modes, test cases, monitoring, and incident ownership. The framework does not endorse TaskChad or certify this script.

Test silence, interruption, accents, background noise, multiple requests, wrong identity, unsupported service, urgent uncertainty, hostile instructions, transfer failure, full capacity, scheduling conflict, and opt-out. Preserve the caller's original words when summaries are used.

Measure the call beyond answer rate

Track calls offered, answered, abandoned, classified, uncertain, routed, transfer attempted, transfer accepted, callback task accepted, appointment confirmed, estimate request accepted, existing-customer case opened, complaint escalated, spam, wrong number, duplicate, completed service, collected revenue, and unknown attribution.

Review routing accuracy, time to human ownership, repeat calls caused by failure, script corrections, sensitive-data exceptions, and terminal outcomes. An answered call is not a lead; a transferred call is not accepted until the next owner says yes; a booked job is not collected revenue.

Build a daily unresolved-call board

List every call that ended without a verified terminal state: uncertain intent, transfer failure, callback task unaccepted, scheduling error, serious escalation awaiting ownership, complaint open, voicemail delivery uncertain, and source mismatch. Show call reference, business or location, request class, last event, age, current owner, next action, and due time.

Reconcile repeat calls into the same episode when appropriate, but preserve the separate attempts. If the customer already reached a person, close the stale callback rather than contacting them again. If the CRM says closed but the phone record shows another unanswered question, investigate the disagreement.

Review the board at shift change. An always-available script cannot compensate for an unstaffed exception queue.

Coach from evidence rather than tone alone

Sample calls by route and outcome: correctly routed, incorrectly routed, abandoned, repeated, escalated, booked, existing-customer resolution, complaint, and no terminal evidence. Score identity, listening, minimal fact collection, accuracy, ownership, verified next step, and privacy or safety boundary.

Do not reward shorter calls that create repeat contact or longer calls that collect unnecessary details. Compare script behavior with downstream acceptance and customer correction. Update the source, branch, training, or integration responsible for the defect.

Keep human and automated receptionist quality measures comparable without pretending they fail in identical ways. Humans may improvise unsupported facts; models may repeat stale sources consistently. Both need governed information and review.

Handle script changes as releases

For each version, record the observed problem, branches affected, approved wording, data-source changes, test cases, reviewer, effective time, monitoring window, and rollback. Test the complete next step, not only whether the new sentence sounds right.

Keep in-flight calls and callback tasks attached to the version that created them. A new script should not erase a prior promise. Monitor misroutes, corrections, repeat calls, sensitive exceptions, and owner acceptance after release before expanding the change to more locations or services.

If your front desk answers calls but requests still disappear between greeting, transfer, and follow-up, run the TaskChad Revenue Leak Score. We can map the script and ownership trail without guaranteeing calls, bookings, leads, or revenue.