Remittance is a habit business. Most regular customers send on a rhythm: every payday, every fortnight, on the first of the month before the rent is due back home. When a regular sender misses their usual day, they have often not stopped sending. They have sent with someone else. By the time a monthly report shows the drop, the habit has moved. This guide is for growth, retention and customer support leads who want to see those customers while there is still time to do something about it.
The principle: a customer's own sending history is the best predictor of when they will send next, and a missed day is the earliest warning you will get.
RemitSo, a white label remittance platform, now includes a Sending Forecast in the admin panel. Every night it reads each customer's paid transfers and lists who is likely to send next, who is overdue and who has lapsed. Your team still decides who to contact, what to offer and how often.
Why sending rhythm matters more than sending volume
Two customers each send four times in four months. One sends on the 28th of every month, like clockwork. The other sent three times in one week and once two months later. A volume report treats them the same. They are not.
The first customer has a habit. If the 28th passes with nothing, something has changed: a better rate somewhere else, a bad experience, a new job. The second customer has no habit to break, so a quiet month means very little.
That is why a useful forecast looks at three things for each customer, not just how much they send:
- How often they send: the usual gap between transfers.
- How regularly: whether that gap is steady or all over the place.
- Whether they send on the same date each month, which usually points to a pay-day.
How the RemitSo Sending Forecast reads a customer
The forecast runs every night over each customer's paid transfers from the last six months. Only paid transfers count, so an abandoned quote never looks like a habit.
| Situation | What the forecast does | Why |
|---|---|---|
| Sends on the same date each month | Reads it as a pay-day, using the last four months first | A recent change of payday should win over an old pattern |
| Sends on a steady gap | Predicts the next expected day from the usual gap | A fortnightly sender is due about two weeks after the last transfer |
| Sends less often than about every 35 days | Lists the customer as occasional, with no expected day | A guess on a slow rhythm would send your team after the wrong people |
| Few transfers behind the pattern | Lowers the confidence: high needs at least six sending days, medium at least four | A confident prediction needs real evidence behind it |
Before it is switched on, RemitSo scores the forecast against your own past transfers, so you can see how well it would have predicted your customers before anyone acts on it.
What your team sees each morning
The Sending Forecast page opens with tiles that count customers by when they are expected:
- Overdue: past their expected day with no transfer. This is the list to act on today.
- Due today.
- Due within 7, 10 and 30 days: useful for planning a message or an offer ahead of time.
- Lapsed: well past their rhythm. Harder to win back, but worth knowing about.
Occasional senders sit under a filter of their own rather than on a tile, so the tiles stay focused on customers with a real rhythm.
Useful test: look at the overdue tile for one week without doing anything, then count how many of those customers sent anyway. That tells you how much of the list is a real warning on your corridors, and how hard to act on it.
What to do with an overdue customer
The forecast does not contact anyone. It tells you who to think about. What you do next depends on the customer and your licence, but these work well in remittance:
| List | Good first action | Tool in RemitSo |
|---|---|---|
| Due in 7 days | A gentle reminder of today's rate | Broadcast messages to a chosen audience, or customers' own rate alerts |
| Overdue | A short check-in: did something go wrong last time? | Support outreach; customer feedback from the app |
| Overdue, high value | A better rate or a fee waiver for the next transfer | Promo codes with limits, dates and uses per customer |
| Lapsed | A win-back offer, then let them go | Promo codes; broadcast messages |
Keep the contact light. A regular sender who is two days late does not need a discount. They may need nothing at all. Save offers for customers who are clearly drifting.
Watch out: only contact customers through channels they have agreed to, and keep marketing messages separate from service messages. A forecast is a reason to look, not permission to message.
Why customers benefit too
Customers who send to family on a schedule care about two things: that the money arrives on time and that they get a fair rate. A reminder a few days before their usual day, or a quick check-in when something went wrong last time, feels like service, not marketing. Done well, the forecast helps your team look after the people who rely on you most.
Doing it with RemitSo
The Sending Forecast arrived in release 2026.10.9 and was refined in 2026.10.10. It is switched off until you ask for it. RemitSo turns it on, scores it against your past transfers, and runs the first refresh. Super administrators see it at once, and anyone else needs the Browse the Sending Forecast permission. Pair it with broadcast messages and promo codes in the admin panel and the rate alerts and quick send-again in the customer app. See the release notes, or book a demo.
Frequently asked questions
What data does the Sending Forecast use?
Each customer's paid transfers over the last six months. Quotes that were never paid and cancelled payments do not count.
How often is it updated?
Every night, so each morning's tiles reflect the previous day's transfers.
Does it send messages to customers automatically?
No. It lists customers by when they are expected to send. Your team decides who to contact and how, using tools such as broadcast messages and promo codes.
Why does a customer show as occasional?
They send less often than about every 35 days. Predicting a day for such a slow rhythm would be a guess, so the forecast lists them under their own filter with no expected day.
How do we know it works on our customers?
Before switching it on, RemitSo scores the forecast against your own past transfers, so you can see how it would have performed before anyone acts on it.