Playbook, fintech app
At two in the morning the only useful answer is a telephone number
The overnight queue on a money app contains two completely different people. One has a question about a fee and can wait. The other has just seen payments they do not recognise, and for them every hour is worth something, because in many markets how quickly a firm is told affects what happens next. The job of an assistant at that hour is not to answer, it is to sort those two apart in one reply and produce a number for the second.
Why this is not the general answer
The handling pattern for out of hours holds across every trade. What follows is the part that does not.
- Some routes on a regulated money product run continuously while general support does not, which turns the overnight question into which route rather than what time, and that is not true of a business with a closing time.
- Notifying quickly can affect how an unauthorised transaction is treated in many markets, so the delay introduced by a form at midnight is not a neutral cost the way it is elsewhere.
- Money moves on working days rather than on clock hours, so nothing having happened since Friday afternoon is usually settlement and a cut off time rather than anybody being asleep.
- The customer at midnight has typically already tried the app, so an answer that sends them back to a screen they have just used reads as a refusal rather than as help.
How it arrives
- is there anyone i can call right now
- i can see payments i did not make and it is the middle of the night
- my transfer has not moved since friday afternoon
- what time does your support team start
- can i freeze my card without speaking to anyone
- is there anybody available on a bank holiday
What has to be indexed for this to work
| The fraud line, its number and its hours, written into the fallback | The most important string in the corpus for this industry. It belongs inside the message returned below the match threshold, so it appears without depending on the right page being retrieved at three in the morning. |
|---|---|
| Which routes run continuously and which do not | A short table separating the always available routes from ordinary support, with the hours and the time zone named beside each. Customers merge the two constantly, and the merge is what produces a complaint about being ignored. |
| The card freeze path, in one line | The exact route inside the app. It is the one thing a customer can do themselves in the seconds before a call connects, and under stress nobody can find it. |
| Cut off times and working day rules | When a payment sent late in the day is processed, what a weekend or a public holiday does to it, and which dates the team treats as non working. This answers the quiet weekend question without anybody being contacted. |
The reply
If you can see payments you did not make, please ring the number above now rather than waiting for a reply here, and freeze your card in the app while the call connects [1]. That line runs outside the hours of ordinary support, which are listed with the time zone on the contact page [2]. If instead a transfer has not moved since Friday, that is usually a working day question rather than a fault: payments sent after the cut off are processed on the next working day and weekends do not count. I cannot see your account or any payment on it, so anything specific needs the team.
The fraud route comes first and unconditionally, because sorting the two overnight cases apart is the entire job and getting it the wrong way round costs somebody money. The freeze instruction gives them something to do in the gap. The settlement sentence is included because it silently resolves the other half of the overnight volume without anybody needing to be awake.
Where it stops
The trigger. Any overnight message that could be an unauthorised transaction, and any question about when a specific message will be answered.
Please ring the number above straight away rather than leaving details here if money has moved without your say so. For anything else, leave your name and the email on the account and it will be picked up when the team is next in, within the hours on our contact page.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never ask somebody to complete a form before the fraud number has been given.
- Never promise when a message will be answered, or say that somebody is available now.
- Never say a payment will land at a particular time on a particular day.
- Never treat a message about money moving without permission as an ordinary out of hours enquiry.
Questions
- What is the point of answering overnight if nobody is there?
- Two things happen. The fee, limit and timing questions get answered at three in the morning from material you already wrote. And the one message that needed a telephone number gets one immediately instead of sitting in an inbox until morning, which is the case the whole design is for.
- Can it tell somebody when their transfer will arrive?
- No. It can quote the cut off and the working day rule, which tells the customer whether the payment is even late yet, and that resolves a good share of them. It has no view of any payment and must not imply one.
- Should the number be in the fallback message rather than in the answers?
- In the fallback, word for word. The messages that most need it are the ones typed fastest and worded worst, which are exactly the ones least likely to match an indexed page. Putting it in the fallback means it is present by construction.
Keep reading
- Everything for a fintech appFees, limits and identity checks are safe ground. Balances, transactions and anything reading as a personal recommendation are not.
- Handling out of hours in generalThe difference between an emergency route and a message form, and why an honest wait time beats a promise you cannot keep.
- The one answer that has to be a quotation rather than a sentenceSafeguarding and deposit protection are drafted statements, not a topic. Quote the paragraph, never summarise it, never reassure.
- The list is genuine, and joining it is not an applicationRegion by region launches make this a real list rather than a marketing device. What may be said, and why eligibility is never predicted.
- Why an account is restricted is never something a public widget knowsLocks, reviews and frozen cards are the highest anxiety questions on a financial app. Which parts are publishable and which are not.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.