Build your own AI receptionist, or buy one

You can build an AI receptionist yourself, and the parts are cheaper than most people expect. The bill depends on the voice, reasoning service, phone network and hosting you choose. That is not the hard part, and the price is not what should decide this.

The hard part is everything that happens after the call works.

The five parts you have to assemble

A voice agent that answers a phone is five services in a row, and each one is a bill.

1. A number and the telephony. Something that answers a South African number and turns the call into audio your code can read.
2. Speech recognition. Turning the caller's audio into text, fast enough that the pause does not feel wrong.
3. A language model. Deciding what to say next, with your prices and your rules in context.
4. A voice. Turning the reply back into audio that a stranger will listen to without hanging up.
5. Orchestration. Holding the turn, handling interruptions, knowing when the caller has finished talking, and cutting the model off when they start again.

Platforms exist that bundle three, four or all five. That is the market you are shopping in when you look at the developer tools, rather than the receptionist products.

What the parts actually cost

Price the complete path from the phone network to the spoken reply. A platform fee may leave the voice, reasoning, phone number and network charges to separate suppliers.

Make a list of every bill, then check each provider's current rate card. Note the billing unit, currency, minimum spend and any extra charge for several calls at once. Ask whether silent time, ringing and transfers count.

Do not compare a raw speech price with a finished service. The cost of hosting, monitoring, storage, testing and support is part of running it too. Use a small trial to measure actual usage before projecting a monthly bill.

The worked example

Start with a forecast of 1,000 connected voice minutes a month. For each supplier, multiply its applicable rate by the expected use, then add monthly fees and number rental. Convert foreign bills using a realistic rate and include payment fees.

Next, put a value on your own time. Include building the first version, testing each booking action, fixing failures and keeping it working when a provider changes something. A working demo is not yet a service your customers can rely on.

Compare that total with a finished product. Municate Pro includes 1,000 voice minutes for R2,495 a month, with R3.00 per extra minute. Assisted setup is optional. The pricing guide explains how to compare the monthly fee and usage together.

Building can still be right for you. The question is whether the control or specialist workflow is worth the time and ongoing responsibility.

What the per-minute price does not buy

A demo is only the start. The work below is part of running a dependable service, and none of it appears on a pricing page.

• A playbook that survives contact with real callers. Your hours, your prices, your service area, what you do not do, and the forty edge cases you discover in week three.
• Handover to a person. Not just a transfer. Knowing when, warm context so the human is not starting cold, and what happens when nobody picks up.
• What it does when it does not know. The difference between a system that says so and one that guesses is the difference between a useful tool and a customer booked for the wrong service on the wrong day.
• Where the conversation goes. Structured into a diary or a CRM, not a transcript nobody reads.
• Recording, retention and erasure. You are the responsible party under POPIA. That means knowing where recordings live, how long you keep them, and being able to delete one when a customer asks. Ask about the full data flow and agree retention before switching it on.
• Somebody to phone at 22:00 when it breaks. If you built it, that person is you, on a Saturday, while the calls go unanswered.

When building it yourself is the right call

Be honest about which of these is true for you.

• You are a developer and this is the product. You are not building a receptionist, you are building a business. Then obviously build it.
• Your call flow is unusual. Something no product handles, wired deep into systems nobody integrates with.
• You have real volume. At tens of thousands of minutes a month, the margin between wholesale and retail starts to justify an engineer.
• You enjoy it and the phone is not urgent. A legitimate reason, as long as you say it out loud rather than dressing it up as a cost decision.

When it is not

If you run a business that is not a software business, and your phone is already ringing unanswered, building this is the expensive option. Not because the parts cost more, they do not. Because the thing you are short of is evenings, and this will eat them.

The tell is simple. If you are reading this to work out whether you can save R1,500 a month, the answer is that you probably cannot, and the attempt will cost you more in missed calls than the subscription would have.

Where Municate fits

Municate gives your business an AI team for calls and messages, with shared customer records and a handover to your people. Your business sets the answers, the work it may do and when it should bring a person in. Booking actions depend on the systems connected during setup.

Pro is R2,495 a month for the organisation, including 1,000 voice minutes. Extra voice minutes cost R3.00 each. Max is R5,995 with 3,000 pooled minutes, then R2.50 a minute. Unlimited agents are included; Sales Copilot is a separate add-on. These are the prices from our 12 November 2026 plan brief, with no VAT added.

Set up Pro yourself for free, or choose assisted setup for R1,000. Assisted Max setup is R3,000. See the full plans and add-ons for the included numbers, email replies and call capacity.

Customer records are stored in Johannesburg. Some speech and AI processing uses providers abroad, so ask about the full data flow, retention and permissions when setting up.

Book a free consultation to talk through your needs, or try the demo to hear how your AI team could sound.