Who is calling, and what do they need?
Prospective clients ask about support, contracted users report an issue, and vendors or account contacts may call the office. The menu can direct a call but does not replace a ticketing or incident process.
Keep the top-level menu in the caller’s language. In Auto Attendant each option does one thing: it rings up to three phones one after another (each for 10 to 60 seconds, never together), takes a voicemail, or plays a message and hangs up. Point each option at the person, or the shared phone, that actually handles this call, and add a backup only where a missed call costs you.
How it managed services provider calls actually go
An IT managed services provider answers two different kinds of call: a client with an outage who wants a human now, and a prospect or a billing contact who is happy to leave a message. Because clients usually pay for responsiveness, the support key matters more than any other option, and it should reach the engineer on duty, not a general inbox.
The menu should therefore be shaped around severity. Clients with a system down get a key that rings the duty engineer during support hours. Auto Attendant does not forward calls after hours, so round-the-clock support needs its own channel. Everyone else gets a ticket-style voicemail with a transcript, plus a pointer to the support email or portal if the provider has one. The line should not be the primary support channel for routine requests.
Recommended menu
| Caller’s choice | Role to ring | What it does | Why this route |
|---|---|---|---|
| 1. Existing client support | duty engineer, then second engineer | Rings up to 3 phones in turn, then voicemail | The engineer on duty rings first for about 20 seconds, then a second engineer, and a missed call goes to voicemail. |
| 2. New service enquiry | sales contact | Rings one phone | A clear owner can arrange a discovery conversation. |
| 3. Office or account contact | service coordinator | Rings one phone | One coordinator directs callers who do not fit the first two options. |
Scroll the table sideways to see every column.
Shaded text is a fill-in field: replace it with your own.
This example uses 3 menu options. Auto Attendant allows up to seven; add an option only when it sends a distinct kind of caller to a meaningfully different destination. A call that rings every phone you listed without an answer goes to voicemail. The menu can be in English, French or Spanish, and a line can also skip the menu and go straight to one action.
Greeting script
Business name. If you are an existing client calling support, press 1. For a new service enquiry, press 2. For an office or account contact, press 3.
Shaded text is a fill-in field: replace it with your own.
27 words, about 11 seconds spoken at 150 words per minute. The estimate is calculated from the script above; allow extra time for pauses and clear delivery.
Read each reason before its key, as in “For a new enquiry, press 1”. Replace the shaded fields and any role or service wording before you type the greeting into the menu; a text-to-speech voice reads it to callers.
A worked example
Illustration: a four-engineer MSP offers 1 for support, 2 for new business and 3 for billing. Option 1 is worded “for a security incident or a system outage” and rings the duty engineer. The voicemail asks for company name, a callback number and a one-sentence description, so the transcript can be turned into a ticket without a second call.
The failure pattern is a duty phone that moves between engineers without anyone updating the menu. The person whose turn it is does not have the phone, and the person who has it does not know it is their turn. A rota owner and a Friday test call fix it.
After hours, weekends, and holidays
State support coverage and the approved method for reporting a priority incident. If the phone is not monitored outside coverage, say so clearly and direct clients to the contracted support channel.
Check the support rota and service commitments for each holiday. Keep the greeting aligned with the channels the support team actually monitors.
Outside the hours you set, Auto Attendant plays your closed message and then takes a voicemail or ends the call; it does not forward calls after hours, and holidays are closed all day. Where the advice above mentions an on-call route, either keep that person’s option within your set hours or give the arrangement in the closed message.
Check the greeting after every schedule change. A voicemail arrives by email with the recording attached and a transcript when one is produced, but it does not make the call live or guarantee a response time.
Rules and standards worth knowing
NIST’s Small Business Cybersecurity Corner gathers guidance for small organisations 1, and its Cybersecurity Framework helps organisations understand and improve their management of cybersecurity risk 2. NIST SP 800-61 assists organisations in establishing incident response capability 3. If your service includes security response, the phone menu is the front door to that process, so its escalation path should match your incident procedure.
CISA’s Stop Ransomware resources describe how ransomware works and what to do if you are affected 4, and its voluntary cross-sector performance goals set out a limited number of high-impact actions for small and medium-sized organisations 5. Clients in the middle of an incident will call; a calm, accurate first ten seconds matters.
If engineers are on call, the Department of Labor’s on-call rule distinguishes between being confined to a place and merely being reachable 6. Settle the arrangement and the pay for it before the rota goes live.
This is general information, not legal advice. Rules differ by state and change; confirm anything that affects your business with the source or an adviser.
Common menu mistakes
- Calling a general mobile the support desk when it is not monitored.
- Treating voicemail as a ticket with a response target.
- Publishing technical escalation details in a public greeting.
Keep the greeting short, use the same names callers see elsewhere, and make sure every route has a sensible end when nobody picks up.
Check the menu before you publish it
- Define “outage” and “security incident” in one sentence at the start of the support branch.
- Name the duty engineer and a backup, and test the route every Friday.
- Turn each transcript into a ticket within a stated time.
- Point routine requests to email or a portal in the greeting.
- Align the escalation path with your written incident procedure.
Related guides and templates
- Accounting and bookkeeping firm: phone menu guide
- Law firm: phone menu guide
- Nonprofit office: phone menu guide
- Insurance agency: phone menu guide
- Sequential on-call escalation: call-flow template
- Urgent after-hours line for trades: call-flow template
- Service versus sales submenu: call-flow template
- Role mailbox greeting: call-flow template
- Call routing and menu design
- Auto attendant or answering service
Further reading
Longer research pieces on this topic, each with its own source list and a downloadable PDF.
Articles on this topic
Topics Small business phone Auto attendant Call forwarding Voicemail All topics
Sources
Every regulatory and pricing claim on this page links to the primary source it came from. Figures were checked on the date shown at the top of the page; rules and prices change, so verify before relying on one.
- NIST, Small Business Cybersecurity Corner. Retrieved 14 Oct 2026
https://www.nist.gov/itl/smallbusinesscyber - NIST, Cybersecurity Framework. Retrieved 14 Oct 2026
https://www.nist.gov/cyberframework - NIST SP 800-61 Rev. 2, Computer Security Incident Handling Guide. Retrieved 14 Oct 2026
https://csrc.nist.gov/pubs/sp/800/61/r2/final - CISA, Stop Ransomware. Retrieved 14 Oct 2026
https://www.cisa.gov/stopransomware - CISA, Cross-Sector Cybersecurity Performance Goals. Retrieved 14 Oct 2026
https://www.cisa.gov/cybersecurity-performance-goals - 29 CFR § 785.17, On-call time (US Department of Labor hours-worked rules). Retrieved 14 Oct 2026
https://www.law.cornell.edu/cfr/text/29/785.17