Did the client get the letter? One place to answer it
Between 29 and 30 September 2026 we rebuilt how LedgerTM talks to clients. Four channels shipped in two days: email, SMS and post, on one shared core. WhatsApp is in build.
The problem it solves. A bank sends a lot of paper: statements, tax certificates, rate-change notices, arrears letters, payment advices. Before this work, each of those decided on its own whether to send, where, and how. That caused four real problems.
- One address, one yes or no. A client had one email address and one opt-in. They could not copy their accountant on tax certificates. They could not take statements by email and notices by post.
- Legal letters and marketing were treated alike. A statutory arrears notice must be delivered whatever the client’s preference. The rule was hard-coded in one sender and missing in others.
- Silence. If a client had opted out, the statement simply did not go, and nothing recorded why. If the email gateway timed out, the email failed for good.
- An auditor had nowhere to look. “Did the client get it, and if not, why not?” had no single answer.
What changed.
- One correspondence service. Every statement, notice and alert goes through it. The sender says what to send and to whom. The service decides how.
- Client delivery preferences. Each client chooses a channel per kind of correspondence, and can add further email addresses, such as their accountant.
- Must-deliver correspondence. A legal notice is marked must-deliver. It goes out whatever the preference, by email and post, falling back to post.
- A recorded outcome for every send. Each send carries a result per channel: delivered, failed, posted, returned. Failed sends retry. A clerk can resend or forward.
The channels.
- Email through the bank’s own SendGrid account. The settings page shows whether each sending domain is live.
- SMS through the bank’s own Twilio account, with number checks and message-segment counts.
- Post. A letter joins a post list. A clerk records it as posted with a tracking number. If it comes back, the return is recorded too.
- WhatsApp, in build. South African clients read WhatsApp before email or SMS. It uses the same preferences and the same record, with Meta-approved message templates and the client’s opt-in.
Each bank holds its own keys. Gateway credentials live in the bank’s own vault, not in our configuration. Activating a new credential needs a second person to approve it.
Why it matters. A bank that must prove a notice was delivered now has the answer on one screen. A bank that wants to add a channel switches it on in settings. The senders never change.
Written by Jeremy Rich.