Nobody waits with the browser open.
A message arrives at 22:47 and the next human touch is 09:15 the following morning. The customer does not experience that as out of hours, they experience it as no answer, and by the time the reply lands they are talking to somebody else.
The usual answers both fail. Hiring around the clock is expensive and still leaves gaps. Asking the team to reply within minutes all day is asking people to behave like a system, which works right up until it is busy.
Underneath that, the conversations are spread across email, phone and chat with no single place they land, so even the messages that do get answered are answered without the history.
Acknowledge immediately, answer what repeats, and hold everything else until the hour a person can do something with it. Automation buys the first minute, not the whole conversation.
Three pieces, and only the first one is mandatory.
Start with the acknowledgement. Add the bot when you can see which questions actually repeat. Add scheduling when you are messaging across time zones.
Acknowledge on inbound, and set the expectation
A record-triggered flow on the inbound message. It replies once per conversation with what happens next and when, and it asks for the one detail that will save a round trip.
Setting a specific expectation is the part that works. "We will get back to you shortly" reads as nothing; "someone will pick it up when the team opens at 09:00" reads as an answer.
Let a bot take the questions that repeat
A bot answers common questions, collects a detail, opens or updates a Case, and hands to a person when it runs out of road. Build it from what the inbox actually contains rather than from what you imagine gets asked.
Give it a hand-off that works. A bot that cannot pass to a human is worse than no bot, because it traps the conversation it was meant to speed up.
Send on the recipient's clock, not on yours
A time window evaluated in the recipient's own time zone, set once at org level rather than remembered per flow. Outbound queues to the next allowed hour; an acknowledgement to someone who messaged you at 22:47 still goes out at 22:47, because they are awake and they started it.
That distinction between answering and initiating is the whole of the setting.
Everything lands on a record, including the ones the bot handled.
The transcript is written back whether a person or a bot answered, so the morning shift reads the conversation rather than restarting it.
Four, and the first one is about not lying.
The number to watch is how many conversations a person never had to touch.
Not deflection for its own sake. A rising bot share with a flat satisfaction score means it is working; a rising bot share with rising chasers means it is hiding a problem.
Where ValueText fits.
ValueText is the inbound handler, the bot builder and the send action. It matches an inbound number to a record, writes the transcript back, exposes the send action to Flow, and holds the org-level send window. Bots are built in ValueText with no code. The flows, the Cases, the queues and the reports are standard Salesforce and stay if you leave.
Professional edition or above · WhatsApp needs an approved template to open a conversation, not to continue one · 1 SMS segment per reply at the published per-country rate“Valuetext can be so simple and yet so complex... if you only need the basic (even for Bots) it gets the job done without much hassle…”
Francisco LozanoAppExchange review