Communications
Make Sure Every Call Goes Somewhere Useful
Bad routing is expensive in a way nobody itemizes, because callers who give up do not send a report explaining why. Mayer Networks designs main-number routing, departmental menus, hours-based behavior and overflow paths with the staff who answer the phones, then configures and dials every path before cutover so no call ends in silence.
The problems this fixes
Bad routing is expensive in a way nobody itemizes. Callers who give up do not send a report explaining why.
- The receptionist is answering every call and transferring most of them
- Callers get passed between three people before reaching the right one
- Departments keep different hours and the greeting does not know that
- After-hours calls ring an empty office
- Holiday schedules get changed manually, when someone remembers
- A weather closure needs a routing change today, not next week
How a call actually travels
Make sure every call goes somewhere useful
Step 1
Incoming call
Answered against the schedule for that day: open hours, closed hours, lunch or holiday.
Step 2
Auto attendant
- Sales
- Support
- Billing
- Company directory
Step 3
Somewhere useful
- Queue
- Employee extension
- Voicemail with follow-up
No path ends in silence. Every branch has an overflow destination, and the whole flow is dialed and tested before cutover rather than discovered by a customer.
Who this fits
- Organizations whose main number lands somewhere unhelpful
- Offices with departments that each need their own path
- Public agencies with statutory hours and holiday closures
- Anyone who has to call a vendor to change a greeting
What breaks first on old phone systems
- Menus with too many options and no way to reach a person
- After-hours callers hearing a greeting that says the office is open
- Holiday closures nobody remembered to configure
- Calls that ring forever because no overflow destination exists
What is included
- Main-number routing design
- Departmental menus and submenus, kept shallow on purpose
- Business-hours, after-hours and lunch routing
- Holiday schedules, including agency and county calendars
- Overflow and alternate destinations
- Voicemail routing per department, per person or to a shared box
- Routing into call queues where queues are used
- Temporary and emergency routing changes: weather closures, outages, building events
How a phone cutover runs
Step 1
Map the current reality
We start from how calls actually arrive today and where they get stuck, not from a blank call-flow diagram.
Step 2
Design with the people who answer
Front desk, dispatch and department staff know which calls are misdirected. They are in the design conversation.
Step 3
Build and dial every path
Each option, each schedule and each fallback is tested by calling it, including after-hours behavior tested outside hours.
Step 4
Change it when you need to
Routing changes are configuration. Weather closures and temporary coverage are handled the day they come up.
Supported by people who know your business
Mayer Networks VoIP customers are supported by the same Southern Illinois technology team that manages their network and IT environment. When something goes wrong, the conversation does not start with a national call center reading a script and asking what a firewall is.
Local engineers, remote support for the things that can be fixed remotely, and onsite capability for the things that cannot. Mayer Networks has been supporting organizations in this region since 2006, and the people answering your call already know how your system is built.
Designing a call flow that survives contact with real callers
The failure mode of a badly designed auto attendant is not that it is confusing, it is that it teaches callers to press zero immediately, which puts every call back on the front desk. A good flow reflects how the organization is actually structured: the three or four destinations that account for most calls, an obvious route to a person, and a sensible place for everything else to land.
The paths nobody designs are the ones that fail. What happens when the queue is empty at 4:55 and a call arrives at 4:58? Where does a caller go when a department's only staff member is at lunch? What plays on the Friday after a holiday? We write those endings down during design rather than discovering them from a complaint.
- Shallow menus, with a route to a live person on every level
- Named destination for every timeout, busy condition and no-answer case
- Hours defined per department where departments keep different hours
- Greetings recorded properly, since a phone-recorded greeting is the first impression of the organization
Why Mayer Networks
- Callers reach the right department instead of a directory maze
- Schedules are configured once and adjusted as your calendar changes
- Every routing path has a defined ending, including the ones nobody plans for
- One organization accountable for support, engineering, security, infrastructure and communications.
Security considerations
- Administrative access to call flow restricted to authorized staff
- Change history retained so routing changes can be traced
- Shared voicemail boxes given owners rather than being everybody's problem
- After-hours paths reviewed so they do not become an unmonitored dead end
How many menu options should we have?
Fewer than most organizations expect. Beyond four or five choices callers stop listening and press zero. It is usually better to route on department with a clear path to a person than to build a decision tree.
Can callers always reach a human?
That is our default recommendation: an option to reach a person, and a defined destination when nobody answers. Menus that trap a caller generate complaints and repeat calls.
Can routing change automatically on holidays?
Yes. Holiday schedules are configured in advance, including the closures specific to a public agency's calendar, so nobody has to remember to change a greeting the night before.
Who can change our call flow?
Designated staff can be given administrative access for routine changes, and we make changes on request for organizations that would rather not. Either way, changes are traceable.
Can we route differently during an emergency?
Yes. Weather closures, building evacuations and outages are handled by switching to a prepared alternate path rather than improvising while the phones ring.
Let's talk about your technology
Tell us what you are running and what is not working. We will tell you plainly what we would do about it.