Small business owner recording an auto attendant greeting

Stop Losing Callers: Auto Attendant Scripts for SMBs + Setup Checklist

A good auto attendant script gets callers to the right place fast: a short greeting, a small number of clear menu options, and an obvious “press 0” fallback to a live agent. Skip the corporate preamble, put the most-requested option first, and never trap a caller in a menu with no way out. Start by drafting your greeting and top three options today, then test them against real call data within a week.

TL;DR:

  • Most small businesses should start with a simple routing-only auto attendant before considering IVR features, which add cost and complexity.
  • Effective scripts include a quick greeting, three to four menu options ordered by call volume, and an obvious “press 0” for live assistance.
  • Keep prompts short, record in a quiet environment, and test regularly by listening to real call recordings to improve clarity and flow.
  • Limit top-level menu options to three or four, and avoid nested menus beyond one level to minimize caller confusion and abandonment.
  • Using a cloud phone system like Talkroute enables easy setup, schedule-based greetings, and quick adjustments, with plans starting at $19 per month.
Talkroute
Make Every Call Easier to Route
Talkroute helps small businesses create custom auto attendant menus and manage calls from desktop and mobile devices.

Explore Talkroute

Table of Contents

What’s the Difference Between an Auto Attendant and IVR?

An auto attendant routes callers using keypad input. Press 1 for sales, press 2 for support, press 0 for the front desk. It’s a digital receptionist, not a database. Interactive voice response (IVR) does everything an auto attendant does, plus it can accept spoken commands, pull up account information, and complete transactions like payments or appointment lookups without a human ever touching the call, according to Voiso’s breakdown of auto attendant vs IVR.

For most small and mid-sized businesses, that distinction settles the question fast:

  • Choose routing-only auto attendant if your goal is simply getting callers to the right department, mailbox, or extension.
  • Choose data-aware IVR if callers need to check an order status, make a payment, or pull account details without waiting for a person.
  • Cost and complexity climb fast with IVR. Voiso’s research notes that most of the engineering effort in a data-aware IVR build goes into error handling and integration testing, not the prompt scripts themselves.

The practical advice: start with a routing-only auto attendant. Add IVR self-service later, only for a specific, repeatable task that genuinely saves your team time. Trying to build a fully automated phone tree before you’ve nailed basic call routing is how businesses end up with menus nobody can navigate.

How Do You Structure an Auto Attendant Script?

Every effective script follows the same skeleton, whether you’re a two-person accounting firm or a 40-person call center. The components exist in a specific order because each one solves a caller problem the previous one doesn’t.

  1. Greeting. Identify the business by name, thank the caller, and set expectations in under 10 seconds. Long greetings are the number one reason callers hang up before the menu even starts.
  2. Menu options. Present three to four choices, most commonly requested option first. TechRepublic’s IVR scripting guide notes that longer menus directly increase abandonment, because callers forget the first option by the time they hear the fourth.
  3. Extension or direct-dial entry. Let callers who already know an extension punch it in at any point, without waiting for the full menu to finish.
  4. Submenu (if needed). Only add a second layer for options that genuinely branch, like “Sales” splitting into “New Customers” and “Existing Accounts.”
  5. Error handling. If the system doesn’t recognize an input, repeat the menu once, then offer a live-agent option instead of looping endlessly.
  6. Fallback to a live agent. Every menu, every submenu, needs a “press 0” (or similar) exit. Fit Small Business’s script templates treat this as non-negotiable: callers who can’t find a human option abandon the call and often don’t call back.

Pro Tip: Put extension numbers at the end of your greeting sentence, not the beginning. Callers listening for a name or department tune out numbers spoken first, according to Fit Small Business’s template guidance.

Menu design rules worth memorizing:

  • Keep the top-level menu to a handful of options. Longer menus tend to reduce pick rates across the board.
  • Order options by call volume, not internal org chart logic. If a large share of your calls are about scheduling, “press 1 for scheduling” belongs first, even if sales technically outranks it on paper.
  • Allow “any-time” input. A caller who already knows they want extension 204 shouldn’t have to sit through the whole menu.
  • Cap submenus at one level deep whenever possible. A menu inside a menu inside a menu is how callers give up and call your competitor instead.

Accessibility matters here too. Keypad (DTMF) input remains essential for callers who are deaf, hard of hearing, or simply in an environment too loud for voice commands to register. Never build a script that assumes voice input is the only path; every voice-driven option needs a keypad equivalent, and every menu needs a way to reach a human being who can type out a response over relay services if needed.

The pattern behind all of this: short menu, obvious escape hatch, forgiving error handling. FSB’s research found that businesses aiming to route callers within two keypresses or fewer see meaningfully better completion rates than those running deeper trees. A well-built script also reduces average handle time for your team, since fewer misrouted calls means agents spend less time transferring and more time actually helping, a pattern Murf.ai’s IVR guide also documents.

Ready-to-Use Auto Attendant Scripts and Templates

These are copy-and-paste starting points. Swap in your business name, hours, and department names, then adjust based on what your call data tells you (more on that below).

Greeting variants

Professional:
“Thank you for calling [Business Name]. For sales, press 1. For customer support, press 2. For billing, press 3. To reach an operator, press 0.”

Friendly:
“Hi there, thanks for calling [Business Name]! We’re glad you reached us. Press 1 to book an appointment, press 2 if you need support, or press 0 anytime to talk to a real person.”

Terse (high call volume):
“[Business Name]. Press 1 for sales. Press 2 for support. Press 0 for an operator.”

  • Appointment-based businesses (salons, clinics, repair shops): “Press 1 to schedule or change an appointment. Press 2 to speak with billing. Press 3 for our hours and location. Press 0 to speak with our front desk.”
  • E-commerce and order-driven businesses: “Press 1 to check an order status. Press 2 for returns and exchanges. Press 3 for product questions. Press 0 to speak with a representative.”
  • Support-centric teams (SaaS, tech services): “Press 1 for technical support. Press 2 for billing questions. Press 3 to speak with your account manager. Press 0 for general assistance.”
  • General service businesses: “Press 1 for [primary service]. Press 2 for [secondary service]. Press 3 for our office address and hours. Press 0 to speak with someone directly.”

On-hold and queue scripts

“All of our representatives are currently helping other customers. Your call is important to us, and we’ll be with you shortly. If you’d prefer, press 1 now to request a callback instead of waiting on the line.”

Offering that callback option isn’t just a nicety. TechRepublic’s research found that giving callers a queue callback option measurably reduces hold-time frustration and can lower abandonment. Murf.ai’s IVR template library reaches a similar conclusion when reviewing queue callback flows.

After-hours and holiday templates

“Thank you for calling [Business Name]. Our office is currently closed. Our regular hours are [days/times]. Please leave your name, number, and a brief message, and we’ll return your call on our next business day. For urgent matters, press 1 to leave a priority voicemail.”

For holidays: “Thank you for calling [Business Name]. We’re closed today, [Holiday Name], and will reopen on [date] at [time]. Please leave a message after the tone.”

If voicemail is your after-hours fallback, pair it with a follow-up habit. Missed messages that sit unheard for days cost you the customer just as surely as a bad menu does. Talkroute’s guide on maximizing business voicemail covers response-time habits worth building into your team’s routine.

Maximum-wait and payment/survey scripts

Maximum wait exceeded: “We’re sorry for the extended wait. To continue holding, stay on the line. To leave a voicemail instead, press 1. To request a callback, press 2.”

Payment IVR: “To make a payment by phone, press 1. Please have your account number and payment method ready. For all other billing questions, press 2 to speak with a representative.”

Post-call survey: “Before you go, we’d love your feedback. On a scale of 1 to 5, how would you rate your experience today? Press the number that applies.” Post-call surveys like this feed directly into the kind of customer feedback loop that drives measurable revenue growth when businesses actually act on what callers report.

How Should You Record and Word Your Prompts?

Wording and delivery matter almost as much as menu structure. A technically perfect menu tree still fails if callers can’t understand the prompts on the first listen.

  • Keep prompts short. Aim for one idea per sentence and under 10 seconds per prompt. If you’re reading it aloud and running out of breath, it’s too long.
  • Place extensions and numbers last. As noted above, callers process names and departments faster than digits, so save numeric details for the end of the sentence.
  • Pick voice talent deliberately. A professional voice actor costs more upfront but sounds consistent across every recording. In-house recordings work fine for smaller operations, provided one person records all the prompts. Mixing voices between menu levels feels disjointed and unprofessional.
  • If you use text-to-speech, listen critically. Modern TTS has improved, but robotic pacing or mispronounced business names still slip through. Always review generated audio before publishing it live.
  • Record in a quiet, consistent environment. Twilio’s IVR scripting guide recommends recording in a quiet space, using the same voice throughout, and testing the final audio at normal phone volume, not studio headphones, since that’s how customers will actually hear it.
  • Normalize file format and loudness. Export in the format your phone system requires (commonly WAV or MP3), and match volume levels across all prompts so callers aren’t jarred by a loud greeting followed by a quiet menu.

Pro Tip: Call your own auto attendant from a cell phone in a noisy parking lot before launch. Studio-quality playback hides problems that real-world call conditions expose immediately.

One more note that belongs here, not buried later: if your greeting or hold message mentions that calls may be recorded, that disclosure needs to be accurate and consistent with your actual call-handling practices, since recording laws vary by state and by whether all parties must consent.

How Do You Test and Improve an Auto Attendant Menu?

Building the script is half the job. The other half is watching what real callers actually do with it and adjusting accordingly.

  1. Track abandonment rate at each menu level, not just overall. A high drop-off after option 2 tells you something specific about that branch, not your whole system.
  2. Measure time to connect from the first ring to reaching either a person or voicemail. Rising numbers over time usually mean menu bloat has crept in.
  3. Watch for wrong-queue transfers. If support agents keep receiving billing calls, your menu wording for that option is probably ambiguous.
  4. Run simple A/B tests on wording, not structure. Keep the menu order fixed and change only the phrasing of one prompt, then compare per-branch pick rates. Twilio’s testing approach isolates whether clarity or option order is actually driving caller behavior.
  5. Review call recordings monthly. Listening to even ten real calls a month surfaces confusion patterns that raw metrics miss entirely.
  6. Set a review cadence. Quarterly is reasonable for stable businesses; monthly makes sense if you’re actively changing services or hours.

If abandonment climbs at a specific menu step, that’s your troubleshooting starting point, not the greeting and not the fallback option.

What Should Be on Your Auto Attendant Setup Checklist?

Handing a provider a vague request like “set up our phone menu” invites guesswork. Handing them a filled-out checklist gets your system live faster and closer to right on the first attempt.

  • Define business hours and after-hours behavior separately, including holidays.
  • List your top three to four caller needs, ranked by call volume, not department importance.
  • Choose your fallback key (0 is standard) and confirm where it routes.
  • Write and record all prompts before scheduling the technical setup call.
  • Test every branch of the menu, including the error path, before going live.
Menu Level Sample Prompt Destination
Top level “Press 1 for scheduling” Scheduling ring group
Top level “Press 2 for support” Support queue
Top level “Press 3 for billing” Billing extension
Top level “Press 0 for an operator” Front desk / live agent
Error path “Sorry, I didn’t get that. Let’s try again.” Repeats menu once, then routes to operator

Business-hours and after-hours greetings should be scheduled separately in your provider’s admin portal, with holiday overrides set up in advance rather than scrambled together the morning of. That single detail prevents the awkward scenario of a caller hearing your normal business-hours menu on Thanksgiving.

How Do Cloud Phone Systems Turn Scripts Into Live Menus?

Every script above depends on the underlying platform actually supporting it. A multi-level auto attendant needs a few core capabilities: the ability to build nested menus, schedule different greetings by time of day or day of week, upload or record custom prompts, and route each option to a ring group, extension, or voicemail box.

In a typical cloud admin portal, you assign a greeting to a schedule, map each keypress to a destination, and upload or record the audio file directly, no telecom hardware, no on-site PBX. Talkroute’s auto attendant phone system works this way, letting you build the menu structure covered above and adjust it without a service call every time your hours change.

Cloud auto attendant setup workflow

Stick with routing-only auto attendant menus for as long as your business genuinely just needs to get callers to the right place. Add IVR-style features, like phone payments or automated account lookups, only when a specific task is repetitive enough to justify the integration work. For businesses evaluating that jump, reviewing how a cloud phone system handles routing versus deeper integrations is a useful next step before committing budget to it.

If your auto attendant greeting mentions call recording, that disclosure has to reflect what you actually do, and it has to comply with the wiretapping and consent laws of the states where your business and your callers are located. Some states require all parties to consent to a recorded call; others only require one party (which can be your business itself) to know. Because this varies by state, a blanket policy copied from a competitor’s script isn’t a safe assumption, check your own state’s requirement and your callers’ likely locations before finalizing wording.

Beyond recording consent, a few other compliance points belong on your radar. If your business handles healthcare, financial, or other regulated information over the phone, your auto attendant script and any recorded voicemail greetings need to avoid inadvertently disclosing protected details, even in a generic “leave your account number” prompt. Payment IVR flows in particular carry additional handling requirements if callers are entering card numbers by keypad, since that data needs to be processed through a compliant payment system rather than stored in a raw voicemail or call recording.

None of this means avoiding useful features like recorded greetings or payment IVR. It means treating the wording and technical handling as seriously as you’d treat a written privacy policy, because in practice, that’s exactly what a recorded phone greeting is. When in doubt on a specific regulatory question, a quick consult with legal counsel familiar with your state and industry beats guessing.

What Are the Legal Rules for Recorded Greetings and Calls? — overview diagram

Keep the Menu Simple, Keep the Exit Obvious

Most SMBs overbuild their phone menus because more options feel like more professionalism. It’s backwards. A caller who has to sit through five choices to book a haircut appointment isn’t impressed, they’re annoyed. Short menus with an obvious way out consistently beat deep, clever trees for teams under 50 people, mostly because small teams don’t have the call volume to justify the complexity.

Automate further only when a specific task, like payment collection or order lookup, happens often enough to earn the engineering effort. Otherwise, a routing-only setup with a greeting, three options, and press 0 for a person handles the overwhelming majority of small business call volume without a single caller getting lost.

— Paul

Get Your Auto Attendant Live With Talkroute

Talkroute gives you the multi-level menus, schedule-based greetings, and custom prompt uploads this article walks through, without needing a phone technician on-site or a hardware PBX in a closet. You build the menu structure in a web-based admin portal, assign each keypress to a ring group or extension, and switch between business-hours and after-hours greetings automatically based on the schedule you set.

Talkroute

Start with the checklist above: define your hours, rank your top caller needs, pick your fallback key, and write your prompts. Then bring that plan to Talkroute’s auto attendant setup, where you can record or upload your greetings and test the full flow before it ever reaches a real caller. Plans start at $19 a month on the Basic tier, with higher tiers unlocking more numbers and users as your call volume grows. If you’re ready to stop losing callers in a confusing menu, the pricing page is the fastest place to compare plans and get your auto attendant running this week.

Sources

FAQ

What’s a Good Voicemail Script for a Business?

A strong business voicemail script states the business name, apologizes briefly for missing the call, gives expected callback timing, and asks for name, number, and reason for calling. For example: “Thanks for calling Business Name]. We’re unable to take your call right now, but please leave your name, number, and a brief message, and we’ll return your call within one business day.” Talkroute’s guide on [maximizing business voicemail covers how to structure follow-up so these messages don’t sit unanswered.

What Should a Customer Service Voicemail Say?

A customer service voicemail should acknowledge the caller’s likely urgency, confirm the message is being received by the right department, and set a specific callback expectation. A simple version: “You’ve reached customer support for [Business Name]. Please leave your account information and a description of your issue, and a support representative will call you back within [timeframe].”

What’s a Good Script for Leaving a Sales Voicemail?

An effective sales voicemail states your name and company clearly upfront, gives one specific reason for the call, and offers an easy next step. For example: “Hi, this is [Name] with [Company]. I’m reaching out about [specific reason]. Give me a call back at [number], or I’ll try you again in a few days.” Keeping it under 20 seconds and avoiding a generic pitch tends to get more callbacks than a long, scripted rundown.

What Is the Difference Between Auto Attendant and IVR?

An auto attendant routes calls through keypad input to reach a department or person, while IVR can also accept voice commands and complete tasks like payments or account lookups, according to Voiso’s comparison. Most SMBs start with routing-only auto attendant and add IVR features only for a specific, high-volume task.

How Many Menu Options Should an Auto Attendant Have?

Keep the top-level menu to three or four options, ordered by call volume rather than department hierarchy. Research from Fit Small Business shows that businesses aiming for two keypresses or fewer to reach a destination see better completion rates than those running deeper menu trees.

How Much Does an Auto Attendant Cost?

Talkroute’s auto attendant feature is included starting with the Basic plan at $19 per month, with Plus and Pro tiers available for teams needing more users, numbers, or advanced routing. Exact features by tier are listed on the pricing page since they vary by plan.

Stephanie

Stephanie is the Marketing Director at Talkroute and has been featured in Forbes, Inc, and Entrepreneur as a leading authority on business and telecommunications.

Stephanie is also the chief editor and contributing author for the Talkroute blog helping more than 200k entrepreneurs to start, run, and grow their businesses.