SureTel
Business phone system guide
Auto-Attendants (IVR) Explained
Route business callers faster with practical IVR menus configured around your teams and working hours.
- • Cloud PBX, VoIP, Yeastar and 3CX support
- • Call-flow planning assistance
- • Business-hours and after-hours routing
- • South African telecoms partner
Educational resource · Not a quote · Licensed SA ISP · ICASA licence 0009/CECS/AUG/09
Answer first
Auto-attendants and IVR menus, in one paragraph
An auto-attendant, also called an IVR or virtual receptionist, answers incoming calls and routes callers to the right person, department, queue or voicemail using menu choices and call rules. SureTel can configure practical auto-attendant call flows for Cloud PBX, VoIP, Yeastar and 3CX environments. Request a quote to scope your call routing.
- Useful for sales, support, accounts, reception and branch routing.
- Can route to ring groups, call queues, voicemail or specific extensions.
- Supports business-hours, after-hours and holiday rules where the phone system supports them.
- Should be kept short so callers reach help quickly.
- SureTel can assist with call-flow planning, recordings and testing.
Problems an auto-attendant solves
The costs of an unmanaged main number
Many businesses lose time when every call starts with reception, or when callers are passed between people before reaching the right team. A simple auto-attendant gives sales, support, accounts, branches and after-hours callers a cleaner front door.
Reception overload
Cost: Staff spend too much time forwarding calls
How IVR helps: Routes common calls directly to teams
Wrong transfers
Cost: Callers repeat themselves
How IVR helps: Uses clear menu options
After-hours missed calls
Cost: No structured message or voicemail path
How IVR helps: Applies time-based routing where supported
Multi-branch confusion
Cost: Callers do not know which number to use
How IVR helps: Routes from one main number to branches
Busy support teams
Cost: Callers reach unavailable staff
How IVR helps: Sends calls to queues or ring groups
Unclear departments
Cost: Sales, accounts and support calls mix together
How IVR helps: Separates routes by intent
When an IVR fits
Best-fit businesses for a practical IVR
Auto-attendants fit businesses that receive enough calls to need structured routing, but they should be designed around caller needs rather than internal complexity. The best menus are short, predictable and easy to understand.
Reception-heavy businesses
Reduce simple call transfers by sending common calls directly to the right team.
Sales and support teams
Separate new sales enquiries from support requests so each queue is handled by the right people.
Professional firms
Route clients to reception, accounts or departments from a single main number.
Medical and pharmacy environments
Route general enquiries, accounts or dispensary-style flows where appropriate. Use carefully and only for genuine urgent paths — an IVR is not a clinical triage or emergency-response system.
Automotive businesses
Route service, parts, sales and admin calls to the right desk.
Multi-branch businesses
Send callers to the right location from one main number and reduce cross-branch transfers.
Call centres
Send callers to the correct queue before agent handling, so the queue only holds relevant calls.
What SureTel can configure
The routing pieces SureTel plans and configures
SureTel can assist with call-flow planning, IVR menu wording, routing logic, recordings or uploaded prompts, testing and handover. The goal is to make the menu practical for callers and manageable for the business — never to replace people or promise every caller will always pick the correct option.
| Configuration area | What to specify | SureTel support note |
|---|---|---|
| Greeting | Main welcome message | SureTel can help with wording and prompt planning. |
| Menu options | Sales, support, accounts, reception, branches | Map options to real teams or routes, not internal jargon. |
| Destinations | Extensions, ring groups, queues, voicemail | Configured according to phone-system capability. |
| Business hours | Open-hour rules | Route calls differently during office hours where supported. |
| After-hours | Closed-hour rules | Play a message, route to voicemail or route to an approved fallback where supported. |
| Holidays | Special date routing | Seasonal or public-holiday flows can be configured depending on the phone system. |
| Emergency option | Escalation or urgent route | Use carefully and only for genuine urgent paths — never presented as clinical triage or emergency-response capability. |
| Testing | Inbound call checks | Test real call paths before handover so callers are not the ones who find a broken route. |
Greeting
Specify: Main welcome message
Note: SureTel can help with wording and prompt planning.
Menu options
Specify: Sales, support, accounts, reception, branches
Note: Map options to real teams or routes, not internal jargon.
Destinations
Specify: Extensions, ring groups, queues, voicemail
Note: Configured according to phone-system capability.
Business hours
Specify: Open-hour rules
Note: Route calls differently during office hours where supported.
After-hours
Specify: Closed-hour rules
Note: Play a message, route to voicemail or route to an approved fallback where supported.
Holidays
Specify: Special date routing
Note: Seasonal or public-holiday flows can be configured depending on the phone system.
Emergency option
Specify: Escalation or urgent route
Note: Use carefully and only for genuine urgent paths — never presented as clinical triage or emergency-response capability.
Testing
Specify: Inbound call checks
Note: Test real call paths before handover so callers are not the ones who find a broken route.
Supported environments
- SureTel Cloud PBX
- SureTel VoIP environments where call routing is in scope
- Yeastar systems where applicable
- 3CX systems where applicable
Yeastar and 3CX are cited as supported environments where the setup is technically applicable — not as certified partnerships or guaranteed compatibility with every platform feature.
A typical IVR call flow
Main business number
Caller dials the published main line.
IVR greeting
A short welcome plays and lists the menu options.
Menu options
Sales, support, accounts, reception, branches — or a hold-for-operator fallback.
Destinations
Extensions, ring groups, call queues, voicemail or an approved after-hours route.
The diagram shows a planning model. Actual behaviour depends on the phone system, its call-routing capability and how the menu is scoped for the business.
Example IVR menus
Short, practical menu examples by business type
Use examples to make the topic tangible, but do not force every customer into the same call flow. Each menu should be scoped around the business’s departments, call volumes, hours and support process.
General SME
Menu: Press 1 for sales, 2 for support, 3 for accounts, 4 for reception, or hold for the operator.
Note: Keep the default path simple.
Automotive
Menu: Press 1 for vehicle sales, 2 for service bookings, 3 for parts, 4 for accounts.
Note: Useful when callers have a clear reason for calling.
Medical / pharmacy
Menu: Press 1 for reception, 2 for accounts, 3 for repeat enquiries where appropriate.
Note: Avoid sensitive promises. Route urgent care responsibly — an IVR is not clinical triage.
Multi-branch
Menu: Press 1 for Johannesburg, 2 for Pretoria, 3 for Sandton, 4 for accounts.
Note: Useful for one main number across sites.
Support team
Menu: Press 1 for new support, 2 for existing tickets, 3 for accounts.
Note: Consider call queues when agents may be busy.
Every example should be tested before go-live. Menu wording and destinations depend on the phone system and the way each business handles its inbound calls.
Auto-attendant vs call queue
Two different jobs that often work together
An auto-attendant decides where a caller should go; a call queue manages callers waiting for available agents. Many business systems use both together — the IVR routes support calls into the queue, and the queue handles the wait. The deeper explanation of queues, wait behaviour, agents, overflow and reporting is covered in the dedicated Call queues explained article.
| Feature | Auto-attendant / IVR | Call queue |
|---|---|---|
| Main job | Routes callers by menu choice or rule | Holds callers until someone is available |
| Caller action | Presses a key, waits, or chooses an option | Waits in line for an agent or team |
| Common destination | Extension, ring group, queue, voicemail, branch | Agents or a support/sales team |
| Best for | Main-number call routing | Busy teams that answer similar calls |
| Example | "Press 1 for sales" | "All agents are busy, please hold" |
| Related page | This article | Call queues explained |
The Call queues explained article covers queue setup, wait behaviour, agents, overflow and reporting in more depth. This page keeps the queue treatment intentionally short so the two articles stay distinct.
Common mistakes
Menus that look tidy inside can still frustrate callers
A menu that looks organised internally can still frustrate callers if it is too long or unclear. The list below points to the simple, caller-first routing patterns that hold up in practice. Queue-specific patterns live in the Call queues explained article.
Mistake
Too many options
Why it hurts: Callers forget the choices
Better approach: Keep menus short and use submenus only when needed
Mistake
Internal jargon
Why it hurts: Callers do not know which option to choose
Better approach: Use plain department names
Mistake
No operator option
Why it hurts: Callers feel trapped
Better approach: Allow hold-for-operator or a clear fallback where appropriate
Mistake
No after-hours routing
Why it hurts: Closed businesses sound unavailable
Better approach: Use after-hours greetings with voicemail or an approved escalation
Mistake
No testing
Why it hurts: Calls can route to the wrong place
Better approach: Test every path before go-live
Mistake
No holiday rules
Why it hurts: Public holidays confuse call handling
Better approach: Plan holiday prompts and routes in advance where supported
Mistake
No voicemail plan
Why it hurts: Missed calls go nowhere useful
Better approach: Assign voicemail destinations and notification handling
Mistake
Overpromising automation
Why it hurts: IVR cannot solve every service issue
Better approach: Keep routing realistic and support it with people and processes
What is an auto-attendant
The mechanics behind the menu
Underneath the wording, an auto-attendant is a phone-system call-flow feature that uses greetings, keypress options, time rules and routing destinations to control what happens after a caller reaches a business number. The pieces below are the moving parts you actually configure.
- A greeting tells callers they reached the right business.
- Menu options route callers to teams, extensions or branches.
- Time rules change routing during business hours, after hours and holidays where supported.
- Destinations can include extensions, ring groups, queues or voicemail.
- A fallback route handles callers who do not press an option.
Buyers often use “auto-attendant”, “automated attendant”, “IVR” and “virtual receptionist” interchangeably. Different platforms label the feature differently, but the behaviour above is what the terms describe in practice.
Multi-branch and department routing
One main number, several destinations
For multi-branch businesses, one main number can route callers to branches, departments or shared teams. That supports a cleaner call experience for the caller and takes pressure off individual branch lines — without pretending routing alone solves every operational issue.
- Main number → branch menu → local reception or queue.
- Main number → department menu → sales, support or accounts.
- After-hours main number → an approved fallback route or voicemail.
- Holiday route → special announcement and voicemail where supported.
- Branch overflow → central reception or support queue where configured.
For a broader look at how multi-branch phone systems fit together, see multi-branch phone systems.
Why set up IVR with SureTel
The practical implementation partner, not just a menu
SureTel plans, configures and tests call flows rather than leaving customers to figure out PBX menus alone. IVR does not replace reception staff, and it will not make every caller pick the right option — but a scoped call flow, sensible fallbacks and real testing consistently reduce noise on the main number.
IVR menus on Cloud PBX, Yeastar and 3CX
SureTel can configure auto-attendant / IVR menus on SureTel Cloud PBX and, where applicable, scoped Yeastar and 3CX systems.
Call routes planned around your teams
SureTel helps plan call routes around real teams, working hours and branches — not around a generic template.
Prompt wording, recordings and testing
SureTel can assist with prompt wording, recordings or uploaded prompts and testing before go-live.
VoIP, Cloud PBX, queues and connectivity together
SureTel understands business VoIP, Cloud PBX, call queues and connectivity together, so the IVR is planned as part of the wider phone setup.
Licensed South African ISP · ICASA licence 0009/CECS/AUG/09 · Standard support Monday–Friday, 08:00–17:00. These facts do not guarantee call outcomes, caller satisfaction or a specific implementation date.
Setup process
How SureTel scopes and configures an IVR
The steps below describe the scoping and implementation path at a business level. They are not PBX admin instructions — the platform configuration is handled by SureTel where the environment is supported.
Map call types
Identify sales, support, accounts, reception, branches and any urgent routes.
Design the menu
Keep options short and caller-friendly, with a clear fallback.
Choose destinations
Route to extensions, ring groups, queues or voicemail depending on the phone system.
Record or upload prompts
Use clear, professional wording that matches the business.
Apply time rules
Configure business-hours, after-hours and holiday logic where supported.
Test all paths
Check real inbound calls before handover, not after.
Handover and support
Explain the flow to the team and adjust when business needs change.
Related resources
Keep planning the phone system
Practical next reads for teams scoping call routing, connectivity and phone-system decisions.
- How to set up VoIP for your business
Practical steps for planning a VoIP setup before wiring up call routing.
- VoIP equipment and hardware guide
Desk phones, softphones, headsets and gateways that fit different roles.
- VoIP bandwidth and internet requirements
What the connection needs to look like before piling IVR flows on top of it.
- Business phone systems overview
How IVR menus sit inside the wider business phone-system decision.
- Multi-branch phone systems
One main number, several sites — planning the routing and branch overflow.
For deeper queue-specific detail — wait behaviour, agents, overflow, reporting — the Call queues explained article is the dedicated home for that topic. For hands-on scoping, use contact SureTel or request a quote.
Auto-attendant FAQs
Frequently asked questions about auto-attendants and IVR menus
What is an auto-attendant in a phone system?
An auto-attendant is a phone-system feature that answers incoming calls and routes callers using menu options and routing rules. Callers may hear options such as “Press 1 for sales, 2 for support, 3 for accounts, or hold for reception.”
Is an auto-attendant the same as IVR?
The terms are often used together. In business phone systems, an auto-attendant is usually the automated menu that greets and routes callers. IVR means interactive voice response and may refer to menu-based call routing or more advanced caller input features, depending on the platform.
What is the difference between an auto-attendant and a call queue?
An auto-attendant routes callers to the right destination. A call queue holds callers while they wait for an available person or team. A common setup is to use the auto-attendant first, then send support or sales calls into a queue.
Can SureTel set up an IVR menu for my business?
Yes. SureTel can assist with IVR menu planning, call routing, prompt wording, recordings or uploads, testing and handover on SureTel Cloud PBX and, where applicable, Yeastar and 3CX systems.
What should my IVR menu say?
Keep the menu short and practical. A common example is: “Press 1 for sales, 2 for support, 3 for accounts, 4 for reception, or hold for the operator.” The right wording depends on your departments, branches and caller needs.
Can an auto-attendant route calls after hours?
Yes. Auto-attendants can use business-hours, after-hours and holiday rules where the phone system supports them. After-hours calls can play a different greeting, route to voicemail, transfer to an approved fallback route or follow another agreed call flow.
Can one number route callers to different branches?
Yes, a business can use one main number with an IVR menu that routes callers to different branches, teams or departments. This is useful for multi-branch businesses that want a cleaner main-number experience.
Can callers still reach a person if they do not choose an option?
They should be able to where the business wants that experience. Many IVR menus include a hold-for-operator path, a timeout route, a fallback extension, voicemail or a queue. SureTel can help design a fallback path so callers are not left stuck in the menu.
Next step
Need a cleaner way to handle inbound calls?
Request a quote from SureTel and we’ll help you plan the right auto-attendant, call routing and Cloud PBX for South African businesses. For the calling service context see business VoIP services.
Your details are used to respond to this enquiry and are handled according to SureTel’s Privacy Policy.