WhatsApp 24/7 Customer Service for Small Businesses in 2026: How to Handle Out-of-Hours Enquiries Without Night Staff

What types of enquiries arrive outside business hours — and which a bot handles well

Before building automation, audit 2–4 weeks of your WhatsApp conversation history and categorise what comes in outside business hours. The distribution for most service and retail businesses follows a similar pattern:

• Booking and availability requests (40–55%) — 'Are you available Saturday at 3pm?' These are handled well by a bot that presents available slots or links to your booking page.
• Pricing questions (20–30%) — 'How much is a 60-minute session?' A bot can answer these with your standard rate card.
• FAQ and how-does-it-work (15–20%) — 'Do you offer home visits?' 'What should I bring?' Standard FAQ responses handle these.
• Complex or bespoke requests (10–15%) — 'I have a medical condition, can you accommodate me?' These need human judgment and should be routed to a queue for morning follow-up.
• Complaints and urgent issues (<5%) — These need a human urgently. Your automation should escalate these to an on-call notification if you have one, or acknowledge and flag for first-thing-in-the-morning priority handling.

A chatbot that handles the top three categories covers 75–85% of out-of-hours traffic. The remaining 15–25% gets an acknowledgement and a realistic wait-time expectation — which is dramatically better than silence.

Building the out-of-hours flow: three components

Component 1 — Time-based routing. Configure your WhatsApp automation to detect the time a message arrives. During business hours, messages go to your team inbox. Outside hours, they enter the automated flow. Platforms like WATI, Respond.io, and BossBot support time-of-day routing rules natively.

Component 2 — Intent detection and response. The bot's first message presents a menu: 'Hi! Our team is offline until 9am. I can help with: [1] Booking [2] Pricing [3] Common questions [4] Leave a message for our team.' Button-menu interactions (rather than free-text) are more reliable and require no NLP — the customer selects, the bot routes.

Component 3 — Human handover queue. Conversations that the bot cannot resolve are flagged and placed in an 'unread' queue for the first agent who logs on. The bot sends a confirmation: 'I've passed your message to our team. You'll hear from us before 10am.' This sets a concrete expectation.

Optional: escalation for urgent issues. If you have a genuine out-of-hours emergency channel (a personal phone number for urgent cases), your bot can ask: 'Is this urgent?' If yes, provide the emergency contact. If no, route to the morning queue. This avoids flooding personal numbers with non-urgent requests.

Response time expectations: what the data says customers will accept

Setting the right expectation matters more than the wait time itself. HubSpot's Customer Service Trends 2024 report found that customers who receive an immediate automated acknowledgement are willing to wait 3× longer for a human response than customers who receive no response at all.

Practical benchmarks from the same report:
- 90% of customers expect a response within 24 hours on any messaging channel
- 60% expect a response within 4 hours during business hours
- Out-of-hours, 48 hours is the outer limit of acceptable wait before most customers seek an alternative

For small businesses, the overnight window (11pm–9am) is roughly 10 hours. An automated acknowledgement at 11pm + human response at 9am = 10 hours. This is within acceptable range for most non-urgent enquiries if the acknowledgement message includes a specific response time commitment: 'Our team will reply before 9am' performs better than 'we'll get back to you soon.'

The risk period is not overnight — it's the Friday-evening-to-Monday-morning window (60+ hours) if you don't have weekend coverage. Consider adding a Saturday half-day response window for high-value enquiries, or flagging weekend messages for priority handling on Monday morning.

Step-by-step: setting up 24/7 automation on WATI in 30 minutes

WATI's flow builder allows time-based automation without developer resource.

Step 1: Create an out-of-hours trigger. In WATI's flow builder, create a new flow. Set the trigger to 'Inbound message during non-business hours.' Define your business hours (e.g., Mon–Fri 9am–6pm, Sat 9am–2pm) in WATI's settings.

Step 2: Build the menu. Add a WhatsApp interactive button message: 'Our team is offline until [time]. I can help with:' + 4 buttons: Book, Pricing, FAQ, Leave message.

Step 3: Branch each option. Book → send a calendar link (Calendly, Google Calendar appointment page). Pricing → send a text message with your standard rates. FAQ → offer a second set of 4 common questions. Leave message → collect their query as a text reply and tag the conversation for team follow-up.

Step 4: Set team handover. Any conversation that reaches the 'Leave message' branch gets tagged 'follow-up' and assigned to the unread queue for the first agent who logs on.

Step 5: Test it. Send yourself a message outside business hours. Walk through each branch. Check that the booking link works, that the pricing message is accurate, and that 'Leave message' conversations appear in the agent queue tagged correctly.

Total setup time for a basic version: 25–35 minutes. Refinement after seeing real usage patterns: ongoing over the first two weeks.