2. Out-of-hours acknowledgement
The worst outcome for a 10pm enquiry is silence until 10am. A flow that acknowledges the message, sets expectations for a reply and offers the FAQ menu in the meantime costs nothing and holds the lead.
3. Routing by intent
Support questions and sales enquiries need different people. A condition node reading the menu choice can assign the thread to the right queue before anyone has opened it, which is the difference between a five-minute response and a five-hour one.
4. Handoff that actually hands off
This is the one most implementations get wrong. A handoff node that only switches the bot off leaves the thread unassigned, and unassigned threads are how leads go missing.
A real handoff picks a specific person. In Waboxa the thread goes to the least-loaded active agent, is marked as assigned, and has AI switched off so nothing talks over the human who just took it.
5. The follow-up nobody remembers
A scheduled message two days after a quote is the least glamorous automation on this list and usually the highest returning. It requires no intelligence at all — just something that does not forget.
The rule about where to stop
Automate anything the customer would not notice a human doing differently. Acknowledgement, routing, capturing structured answers, scheduling a nudge — nobody minds.
Stop at the point where the answer requires judgement about their specific situation. That is the moment a customer can tell, and it is the moment automation starts costing you the deal it was supposed to protect.