IVR Call Flow Design: A Step-by-Step Blueprint for Ghana

GAGodwin AmefiaSeptember 21, 202614 min read

A hand-drawn IVR call flow on a single sheet of paper: a box for the incoming call, a business-hours decision, a main menu branching to order status, support, sales and accounts, and a marked green route out to a person. A ringing mobile phone sits on a card beside the sheet.

Your phone menu is the part of your service most callers actually meet. Good IVR call flow design decides whether they press the right option and reach the right person, or give up and ring someone else.

Voice is not a fading channel here. Ghana counted 42.18 million mobile voice subscriptions at the end of Q3 2025, and total domestic mobile voice traffic reached 29.01 billion minutes in the same quarter, up 3.65% year-on-year from 27.99 billion minutes in Q3 2024, according to the National Communications Authority.

Most phone menus that frustrate callers are not broken systems. They are badly drawn flows, and this guide takes IVR call flow design one step at a time, from the sheet of paper to the live line.

What is an IVR call flow?

An IVR call flow is the map of every path a call can take, from the moment it connects to the moment it ends: what the caller hears, which keys they press, where each choice sends them, and what happens when nobody answers.

The IVR is the system. The call flow is the design you run on it. That distinction matters, because the fix for a menu customers hate is almost always a change to the flow rather than a change of platform.

If you want the mechanics underneath it first, our guide to how interactive voice response works covers them, and the call flow is one piece of a larger operation set out in our guide to running a cloud contact centre in Ghana. This article assumes you already have an IVR, or are about to get one, and need to decide what it does.

How do you map out an IVR call flow before building it?

IVR call flow design starts on paper, not in software, and setting up an IVR system goes faster when the drawing is already done. A call flow built from assumptions routes calls to the wrong team, so settle these four things first and the drawing itself takes twenty minutes.

Your real call reasons, ranked. Not the categories on your website. The reasons people actually ring, in the order they ring about them.
Who answers each one. A named team or person behind every branch. A branch with no owner is a dropped call waiting to happen.
Your real opening hours. Including the half-days, the public holidays, and the lunch hour when one person covers three lines.
What the caller does when nobody is free. Hold, leave a voicemail, request a callback, or get the answer from an automated option. Decide now, because leaving this branch undefined is what turns a missed call into a lost customer.

Write these on one sheet of paper. Everything below is built on them.

Step 1: Write down why people actually call

Pull the last two weeks of calls and group them by reason. If you have no call log, ask the three people who answer the phone most what they heard yesterday.

Rank the list by volume. Only the reasons at the top of it earn a place on the main menu. Everything further down belongs deeper in the flow, or on another channel entirely.

Now mark each reason with one of two labels: needs a person, or can be answered automatically. Balance enquiries, delivery status, opening hours and payment confirmations often sit in the second group, and moving them there takes weight off the queue straight away. Our guide to IVR self-service and reducing call volume covers which requests deflect cleanly.

Use the caller’s words in that list. “Where is my order” is a call reason. “Logistics enquiries” is an internal label, and a caller scanning the menu for it will press 0 instead.

Step 2: How many options belong on an IVR main menu?

Keep the main menu short. A handful of options, not a list the caller has to hold in their head while it plays. Someone who reaches the end of a long menu without hearing their reason will press whatever they remember, and the misrouted calls arrive on your team’s desk to prove it.

The order matters more than the count. IVR menu design comes down to two choices: what earns a place on the list, and what order the list plays in.

Put the highest-volume reason first, so the callers who want it never have to sit through the rest of the menu.

Two rules that save you trouble later:

Say the option before the key. “For account balances, press 1” lets the caller decide, then act. “Press 1 for account balances” makes them act, then reconsider.
Never read out an option the caller cannot use. If the accounts line is unstaffed on Fridays, the Friday menu does not offer it.

Keep the layers shallow as well as the list short. Count the key presses on the longest path through your flow, then compare that path with the worked example further down this page: if a common call reason sits deeper than that, it belongs higher up. Every extra level is another chance for someone paying for the call to give up before they arrive anywhere.

Step 3: How do you let a caller reach a person?

Build the route to a human before you build anything else. It is the branch every other branch falls back to.

One key, everywhere. Pick a single key (0 is a sensible choice) and make it reach a person from every menu and every submenu in the flow.
Say it out loud, early. Put the option in the first menu rather than only at the end. A caller who knows the way out exists will listen to the rest of the menu.
Catch silence and wrong keys. If someone presses nothing, or presses a key that does not exist, send them to a person after a second attempt rather than replaying the menu.

This is where the flow earns its trust. A menu that hides the way out teaches callers to press 0 the moment it starts, and you lose the self-service you built the menu for.

Step 4: Where does the call go once it is routed?

The menu choice is only half the decision. The other half is what your queue does with the call.

VoiceConnect gives you four queue routing strategies: Round Robin, Longest Idle, Skills-Based and Sticky Agent. Each one fits a different shape of team.

Round Robin sends calls to each agent in turn. Good for a team where everyone handles the same work.
Longest Idle sends the call to whoever has been free longest. Good for evening out load across a busy support desk.
Skills-Based matches the call to an agent’s skill, with proficiency levels for language, product and technical skill. Good when callers switch between English and a local language, or when one product needs specialist knowledge.
Sticky Agent returns the caller to the agent they spoke to last. Good for accounts, collections, and anything where repeating the whole story costs you the relationship.

Choose per queue, not per company. Sales and accounts rarely want the same behaviour.

Routing also decides what the agent sees when the call lands. If your flow captures an account number on the keypad, that value can travel with the call to the agent’s screen alongside the customer’s history — our guide to contact centre CRM integration covers how that connection is built.

Comparison of the four VoiceConnect queue routing strategies. Round Robin sends calls to each agent in turn and fits a team where everyone handles the same work. Longest Idle sends the call to whoever has been free longest and evens out load on a busy support desk. Skills-Based matches the call to an agent's skill, with levels for language and product, and fits callers who switch between languages. Sticky Agent returns the caller to the agent they spoke to last, which fits accounts and collections. A footer notes that an account number captured on the keypad can travel with the call to the agent's screen.

Step 5: What happens to calls that arrive after hours?

This branch is the easiest one to leave until last, and it is where callers quietly disappear. A line that rings out at 6pm teaches people not to ring you at all.

Decide three things:

What the caller hears. A recorded message that states your hours and the next time someone is available beats a ring that never ends.
What you offer instead. A voicemail box someone genuinely checks, a callback request, or an automated option that answers the common questions. Overflow inside working hours needs the same answer: the call nobody picks up at 11am is lost the same way as the one at 11pm.
When you call back. Name a window the caller can hold you to. “Before noon tomorrow” is a promise; “as soon as possible” is not. Start with the next working morning, then tighten it once you know how long your callback list actually takes to clear.

Put the business-hours switch in the flow itself rather than in a reminder to your team, so it fires on the holiday everyone forgot about.

If your after-hours volume is heavy enough to be worth answering rather than recording, AI voice agents can take those calls and hand off to a person when the conversation needs one.

When your team works through the callbacks, the outbound rules sit in the platform rather than in somebody’s memory: the dialling prefix, the permitted calling hours, a daily limit and a monthly cap apply to every call that leaves the system. How quickly that list clears also depends on the dialling mode behind it, and our guide to progressive, predictive and preview dialling sets out which mode suits which team.

Step 6: Write the prompts your callers will actually hear

Read every prompt out loud before it goes live. A sentence that scans on paper often runs long in the ear.

Lead with the option, not the greeting. Your company name and one line of welcome are fine. A brand statement in front of the menu is not.
One idea per prompt. If a prompt contains “and”, check whether it is really two prompts.
Match the language to the caller. VoiceConnect plays IVR prompts in any language, and it does that by playing an audio file you record and upload for each prompt. So a menu can greet in English and branch into a Twi, Ga or Ewe path where that is how your callers speak — schedule the recording, because every prompt on every language branch is its own file.
Say numbers the way people say them. Read an account number back in groups rather than as one long string.

Then test what you wrote on a real handset. Ghana has three mobile network operators, AT, MTN and Telecel, according to the National Communications Authority’s Q3 2025 bulletin, and the only way to know how your prompts land is to ring your own line from a phone on each of them.

A complete IVR call flow example you can copy

Worked IVR call flow examples are easier to adapt than rules are to apply, because they show the order the decisions land in.

Here is a full flow for a business running three lines (sales, support and accounts) behind one published number. Read it as a sequence, swap the call reasons for your own, and draw it on the sheet from earlier. If that published number is still to be arranged, our guide to getting a toll-free number in Ghana covers the NCA process and what to expect.

The flow, step by step

Flowchart of a complete IVR call flow. The call connects to a greeting, then a business-hours check. Inside hours the caller reaches the main menu, arranged in volume order, which branches to order status (keypad entry, then the status read back), support (queue on Longest Idle, callback offered on hold), sales (queue on Sticky Agent, back to the same person) and accounts (queue on Skills-Based, matched on language). Outside hours a recorded message states the opening time and offers a callback, the caller leaves a number on the keypad, and the request lands on a callback list worked at the start of the next business day. A green lane across the diagram shows that no input, or a wrong key, at any point sends the caller to the general queue and then to a person rather than back to the menu. A closing bar reads: every branch ends in a person, a completed answer, or a callback booked, and no branch ends in a loop.

Call connects. Greeting: company name, one line, no music.
Business-hours check. Inside hours, continue to step 3. Outside hours, jump to step 9.
Main menu. Four options in volume order: order or delivery status, support for an existing product, sales, accounts. The menu closes with “to speak to someone, press 0”.
Option 1, order status. Prompt for the order number on the keypad, read the status back, then offer three things: repeat it, speak to someone, or end the call.
Option 2, support. Route to the support queue on Longest Idle. The hold announcement gives the position in the queue and offers a callback instead of waiting.
Option 3, sales. Route to the sales queue on Sticky Agent, so a returning prospect reaches the person who already knows the deal.
Option 4, accounts. Route to the accounts queue on Skills-Based routing, matched on language.
No input, wrong key, or 0 at any point. Route to the general queue. After two failed attempts anywhere in the flow, the call goes to a person rather than back to the menu.
Outside hours. The message states the opening time and offers a callback request. The caller enters a number, the request lands in the callback list, and the team works it at the start of the next business day.
Every branch ends the same way. A person, a completed self-service answer, or a callback booked. No branch ends in a loop.

That last line is the test. Walk your own flow and find the paths that end nowhere.

If you also want to know how the flow lands with customers, a short question at the end of the call catches them while the experience is still fresh — our guide to IVR voice surveys covers when that works and when it does not.

You now have a flow on paper. Building it is the next step, and VoiceConnect’s visual IVR builder is where a flow like this one gets assembled, one action at a time, without writing code.

Four ways call flows go wrong after launch

IVR call flow design does not end at launch, and the routine that keeps a flow honest starts with a copy of what is already there.

Before you change a live flow, note down what is live now — a screenshot of each menu and each prompt is enough to put it back. Then make one change, ring the line from a phone on each network, and walk every branch, including the wrong-key path.

That is the routine. These are the four things it catches.

The hours change and the flow does not. A Christmas half-day, a new Saturday shift, a queue that moved teams. This is decay rather than bad design, and it is fixed by maintenance rather than by a redraw.
A branch loses its owner. Someone leaves, the queue behind option 3 empties out, and those calls ring into a room with nobody in it.
The menu grows. Every department asks for its own option and a short menu becomes a directory. Add a branch only by replacing one, or by pushing an older option down a level.
Nobody has called the line in months. Flows are not tested by the people who built them. They are tested by customers, and customers do not file bug reports. They stop calling.

Set a recurring date for that walkthrough and tie it to something that already happens: the first week of each quarter, or the day your opening hours change.

Two-part diagram on keeping a live IVR call flow honest. Across the top, the safe edit routine in order: copy what is live by screenshotting each menu and prompt, make one change at a time, ring the line yourself from a phone on AT, MTN and Telecel, then walk every branch including the wrong-key path. Below it, four things that routine catches: the opening hours change and the flow does not; a branch loses its owner when someone leaves and calls ring into an empty room; the menu grows into a directory as every department asks for its own option; and nobody has called the line in months, because customers stop calling rather than reporting the fault.

Can you change an IVR call flow without a developer?

Yes, and that answer decides whether everything above survives contact with a real month.

A flow that needs a developer for every edit will not be updated for a half-day closure. It gets updated once a year, and your callers pay for the gap in between. Whoever owns customer service needs to own the call flow.

With VoiceConnect you can build it yourself. A visual drag-and-drop IVR builder with more than ten flow actions covers the pieces this guide has walked through: spoken prompts, from text you type or audio you upload, keypad input, business-hours branching, connections to your own systems, and call recording.

That is what a no-code IVR builder buys you. The flow is assembled on screen by the person who understands the calls.

If you would rather not start from a blank canvas, Arkesel’s team can set the flow up with you during onboarding. Either way the flow stays yours to edit, so the opening-hours change you make on Monday morning is live on Monday morning.

Arkesel supplies VoiceConnect numbers and the network connection in Ghana, so the flow you draw runs on the networks your callers are already using. Plans are set out on the pricing page.

If the same requests also reach you over USSD, that channel carries its own screen limits and conventions — our guide to USSD menu design covers those separately.

Start on paper, finish in the builder

A caller never sees your platform, your queue settings or your reporting. They hear a menu, which makes IVR call flow design the part of your contact centre that every customer experiences and nobody in your team ever hears.

Draw your flow this week on one sheet of paper, then build it. See how VoiceConnect’s visual IVR builder works, or talk to the team about setting up your first call flow.