Getting AI to answer a customer is the easy part. The hard part, and the part that decides whether it helps or embarrasses you, is the integration: connecting the AI to the places your customers already write, the systems that hold your answers, and the people who need to take over when it should stop. This guide explains how AI integration works in plain terms: how an AI agent connects to WhatsApp, email and a website chat, how it plugs into Google Sheets, Airtable, a CRM or a calendar, what it should and should not be allowed to do, what it costs in South Africa in 2026, and a planner to size your own build. IT-Support-SA builds these systems from Pietermaritzburg for businesses across KwaZulu-Natal and the rest of South Africa.
The Short Answer
An AI integration has four parts: a channel the customer writes on (WhatsApp, email or a website chat), a brain trained on your own prices, policies and tone, tools it can use inside your systems (a log, a CRM, a calendar), and a handover that passes the whole conversation to a person when it matters. Connect them through the official routes, give the AI only the access its job needs, keep people in any decision that commits money, and log everything. If you are deciding what to automate before how, start with our guide to what to automate first.
The Four Parts of an AI Integration
It helps to picture one customer message travelling through the system:
- The channel receives it. A customer sends “Do you have a 10:00 slot on Thursday?” on WhatsApp. The channel connection hands that message to the AI, and carries the reply back.
- The brain works out what they want. The AI is trained on your business: services, prices, opening hours, policies and how you speak. It does not guess from the internet. If the answer is not in what it was given, it should say so.
- The tools do the work. To answer that question the AI looks at your calendar. To book, it writes to it. To remember the customer, it saves a contact in your CRM or a row in a log.
- The handover catches the rest. If the customer is upset, asks for a person, or raises something the AI must never handle, it stops and passes the full conversation to a staff member.
Everything below is about how those four parts connect, and what to put in place so each one is safe.
Connecting to WhatsApp
For most South African businesses, WhatsApp is where customers actually are, so it is usually the first channel to connect. There are two very different ways a business can use it:
- The WhatsApp Business app is free and made for one phone. It suits a small team answering by hand, with quick replies, labels and an away message. It is not built for software to plug into.
- The WhatsApp Business Platform (often called the WhatsApp Business API) is made for software to connect to. It is what lets an AI agent, a shared inbox and your other systems all work on the same conversations. It is accessed through an approved provider.
If you want AI answering customers, you need the platform. A few things are worth knowing before you start:
- Use the official route. Unofficial tools that imitate a phone can get a number blocked, and you may lose the number your customers already know.
- Plan the number. The cleanest set-up is a number dedicated to the platform. Talk to your provider about moving an existing number rather than assuming it can simply be switched.
- Customer-started conversations are the easy case. When a customer messages you, you can generally reply freely for a short window afterwards. Messages your business starts outside that window, such as reminders or follow-ups, generally need a pre-approved template.
- Keep marketing separate from service. Answering someone who wrote to you is service. Broadcasting a special to a list is direct marketing, which under Section 69 of POPIA needs opt-in consent.
- Check Meta’s current rates. WhatsApp charges for some categories of message, and its rate card changes, so confirm the current pricing instead of relying on an old figure.
A tap can also start the conversation. An NFC card or tag can open a WhatsApp chat with the message already filled in, which sends repeat orders straight to the AI. Our guide to NFC for takeaways and restaurants shows how.
Connecting to Email
Email is the second channel, and the right one for quotes, supplier queries and anything long. The AI connects to one shared mailbox, such as info@ or sales@, through your Microsoft 365 or Google account’s own permissions. That matters for two reasons: the access is limited to that mailbox, not everyone’s, and you can withdraw it at any time from your own admin settings.
What the AI does with the mail is a choice you make per type of message:
- Reply automatically to routine questions where the answer is certain, such as opening hours, prices on a list or a booking confirmation.
- Draft a reply for a person to approve for anything with money, a promise or a customer you care about.
- Do nothing but file it for messages it should not touch, such as invoices from suppliers or legal notices.
If your email runs on Microsoft 365, the licence you have affects what is possible. Our comparison of Microsoft 365 Business Premium and Standard explains the security features that matter when you let any software into a mailbox.
Connecting a Website Chat
A website chatbot is the third channel: a chat window that answers visitors at 22:00, captures their details and routes the enquiry. It is the most visible part of the build, so it is worth doing last, once WhatsApp and email are behaving. It should feed the same brain and the same log, not become a separate system with its own answers. Otherwise the website says one thing and WhatsApp says another.
Connecting Your Business Systems
This is the step that turns an AI that talks into an AI that works. Each system you connect lets it do one more job:
- Google Sheets or Airtable as a log. Every conversation becomes a row: who, what they asked, what the AI did and whether it was resolved. This is the simplest and most useful connection, and it is the one that shows you what to improve. Airtable also gives a proper management view, with open, escalated and resolved queries side by side.
- A CRM so a new enquiry becomes a contact and a deal, with the details the AI collected already filled in. Nobody retypes a lead again.
- A calendar or booking system so the AI can offer open slots and confirm bookings, with a person able to override.
- Accounting software, where your package allows it, so the AI can look up whether an invoice has been paid. Read-only is the sensible default: the AI looks, it does not change a ledger.
Each connection has the same rule: give the AI the smallest access that lets it do its job. A system that only needs to look something up should be read-only. A system the AI writes to should be one where a mistake is easy to see and easy to undo. If a tool does not have a ready connection, or the logic is specific to your business, the missing piece is a small piece of custom software, which our guide to custom software development for South African businesses covers.
Plan Your Own Integration
Choose the channels, systems and tasks you have in mind and set your monthly query volume. The planner shows which package it points to, why, how long it usually takes and the order the connections are built in.
The start-up selection describes a typical small business that wants WhatsApp and email together with a log, routine questions, lead capture and reminders. Notice what moves the package up: a second channel, a CRM, calendar or accounting connection, booking or quoting, a website chat, or simple volume. Adding a Google Sheets log on its own changes nothing. The result is a guide, and the real scope is set on a discovery call once someone has looked at how your queries actually arrive.
What the AI Should and Should Not Be Allowed to Do
Connecting systems is also where a project can go wrong, because an AI with access can act. Decide in advance which actions are open to it:
- Allowed on its own: answer from your approved information, ask qualifying questions, save a lead, offer open slots, send a reminder on a schedule you set.
- Allowed with approval: send a quote, change a booking that is already confirmed, reply to a supplier or a high-value customer.
- Never: issue a refund, give a discount, change credit terms, give medical, legal or financial advice, or handle a complaint beyond recognising it and escalating.
Three habits make that list work in practice. Make the handover immediate and complete, so the person who takes over sees the whole conversation and nobody asks the customer to start again. Make the AI say what it is, in the first message, so no customer feels misled. And make every action logged, so that if something is wrong you can see what was said, to whom and why.
POPIA and Security When You Connect Systems
Every connection is a place where personal information moves, so POPIA applies to all of them. In practice:
- Know where data is processed. Many AI services run outside South Africa, and Section 72 of POPIA sets conditions for transferring personal information across borders. Your supplier should be able to say where it goes and on what basis.
- Collect only what the job needs. An order query needs an order number, not an ID number.
- Keep people in significant decisions. Section 71 restricts decisions with substantial effects on a person being made purely by automated means.
- Protect the connections themselves. Access keys belong in a secure store, not in a spreadsheet or a chat. Access should be revocable, and the accounts the AI uses should have the minimum rights.
- Be able to show what happened. A log of messages and actions is what you need if a customer asks.
Our POPIA IT compliance checklist covers the wider obligations that apply to any system holding customer data.
What a Build Actually Looks Like
A properly run integration follows the same order every time, because skipping a step is how projects fail:
- Discovery. Map how queries arrive today and find the repetitive, high-volume ones.
- Connect and train. Connect the channels and systems, and build the knowledge base from your prices, policies, FAQs and tone.
- Set the rules. Decide what the AI may do alone, what needs approval and when it must hand over.
- Pilot for 30 days. Run real queries with a person checking its work.
- Go live with the log and dashboard running, then monitor and retrain monthly as your prices and policies change.
The timelines we work to are about two weeks for a single channel, three to four weeks for WhatsApp and email together, and six to eight weeks for a full build with a website chatbot and branded portal, including testing.
What AI Integration Costs in South Africa in 2026
Our AI integration service runs on three packages, all priced as from-prices:
- Starter: from R12,500 setup plus R2,000 a month. One channel, WhatsApp or email, and a Google Sheets or Airtable log, for under 500 queries a month.
- Business: from R28,000 setup plus R4,000 a month. WhatsApp and email together with an Airtable management portal and a monthly review, for 500 to 1,500 queries a month.
- Enterprise: from R60,000 setup plus R7,500 a month. Everything in Business plus a custom branded portal and a website chatbot, for 1,500 or more queries a month.
The setup fee pays for mapping, connecting and training the system. The monthly fee covers hosting, AI usage, monitoring and retraining. WhatsApp’s own message charges, where they apply, come from Meta and change over time, so they are worth checking separately. To see what routine queries are costing you today, use the calculator in our guide to what to automate first.
Mistakes That Make Integrations Fail
- Using an unofficial WhatsApp tool and losing the number.
- Giving the AI more access than it needs, so a mistake can reach systems it should never touch.
- Connecting everything at once instead of one channel and one log first.
- A chatbot with its own answers, separate from WhatsApp and email, so customers get different replies in different places.
- No handover, so a customer is stuck in a loop or has to repeat themselves.
- Letting the AI send quotes or promises unreviewed.
- Leaving it untouched after launch while prices, stock and policies change.
- Not asking where the data goes. Under POPIA you need to know.
Conclusion
AI integration is not a clever chatbot bolted onto a website. It is a set of careful connections: the channel your customers use, a brain that knows your business, the tools it is allowed to touch, and a person ready to take over. Start with one channel and a log, add systems one at a time, give the AI the least access it needs, and keep people in anything that commits money.
If you want to see what that would look like for your business, our AI integration service starts with a free discovery call, or WhatsApp us and tell us how your enquiries arrive today. IT-Support-SA builds POPIA-compliant AI systems for businesses across Pietermaritzburg, the KZN Midlands, Durban, Ladysmith, Johannesburg, Cape Town and all 9 provinces of South Africa.