How to set up a call center in Ethiopia

To set up a call center in Ethiopia, decide what the line is for, get a phone line from Ethio Telecom, choose where the system runs, size your team, design a short voice menu, plan for missed calls, and agree on the three numbers you will watch every day. Then test it all with real calls before you announce the number. This guide walks through each step in that order, with the questions to settle at each one.

1. Decide what the line is for

Start with one sentence that says why customers call you. Everything else follows from it.

Most lines in Ethiopia fall into one of three types:

Orders. Customers call to buy or book something. Speed matters most, and every missed call is a lost sale. Delivery companies, pharmacies and restaurants are in this group.
Support. Customers call about something they already have: an account, a delivery, a bill. Callers can wait a little longer, but they expect the agent to know their history.
Hotline. The public calls for information or to report a problem. Volume can jump without warning, and many callers call only once.

Write down the hours the line must be open, the languages your callers speak, and what a good call looks like. For an order line, that might be “the order is placed and confirmed in under four minutes”. For a hotline, it might be “the caller gets the right answer or a reference number”.

If the line serves more than one purpose, plan a separate queue for each. Orders and complaints should not wait in the same line.

2. Get a phone line

You need a way for calls to reach your system. For a call center with several agents, that is usually a SIP trunk from Ethio Telecom.

Ethio Telecom offers a SIP service for businesses, delivered over VPN and internet connectivity, on a postpaid basis. Source: ethiotelecom.et A SIP trunk carries many calls at once over a data link, so several agents can talk to customers at the same time on the same published number.

To start, call Ethio Telecom’s enterprise customer service line on 980. Source: ethiotelecom.et Ask Ethio Telecom’s enterprise team for the current document list and prices.

When you talk to them, have these answers ready:

How many calls you expect to handle at the same time at your busiest hour.
Which numbers you want callers to dial, and whether you keep an existing number.
Where your call center system will run, so the link can be delivered there.

A very small team can start with ordinary phone numbers and move to a SIP trunk later. If you expect to grow past a few agents, starting on a SIP trunk saves you a second move. Our guide on how to get an Ethio Telecom SIP trunk covers the questions to ask in more detail, and the page on connecting an Ethio Telecom SIP trunk to a full call center explains what the system side needs.

3. Choose where the system runs

Your call center system runs either in the cloud, on servers you rent by the month, or on your own server, in your office or in a data centre. Both work. The right choice depends on where you want your data to live and who will look after the server.

Question	Cloud	Your own server
Where calls and recordings are kept	On the provider’s servers	On a server for your company alone
Who looks after the server	The provider	You, or the company that installs it
How you pay	Usually a monthly fee per agent	Usually a licence and setup, plus the server
What you need on site	Internet for agents	Internet for agents, and a place for the server
Where the phone line connects	To the provider’s servers	To your server

Questions to ask before you choose:

Where will recordings be kept, and for how long? Banks, clinics and public offices often have rules about this. Ask your own legal team what applies to you.
What happens when the internet link is down? Agents in the office need a working link in both cases. Ask what callers hear while it is down.
Who do you call when something breaks? Get a name, a phone number and the hours they answer.
How do backups work? Ask where backups are stored, how often they run, and when a restore was last tested.

4. Size your team and shifts

Count the calls first, then the people. Guessing the other way round leads to long waits at lunch and idle agents in the afternoon.

If you already take calls, look at a normal week and count calls in each hour of each day. If you are new, estimate from your orders, tickets or visitors, and plan to adjust after the first month.

A simple way to size each hour:

Take the number of calls you expect in that hour.
Multiply by the average call length in minutes, including the time an agent needs after the call.
Divide by 60. That is the number of agents busy full time.
Add at least 20 to 30 percent, because calls do not arrive evenly and agents need breaks.

For example, 90 calls in an hour at 4 minutes each is 360 minutes of work, or 6 agents busy full time. Plan 8 for that hour.

Then build shifts around the busy hours. Many Ethiopian lines see a peak in the morning and another around lunch. Stagger lunch breaks so that the floor never empties at once, and keep one experienced agent on every shift who can take hard calls. Name a supervisor for each shift, even if that person also takes calls.

A voice menu, or IVR, greets the caller and sends them to the right queue. Keep it short. Callers who hear a long list of options hang up or press zero.

Good rules for a first menu:

Greet in one sentence, with your company name.
Offer the language choice first if you serve callers in Amharic and English, or play Amharic first and offer English as an option.
Use three or four options at most. Put the most common reason for calling first.
Say the option, then the key. “For orders, press 1” is easier to follow than “Press 1 for orders”.
Plan what happens outside open hours. Play your hours and offer a callback or voicemail.
Plan for public holidays. Record a holiday greeting for days like Genna on 7 January and Timket on 19 January.

Record the prompts with one voice, in a quiet room. Our guide on how to record IVR prompts in Amharic shows how, with example lines, and the page on Amharic voice menus shows how a menu is built step by step.

6. Plan missed calls and callbacks

Some calls will be missed, even in a well-run center. What matters is what happens next.

A missed call is any caller who did not reach an agent: someone who hung up while waiting, called after hours, or left a voicemail. Each of these is a customer who wanted something from you.

Decide now:

Who calls them back. One shared list that any free agent can work from is easier to manage than personal lists.
How fast. Set a target, such as “every missed call is called back within 30 minutes in open hours”.
When a callback is done. Count it as done when you reach the customer, not when you try once.
What callers hear when the wait is long. Offering a callback instead of a long wait keeps the queue moving and the caller calm.

The page on missed call callbacks shows how missed calls can become tasks on one shared list.

7. Measure what matters

Pick three numbers and look at them every day. More numbers can wait until these are under control.

Service level. The share of calls answered within a target time. A common starting target is 80 percent of calls answered within 20 seconds. Pick a target you can reach, then raise it.

Abandoned calls. The share of callers who hung up while waiting. If this number rises, check your staffing for that hour before anything else.

Callbacks closed. The share of missed callers you reached again, and how long it took. This number tells you whether missed calls are being won back or forgotten.

Show these numbers where the team can see them, on a screen on the wall or a shared dashboard. A live call center wallboard lets supervisors react while the queue is building, not the next morning.

8. A launch checklist

Before you publish the number, go through this list with the person who will run the floor.

The SIP line is delivered, and test calls in and out work from several mobile networks.
The caller ID that customers see on outgoing calls is your number.
Each agent can log in, answer, hold, transfer and end a call.
The voice menu plays correctly in every language, and each option reaches the right queue.
Out-of-hours and holiday messages play at the right times.
Missed calls, voicemails and callback requests reach the callback list.
Recordings are saved, and the right people can find and play them.
Supervisors can see the queue and agent status live.
Backups run, and you know who to call if something stops working.
Agents have practised with role-play calls for at least one full day.

On launch day, keep a supervisor on the floor for the whole day and review the three numbers from step 7 at the end of it.

How Halo and Skynet do this

Halo is call center software built in Addis Ababa and built for Ethio Telecom SIP trunks. It runs on your own server or one from Skynet VISP. Setup by Skynet covers the install and licence with backups, the Ethio Telecom SIP line connected and tested, the first voice menu, queues, agent accounts and hours, and hands-on training in Addis Ababa. Missed calls and voicemails become callback tasks that close when the customer is reached, and the wallboard shows the floor live.