For years we ran campaigns for South African businesses and watched the same thing happen. The ads worked. The leads arrived. And then a good third of them simply evaporated between arriving and being answered.

Not because anyone was lazy. Because the person meant to answer was on a roof, in a patient's mouth, or in court. Because the enquiry came in at 20:40 on a Saturday. Because three quotes went out on Monday and ours was the second one.

You cannot fix that with more advertising. You fix it by putting something at the front door that never sleeps, never gets busy, and never forgets to follow up.

Why South Africa specifically

Most AI automation being sold here is repackaged from somewhere else — American playbooks, American assumptions, dollar pricing with a Rand conversion. It doesn't account for WhatsApp being the default channel, for load reduction, for medical aids, for POPIA, or for the fact that a South African customer can tell within one message whether they're talking to something local.

We're in Cape Town. We price in Rands. And we only take on four industries, because going deep in four beats being adequate in thirty.

What we're not

We're not a reseller with a white-labelled chatbot. We're not going to tell you AI will transform your business. And we're not going to put logos on the results page that aren't ours. If a R299 tool would do the job, we'll say so on the call — we'd rather lose the sale than take a fee for something that won't move.

Two things on this site collect anything at all.

The contact form, and Google Analytics. Nothing else asks you for a character and nothing else keeps one. The calculator, the pricing tables, the articles and all eleven tools in the Playground run in your browser and send us nothing about you.

The form

It will not send without a name and either an email address or a mobile number. That is not a dark pattern, it is arithmetic: without one of those we cannot reply, which is the only reason anybody fills in a contact form. Everything else is optional, and an empty field is sent as empty rather than guessed at.

• nameWhat to call you. Required.
• businessOptional. It changes the answer, so we ask.
• emailOne of these two is required.
• phoneThe other. A mobile, so we can answer on WhatsApp.
• situationWhich of five options sounds most like you.
• messageOptional, and usually the most useful thing on the form.
• slotOnly if you pick a time for a call. It goes into our diary.
• pageAdded by us: the page you were on when you pressed send.
• sourceAdded by us: the domain you were on, which is always this one.
• _gotchaA field you cannot see. Automated spam fills it in, a person never does, and anything arriving with it filled is thrown away.

Only the last three are not yours. page tells us whether you came from the pricing page or from an article, which is genuinely useful when we write back and useless for anything else. There is no tracking identifier anywhere in that form, nothing is read off your device, and nothing is remembered between visits.

Your IP address, when you submit

This is the part most privacy notices leave out, so it goes near the top instead. When the form is submitted, the system receiving it writes one row to a rate-limiting log: your IP address, one word for what happened to the request — accepted, agent_reply, lead_send, rate_limited, send_test or connection_test — and the time. That is the entire row, and none of it is typed by you: all four columns are derived, which is the opposite of the form fields above. It is what stops one machine firing a thousand submissions at us overnight, and without it the form would need a CAPTCHA, which is worse for you than this is.

What is actually in that log, written as it is rather than as it ought to be. It has been running since 1 August 2026, and it is smaller than the paragraph above makes it sound: of 589 rows, 492 are connection_test — a dashboard health check that was publicly reachable until we closed it on 29 September. That much you can still check, because the column it is counted from is untouched. The next three counts you cannot, and you should know why: they were taken on 6 November 2026 from the address column, which was erased the same day. The log held 85 distinct addresses, eight of which had ever produced one of the outcomes a visitor can actually cause, and two rows, from two addresses, were a visitor and nothing else. Those are also the three figures that flatter us most, so it matters that you can tell which claims on this page are checkable and which are being taken on trust. We would rather set it out that way than leave you reading the log as a list of everyone who has been here, because that is not what it is.

Every address in it has been destroyed. On 6 November 2026 the address column was overwritten for all 589 rows — 1 August to 1 November, the entire history of the log. Not shortened, and not hashed: erased, which means unrecoverable with or without a key, by us or by anybody else. No rows were deleted, so the counts and the dates still stand and the rate limiter keeps its history. What it no longer has is the addresses.

What has not changed is what happens the next time somebody presses send. Until the replacement is deployed, a new submission still writes its address exactly as it arrives. That is the live position today, and it is the one sentence on this page most likely to go out of date.

What replaces it is written and tested but not yet running, so it is set down here as a plan and not as a fact. The address will be turned into a keyed fingerprint as the row is written — HMAC-SHA-256, with a secret this website does not hold, stored as v1$ and sixty-four hex characters. That still catches one machine submitting a thousand times, because the same address always produces the same fingerprint, while being arithmetic nobody can run backwards into an address. Rows will be deleted automatically at twelve months, by a job that runs daily rather than when somebody remembers. That work belongs to the backend rather than to this website, and it will be described here in the present tense on the day it goes live, not on the day it was agreed. You should be able to tell a commitment from a fact on a page like this.

Reading the site logs nothing at all — it is pressing send that writes the row.

Something worth knowing before you type

The first reply you get is written by an agent, not by a person. That is the thing we sell, and demonstrating it on our own enquiries is rather the point — but it means the text of your message is read by a language model, not simply stored and forwarded. A person sees it as well, usually within the hour. If you would rather no machine ever read what you write, send it on WhatsApp or by email instead. The details are at the bottom of this page, and nothing here forces you through the form.

The paperwork, which is the part nobody checks.

Section 21 of POPIA says that if somebody processes personal information on our behalf, there has to be a written agreement obliging them to keep it secure. It is not a formality: the Regulator enforced exactly that point against Dis-Chem. So the fair question to ask us is not whether we say nice things about security, but whether those agreements exist for the three companies named above.

Each of them publishes one that applies to an ordinary account without being separately negotiated. Supabase’s data processing addendum forms part of its terms of service. Twilio includes SendGrid’s inside its own terms. Google’s data processing terms are accepted automatically for new Analytics accounts, which this property — created in October 2026 — is. That is what those companies publish, read on 6 November 2026.

Now the honest limits of that answer, because this is exactly where a privacy page usually starts overclaiming. It is what the providers publish, not a lawyer’s reading of our particular accounts, and a separately signed contract would override it. Analytics is the awkward one of the three: depending on the data-sharing settings on the account, Google can be acting in its own right rather than purely on our instruction, which is a different relationship with a different answer. And none of us writing this is a lawyer. What we can tell you is who handles your information and on what published terms. Anyone who tells you more than that about their own compliance is guessing in a confident voice.

It leaves South Africa, and POPIA has a view on that.

The database is a Supabase project in the us-east-1 region, which is Northern Virginia, in the United States. So from the moment you press send, your name, your contact details and the text of your message are stored outside the country.

Section 72 of POPIA sets conditions on sending personal information to a third country, and section 18 says you are entitled to be told that it is happening. You are being told. We are not going to dress it up as a feature: it is where the system we already run happens to live, a South African region is available from the same provider, and moving it is on the list.

The database is not the only part of this with an American provider, so it would be misleading to leave it there. The notification email is carried by SendGrid, a Twilio company, and it lands in a Google Workspace mailbox. The accurate summary is therefore not “one offshore database” — it is that an enquiry sent through this form is handled by American providers from the moment you press send.

What we can tell you is the shape of it: every provider in the chain is named on this page, there is no onward sub-processor we have not listed, and access at our end is limited to Awake AI’s own people. If your business has a policy against its enquiries sitting offshore, say so in the first message and we will tell you straight what we can and cannot keep in the country, which for a website enquiry today is not much. The fix is moving the database to the South African region the same provider already offers, and that is on the list rather than done.

Analytics, and the cookie banner that is deliberately missing.

Google Analytics 4 runs on every page of this site, property G-YDVZ6VK0VX. A Google Tag Manager container, GTM-KNT6JJLN, is installed beside it and currently holds no tags whatsoever — it is there so that an advertising pixel can be added later without re-cutting the site. The day one is added, this paragraph changes.

What Analytics gets is the ordinary set: which pages you looked at and in what order, roughly where in the world you are (worked out from your IP address by Google, and not stored by us), what device and browser you are on, and whether this is your first visit or your fifth. That last one needs two first-party cookies, and they are the only reason this site sets any.

Three events are reported by name. generate_lead when the form is sent, book_appointment when a call is booked, and contact_click when you tap a WhatsApp, phone or email link anywhere on the site. The third is the one worth spelling out: we record that a WhatsApp tap happened, on which page, and the words that were on the button. We do not get your number, and we never see the message you type afterwards. What you say on WhatsApp is between you and whoever reads it at our end.

Why there is no banner

There is no cookie dialogue on this site, and that is a decision rather than an oversight. POPIA governs us, not the GDPR, and POPIA does not require a click-through consent box for analytics the way the EU’s cookie rules do. Beyond that, a banner would be the first thing a visitor meets on a site whose entire argument is that we do not put obstacles in front of people — and a box everybody dismisses in a quarter of a second collects a click, not a decision.

The straight version of what that means for you: measurement starts on the first page you load and you are not asked first. If you would rather it did not, block it. Any ad blocker, or a browser with tracking protection switched on, will stop it; every analytics call on this site is written to carry on quietly when the tag is missing, so nothing you can see will break. We would rather tell you how to turn it off than put a box in your way and call it permission.

One thing would change this. If we ever point Google Ads at visitors in the EU or the UK, consent rules apply that POPIA does not, and a banner goes up. We have not, and this page will say so on the day we do.

How long we keep it, and what we never do with it.

Twenty-four months for an enquiry that never turned into work, set on 6 November 2026. Sooner whenever you ask, which takes one email and no reason. If you do become a client, your information stays while we are working together and then for whatever period the tax and companies legislation obliges us to keep records of the work.

And now the part these pages usually leave out. Nothing deletes anything automatically yet. There is no scheduled job quietly clearing out enquiries at twenty-four months, so for the moment that period is a commitment kept by hand, and a deletion request is what actually makes it happen on the day. It is the same gap as the IP log further up and it is being closed the same way. We would rather you knew which line on this page is enforced by code and which is enforced by us remembering.

The list of things we do not do is short and absolute. We do not sell your information. We do not share it with advertisers, data brokers or lead marketplaces. We do not pool one client’s data with another’s. And nobody outside Awake AI’s own people and the providers named on this page can reach it.

The mailing list deserves its own line, because it is the promise most often broken quietly. Enquiring does not put you on one. That is not a new sentence written for this page: the contact page has answered “Will I get put on a mailing list?” with “No. What you send is used to reply to you and nothing else” since the site went up, and there is no consent checkbox anywhere on this site to have pre-ticked in the first place. The law agrees with us rather than the other way round — section 69 of POPIA makes electronic direct marketing opt-in in South Africa, so an enquiry is not permission and an unsubscribe link at the bottom would not turn it into one. If marketing ever arrives from us, it is because you asked for it.

If something does go wrong, you hear from us in plain language with what we know and what we do not know yet, and we notify the Information Regulator where the Act requires it. We are not going to promise that nothing can ever go wrong, because nobody honest can.

Who to talk to about any of this.

Awake AI Automation & Development, Cape Town, Western Cape, South Africa. byron@awakeai.co.za, or WhatsApp +27 64 543 1411. Both reach the same person, and he is the one accountable for everything on this page.

Byron owns the business, which under POPIA makes him its Information Officer: the person answerable for what happens to your information, and the one the Regulator deals with.

We do not publish a street address, and the reason is worth saying out loud. There is no office you could visit — we work at your premises or remotely — and the registered address is a house. Printing somebody’s home address on a public page to make a company look more solid is not a trade we are willing to make. The two routes above are not a switchboard; they are the actual person.

This page covers what this website collects from you. What happens to your customers’ information when we run an agent inside your business is a different question with a different answer, and it has its own page: POPIA & your data.

Most of the AI automation sold into Cape Town was designed somewhere else. That is not a complaint about quality — a lot of it is good software. It is that the assumptions underneath it were made for a market where people email, where the power stays on, where one language is enough, and where GDPR is the law that matters. None of those four hold here, and the gap shows up in the places that cost money.

What we build, and who for

AI agents that answer your enquiries — on WhatsApp, on the phone, on your website and in your inbox — within seconds, at any hour, in your own words. They answer what they can, ask what they must, book the job in your diary, and hand you anything that needs a person. We also build the unglamorous half: the quoting, the invoicing, the follow-up that never happens and the re-typing between systems that eats a week.

The clients are small and mid-sized businesses across the city and the province — the CBD and Foreshore, the Southern Suburbs, the Northern Suburbs and Durbanville, the Atlantic Seaboard, Somerset West and the Winelands, and up the West Coast. Trades, professional services, practices and hospitality, mostly. If your enquiries arrive faster than people can answer them, that is the problem we work on.

Why a Cape Town business loses the enquiry

Rarely on price. Almost always on silence. The message lands at twenty to eight on a weeknight or halfway through a Saturday, nobody sees it until Monday, and by Monday the customer has three quotes and a date booked with whoever replied first. Nothing about that was a pricing decision.

Two local things sharpen it. The first is the channel: this is a WhatsApp market, and a WhatsApp left unanswered for two hours reads as a business that is closed or does not want the work. The clock a customer runs on WhatsApp is not the clock an email runs on. The second is power. Load reduction still cuts supply across overloaded suburbs through the morning and evening peaks, and the evening peak is exactly when domestic enquiries arrive. An agent hosted properly keeps answering when your office cannot.

We have written up what the response-time research actually says — including what it does not claim, and why most of it describes a market that is not this one.

What it costs

It is on the page, in Rands, like everything else we sell. AI reception starts at R2 450 a month, the full front desk at R5 900, and custom builds are scoped after a paid discovery phase rather than guessed at. The full price list is published because anybody hiding their pricing is telling you something.

Before any of that, there is a week-long audit that counts what actually reaches you and what gets answered, and puts a Rand figure on the gap using your numbers rather than ours. It is the cheapest thing we sell and it regularly ends the conversation, because a business already answering nine enquiries in ten inside ten minutes does not need us.

What is genuinely different about building here

Four things, and they are the reason imported playbooks underperform rather than fail outright. WhatsApp is the channel rather than a secondary one, so an agent has to be good there first and everywhere else second — including voice notes, which are normal here and which a surprising number of tools still cannot handle.

Language is not a translation setting. A customer who opens in English, slips into Afrikaans for a sentence and back again is not an edge case in this city, and an agent that resets or answers in the wrong one reads as foreign. Seasonality is sharper too: hospitality here has a December and January that arrive whether or not anybody is staffed for them, and the trades have a winter of geysers and leaks that does the same thing in reverse.

And POPIA governs the personal information arriving in every one of those conversations. It is not GDPR with the names changed, the transfer conditions bite the moment a supplier processes offshore, and the Information Regulator enforces it rather than the supplier’s terms of service. We set out the plain version in our POPIA guide and what we ourselves do with data on our POPIA page.

Why being local matters, and when it does not

It matters for the things that need a room. A workshop where your team argues about what the agent should say is better in person, and the first fortnight of corrections goes faster when somebody can come and sit with the person actually fielding the calls. It matters for invoicing in Rands and for being in the same time zone when something breaks at five to five.

It does not matter for the software. Anyone telling you that AI built in Cape Town is technically better than AI built in Berlin is selling geography. What is actually different is the design decisions — which channel comes first, which law applies, what happens when the power goes — and a supplier anywhere could make those correctly if they understood the market. Most do not, which is the real argument, and it is a smaller one than it sounds.

We work with clients outside the country too, and we invoice some of them in dollars. Being here is a reason to trust the design, not a reason to pay more.

How to check us before you spend anything

Open the Playground. It runs real working agents in your browser with no form, no email address and no “book a demo to see the demo”. If what you see there is not better than what you have, there is nothing for us to talk about.

Then read the thing that argues against us: when a cheap subscription chatbot is genuinely the better buy, including the thresholds that rule us out. Most small businesses in this city sit under at least one of them.

If you still want to talk, book a call or send a WhatsApp and start the clock on us. Seeing how quickly we answer is a more useful test than anything on this page.