A receptionist does not need your entire operations manual on day one. Start with a short, approved reference for routine calls, plus a reliable way to reach the person responsible for exceptions. The goal is a useful next step for the caller, even when the answer requires your team.
This guide covers preparation and sign-off. For the service itself, see business call answering; for calendar coordination, see appointment scheduling.
What should you prepare before coverage starts?
Your greeting and business facts
Write the exact business name and pronunciation, opening hours and time zone, holiday exceptions, locations or service area, and an approved website or information sheet. Separate business opening hours from the hours when receptionist coverage is actually available.
The calls you want handled
List your common call reasons: a new inquiry, an existing customer question, an appointment change, a complaint or a supplier call. For each, choose an outcome: answer from approved information, book within permissions, send a message or attempt a transfer. Mark anything the receptionist must refer to a decision-maker.
Answers and authority limits
Record which prices, policies and service descriptions may be quoted. Say who can approve discounts, refunds, exceptions and commitments. “I can pass that request to the manager” is safer than implying approval. Add an owner and review date to your reference so outdated information is easy to identify.
Calendar and system permissions
Define appointment types, durations, buffers, time zones and who can approve a cancellation or reschedule. Specify whether the receptionist can confirm a booking or only request one. Give each person appropriate access through the system's account or invitation process; keep passwords and sensitive customer records out of a shared call script.
A contact and backup route
Name the primary recipient for each call type, their availability, and a backup. Define which situations warrant an interruption. If neither person answers, specify the approved message and callback process. A transfer attempt should never be described as a completed handoff.
A message destination and follow-up owner
Choose where messages go and who checks them. A message needs the caller's name, confirmed callback number, reason, relevant reference, requested timing, action already taken and next owner. Agree realistic response windows before anyone promises them to a caller.
Copy this onboarding worksheet
Complete one copy for your business, then add a short rule for each common call type.
- Approved by / last reviewed: [name] / [date]
- Greeting: “Thank you for calling [business]. How can I help?”
- Coverage: [days, hours, time zone] / outside-hours route: [destination]
- Call reason: [for example, an existing order question]
- Required details: [name, callback number, reference, request]
- May answer or change: [approved information and permissions]
- Needs approval: [exceptions and approving person]
- Primary / backup: [contact, availability] / [contact, availability]
- If unavailable: [message destination and follow-up owner]
- Caller hears: [the next step and any approved response window]
Keep it practical: if you cannot name the next owner, the workflow is not ready for that call type.
Test decisions, not just the greeting
Have a colleague act as a caller before you enable coverage. Use these practice scenarios with invented customer details. Check what the caller hears and whether the correct person actually receives the message.
- A routine new inquiry: Can the receptionist find the approved answer and collect a usable callback number?
- A request outside your policy: Ask for an unapproved discount or unavailable time. The receptionist should explain the review step without granting the exception.
- A failed transfer: Let the primary contact go unanswered. Check the backup route, the message destination and the wording used with the caller.
- A request near closing: Make sure the receptionist distinguishes the coverage window from any callback commitment. Confirm what happens to unresolved requests.
- An unclear request: The receptionist should ask for clarification and record uncertainty rather than guess a price, policy or customer identity.
Example: an order change that needs approval
A customer asks a small wholesaler to change a delivery address after dispatch. The receptionist records the order reference, callback number and requested address, then contacts the approved operations lead. If that person is unavailable, the message goes to the named backup. The caller hears that the change has been requested and still needs confirmation.
This is an illustrative training scenario, not a customer result. The same decision pattern works for a cleaning schedule exception or a professional office's request for a manager.
When is the receptionist ready?
Sign off when they can handle routine questions, recognize approval boundaries, use the backup route and leave a complete message in the correct place. After coverage begins, review a small selection of actual inquiries with the responsible staff member. Record the rule that needs changing, its owner and the approved update. Keep spam, sales pitches and practice calls separate from genuine customer inquiries when reviewing demand.
What should you bring to an FDS consultation?
Bring your completed worksheet, busiest call times, approximate call volume if known, and the tasks you want covered. Compare plans, included coverage and pricing and ask which permissions, routing arrangements and fallback steps fit your setup. This checklist is preparation guidance; the agreed service scope determines what FDS handles.
Explore a sample customer call, or book a consultation to discuss your onboarding plan. Trade businesses can also use the more specific contractor call intake checklist.
