Your Chatterbox® answers customer questions, sends payment reminders and handles the replies. It works from your organisation’s information and rules. When someone needs personal help, your team receives the conversation and what needs their attention.
Your knowledge. Your rules. Your Chatterbox.
A free, private Preview using your website or approved documents.
Customer questions arrive while your team is busy. Payment follow-ups still have to get done, and the replies need attention too. Your Chatterbox handles those conversations using your information and rules, and passes the requests that need a person to your team.
One monthly fee for the whole job, not a charge per call, message or account. Quoted on the scope of the job before you commit.
Customer service
Questions and requests arrive after hours and during busy periods, even when your team is already helping someone else.
Your Chatterbox answers from information you approve and passes requests needing a person to your team, with the conversation attached.
Credit control
More accounts to chase than people to chase them. Then the replies: “I paid”, a dispute, an arrangement request, someone who wants to speak to a person.
Your Chatterbox sends the reminders, responds within your rules and records what your team needs to do next.
What happens when a customer cannot reach you, or a request goes nowhere? A fault can get worse, a customer can lose confidence, and your team can end up handling the same request again. Start with a recurring problem your team recognises.
Capture enquiries and callback requests when your office is busy or closed. Your team receives the details, so it knows who needs help and why. See a service request captured
Levy details, school dates, admissions documents. Give customers answers from information you approve, without asking your team to explain the same thing again. See the conversation and team record
Let customers explain what they need in the language they are most comfortable using. Your team still receives a structured English record. See the language example
Send a notice or appointment reminder and understand what customers say back, rather than a one-way broadcast. Reminders on a subscriber base
Capture what happened, where and when, and pass the details to the team you choose. They receive the conversation and a clear request to act on. See how a request is handled
Keep the request and conversation together so customers do not have to start again. Your team records progress and can see what still needs attention. See the next step for your team
Each example shows what the customer says, how your Chatterbox responds and what your team receives.
Customer service Starts when customers reach you
I have no power in my unit.
Which unit are you in, and when did the power go off?
Unit 18. About twenty minutes ago.
Thank you. I have logged the power issue for the estate team. Your reference is 5183 6046.
The reference confirms that the issue was logged. The estate team still needs to investigate and record what happens next.
Credit control Starts when you reach customers
A payment reminder has gone out. The customer replies.
I have already paid at the supermarket.
Thank you. I have recorded your payment claim. Your reminders are paused while your accounts team checks it.
A claim does not mark the account paid. Your team checks it against the next account list; this workflow writes nothing back to your billing system. Your Pilot proves SMS replies on your own base.
A customer enquiry can lead to an update. A payment reminder can bring a reply. Your Chatterbox keeps the conversation and next step together, so your team can pick up where it left off.
Side one
Side two
Shared by both sides: Your knowledge. Your rules. Your Chatterbox.
Shared outcome Context kept. Next step clear.
Service path
Credit-control path
To send an update about a request, your Chatterbox needs its current status. Your team records that status unless a connected system supplies it.
Choose customer service, credit control, or both.
Customers can write in South Africa's 11 official spoken languages and speak in English, isiZulu or Afrikaans. Your team receives an English record of what the customer needs, with their original words alongside.
A separate example: a customer asks about debit-order dates and help changing theirs.
Watter debietorderdatums bied julle aan, en kan iemand my help om myne te verander?
You choose the information your Chatterbox uses, who it contacts and which requests need your team.
It answers from what you approve. When the answer is not there, it says so and records the request for your team.
Urgent matters are recognised, flagged with the reason, and handed to your team. You choose who receives service requests, disputes, arrangement requests and requests to speak to someone, with the conversation attached.
An authorised person approves the exact contact list and message. Your team can pause, resume or stop a campaign at any time.
Consent is checked before campaign texts.
Campaign calls, texts and emails follow permitted contact hours, and you cap how often each contact is called, texted or emailed.
Opt-out and do-not-contact records suppress campaign calls, texts and emails. STOP ends reminders on every channel.
No. Start with customer service or credit control. Customer service is useful without recurring billing or overdue accounts.
Yes. Replies to payment reminders belong to credit control. Updates about a service request belong to that service job. Changing who contacts whom does not create another chargeable job.
Your team investigates service issues, handles disputes and arrangements, and confirms what has been done. A logged request is not a completed change, and a payment claim is not a confirmed payment.
A public website or a small set of approved documents. You and your team try familiar customer questions privately. No account list is needed.
Calls, texts and emails to customers are set up later, along with actions in your systems. The route depends on the job; not every setup needs a Pilot.
We prepare a free, private Preview using your website or approved documents. You and your team can try familiar questions and review the answers and sample requests. Open it through a secure link on your phone or computer, with nothing to install. For credit control, start with the payment questions your policies already answer.
A public website, or a small set of approved documents.
Ask what your customers already ask.
Go through the answers and sample requests together.