Most requests stall in the follow-up
A surprising amount of operational work is waiting. Waiting for a customer to send a document, confirm a detail, sign a form, pick a date, or answer a question they were asked last week. The work itself might take five minutes. Getting the customer to do their part takes five follow-ups.
Someone on your team ends up keeping a mental list, or a spreadsheet, of who still owes what. When that person is busy, off sick or simply forgets, the request stalls.
Specific beats persistent
The usual fix is an automated reminder: the same message, every few days, until someone replies. It works badly because it's generic. It tells the customer they owe something, not what, and it keeps going even after they've replied with the wrong thing.
Nuncily follows up the way your best team member would:
- It knows what's outstanding, item by item, so the follow-up says "we still need page two of the March statement", not "please send your documents".
- It answers questions in the same thread. If the customer asks which statement you mean, they get an answer, not another reminder.
- It adapts the timing to the deadline and to how the customer has responded so far, within limits you set.
- It stops as soon as the request is complete.
Channels are an interface, not the product
Customers reply fastest on the channel they already use. In much of Europe, the Middle East, Latin America and Asia, that's WhatsApp. In the US it's more often text messages and email. The platform is WhatsApp-first with email alongside, and custom builds can add SMS or web chat. Whatever the channel, the logic behind the follow-up is the same.
When a person takes over
Some replies need a human: a complaint, a dispute, a question about a decision, a customer who's upset. Those go to your team immediately, with the whole conversation attached, so nobody has to ask the customer to repeat themselves.
Getting started
Follow-up for a standard process, like collecting documents or confirming details, runs on the Nuncily platform. Follow-up that has to read from or write to your own systems is a custom build.