Customer case study. A real AskMandla household, from the WhatsApp thread, June to August 2026.
An employer in Gauteng found us on Instagram in June 2026. Her domestic worker had been with her about 15 years, with no contract and no records she could put her hands on. Her worker also had no smartphone, no street address, and limited English. Every part of a WhatsApp-first product should have failed here. It took seven weeks instead of ten minutes, and it got done.
Her first question is the one everybody asks
"If I've had someone working for me for years how is the UIF worked. From today or from when they started with me."
The answer is that you can register now and catch up. UIF arrears can be declared and paid for years already worked. Nobody is fined for arriving late with a backlog, and she asked twice more over the following weeks about back-paying the years that were never paid, which is exactly the right instinct.
She also asked, plainly, what she would be paying: "I just want to be clear. I pay R 450 set up fee. Then R 49 per month. Then I pay you her salary and you pay her. Where does the UIF payment come from?"
Yes, and the UIF contribution comes out of the top-up alongside the salary, shown as its own line. Her worker's 1% and the employer's 1%, on the payslip, going to the fund.
No smartphone, no WhatsApp
On 2 July she wrote: "My domestic worker is at work and we need to complete our registration. She does NOT have a smart phone. Are you able to assist her via my Watapp?"
A WhatsApp-first service has to have an answer to this, because a good share of domestic workers do not have a smartphone. Ours is that a person picks up the phone. Our Customer Success lead called the worker directly, on her own basic phone, and took her through it by voice.
Then the language barrier: "We are battling with a language barrier. This may take a while. Please be patient. She has questions."
She had questions, and one of them showed why this call mattered: "Ok seems she thought we were talking about pension. Not UIF." Her worker had understood the whole conversation to be about a pension. If nobody had spoken to her, she would have signed a contract about something she had misunderstood.
Her employer was clear about the standard: "I don't want her to sign without understanding."
That is the right standard, and it is ours too. A contract signed by someone who did not follow it is not worth the paper.
No street address either
Her worker lives in a township without street names or numbers. She has a PO Box.
That is a real problem for a system that wants an address, and it is extremely common. We took the postal address. A worker with no street number is not less employable, less registerable or less entitled to a contract. If a form cannot cope with her, the form is wrong.
How her payslips actually reach her
Her worker's daughter has a smartphone. With the worker's agreement, her WhatsApp is where the payslips and documents go, and her employer confirmed the arrangement with the daughter before anything was sent.
We would rather a worker receive her own payslip on her own phone. Where she cannot, a family member she chooses is the next best thing, and it beats the alternative, which is her having no record at all.
Two other things she needed changed
Her payday is the 27th, not the 25th. "I can't do the 25 th. I only get paid on the 27th." Her worker's pay date moved. This comes up constantly and there is no extra charge for it.
She wanted the contract amended. She asked for a copy to read first, sent her amendments by email, and our Chief Legal Officer made them. The contract is a starting point, not a take-it-or-leave-it.
Where we were slow, since this is a case study and not an advert
This took seven weeks. Some of that was unavoidable: her worker was only at the house on Thursdays, so anything needing the two of them together moved in weekly steps.
Some of it was us. She asked for updates on 7 July and again on 16 July. The amended contract took longer than it should have, and she followed up twice. Her invoice went missing in email more than once, and on 13 August she had to write: "I really want to pay my registration. Any chance of getting and invoice before the end of the month please... otherwise it will appear that I am in default. I really do t want that."
A customer chasing us to let her pay us is our failure, not hers. It is in this case study because it happened.
Where it ended
Signed contract, UIF lodged with back-pay in hand, payday moved to suit her, and payslips going to a phone her worker's family controls. On 17 August, checking her worker's banking details: "Thanks. Great service as always."
What this cost
R450 once-off onboarding for the worker, then R49 a month. The phone call to her worker, the voice explanation, the contract amendments and the postal-address workaround were not extras. They are what the fee is for.
If your worker has no smartphone, no fixed address, or does not read English comfortably, say so at the start of the chat. It is a normal case, not a hard one.