---
title: "How to respond to customers outside working hours · Lyntev"
description: "Prepare a useful away reply and handle the request when work resumes. Define realistic timescales, exceptions and a queue to avoid promises without follow-up."
url: "https://lyntev.com/en/guides/respond-customers-outside-working-hours"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. How to respond to customers outside working hours

# How to respond to customers outside working hours

Acknowledge receipt, explain when the team can respond and ask only for the necessary context. Then ensure the request enters a queue reviewed when work resumes. An immediate message can provide guidance, but should not promise a reply, appointment or solution that nobody can confirm.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 20 November 2026.
About 6 minutes to read.

[Start reading](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/responder-clientes-fora-horario.txt>)

**The answer starts with the source**Approved information, defined access and a verifiable answer.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/responder-clientes-fora-horario>); source revision 20 November 2026.

By the end, you can:

- Distinguish an automatic reply from completed service
- Set an expectation compatible with opening hours
- Prepare for resuming work and exceptions without losing requests

In this guide

1. [Define what is available outside opening hours](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#capacidade-horario>)
2. [Write an acknowledgement with a realistic expectation](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#mensagem-util>)
3. [Control when and how often the message appears](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#regras-e-frequencia>)
4. [Create a queue the team reviews on returning](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#preparar-regresso>)
5. [Test a weekend through a fictitious scenario](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#exemplo-fim-semana>)
6. [Give exceptions a clear destination](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#situacoes-delicadas>)
7. [Evaluate what happened after acknowledgement](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#avaliar-ausencia>)
8. [Approve the message and the resumption plan together](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#ficha-fora-horas>)
9. [Sources and criteria](<https://lyntev.com/en/guides/respond-customers-outside-working-hours#fontes>)

## Define what is available outside opening hours

Separate automatic information, receiving requests and the presence of a person. A business may accept messages at any time without permanent human support. Write down working hours, public holidays, breaks and who monitors changes. If exceptional coverage exists, describe its scope and dedicated channel instead of leaving customers to assume the whole team is available.

Observe when requests arrive and which tasks they require. A question about an address can be answered with stable information; appointment availability or a fault may require checking. This distinction helps choose what the message can clarify and what must remain explicitly pending until someone resumes work.

## Write an acknowledgement with a realistic expectation

A good message identifies the business, confirms the channel’s context and explains the next point of follow-up. It can indicate the minimum information needed to prepare a response, but should not demand a long form within a conversation. If timescales vary, explain how priority will be confirmed; do not invent a “reply in five minutes” for every situation.

Illustrative wording to adapt: “Thank you for your message. The team will resume service in the next opening period. Tell us which service you need and, if you have one, your enquiry reference. We will contact you again to confirm the next steps.” Add specific opening hours only after validating them. For permanent information, a clear link can avoid repeated messages without promising automatic resolution.

Write an acknowledgement with a realistic expectation

| Element | Function | Check |
| --- | --- | --- |
| Opening hours | Explain when the team is available | Matches operations and public holidays |
| Information requested | Prepare the next action | Is necessary for this request type |
| Commitment | Say what will happen next | Someone is responsible for fulfilling it |
| Exception | Guide situations outside the scope | The indicated channel exists and is available |

## Control when and how often the message appears

Check the tool’s actual options and test its behaviour with fictitious contacts. An away message may trigger in different situations from a greeting or an AI reply. If several automations act on the same incoming message, customers may receive repetitions or incompatible instructions. Define which is responsible for the initial guidance.

The Business app includes away-message and quick-reply tools; other solutions have different rules. If you use the Business Platform, confirm message and customer service window requirements for the contracted model. Do not circumvent restrictions through repeated sending or turn an out-of-hours contact into permission for campaigns. Keep the conversation within the purpose the person expects.

## Create a queue the team reviews on returning

Define how requests received outside opening hours are identified. At the start of the shift, someone should distinguish new requests, information added to an open matter and situations already handled through another channel. A message count does not automatically reveal how many tasks exist or what commitment was made before the absence.

Prepare a review order with clear criteria and available capacity. If volume exceeds what the team can handle, communicate a revised expectation and identify where additional capacity is needed. Reception automation may reveal a larger queue; it does not remove the work of checking, deciding and responding. The solution must include the return to work, not only the moment a message is sent.

## Test a weekend through a fictitious scenario

Loja Pátio, a fictitious example, receives a request on Saturday evening about collecting an order. The message explains the next service hours and asks only for the reference, without requesting a photograph of a document. The matter goes into the review queue. On Monday, the team checks the actual status and confirms when collection will be possible.

In a second test, the person sends more information before opening. The team checks that this message does not create two independent requests or trigger an endless sequence of automatic replies. The test uses fictitious data. The aim is to observe continuity and clarity without claiming a greeting increased sales or the request was resolved before human verification.

## Give exceptions a clear destination

If the channel is not for emergencies, say so in a way appropriate to the service and indicate a valid alternative where one exists. Do not use AI to make decisions on its own in situations requiring human assessment or professional procedures. In healthcare and other sensitive areas, service and information-handling rules need specific review; a generic retail message is insufficient.

Prepare for failures too: an unconfigured public holiday, unexpected absence, connection interruption or unavailable automatic message. Keep consistent contact options and opening hours on the website. The team should know how to update guidance without depending on an absent person. Test withdrawal of an old promise because saved replies may continue circulating after operations change.

## Evaluate what happened after acknowledgement

Count requests received, time until the team’s first useful reply and matters still without a next action. An automatic reply can have low latency but insufficient usefulness. Examine a sample to see whether people sent the necessary information or had to repeat everything. The indicator should distinguish guidance from resolution.

Compare periods with similar hours and volumes, including the size of the initial queue. If there are fewer complaints, look for other changes that might explain the effect. Use the review to improve the message and capacity to resume. Do not assess quality solely by the number of automatic sends, which may rise precisely because customers did not understand what to do.

## Approve the message and the resumption plan together

The worksheet should be validated by someone who knows operations and by those handling requests on returning. Keep opening hours, activation rules, wording and exception destinations. Someone should confirm holiday and public-holiday changes before they start rather than correct the notice only after a complaint.

Repeat the test after changing tools or adding AI to customer service. Preserve the principle: provide truthful information, collect the minimum and hand the request to someone able to continue. If the system does not allow control of a required behaviour, document the limitation and manual procedure rather than present automation as permanent human coverage.

### Worksheet for your project

```
Opening hours and periods without staff:
What automation can clarify:
Approved wording and expectation:
Minimum information requested:
Activation and frequency rule:
Other automations to avoid running simultaneously:
Queue and person responsible when work resumes:
Priorities and review commitment:
Exceptions and validated alternative channel:
Public-holiday, repetition and new-message tests:
Indicators and next review:
```

## Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

- [WhatsApp — ferramentas da aplicação Business](<https://whatsappbusiness.com/products/business-app-features/>)
- [WhatsApp — política de mensagens empresariais](<https://whatsappbusiness.com/policy/>)
- [Microsoft Learn — classificação e distribuição do atendimento](<https://learn.microsoft.com/en-us/dynamics365/customer-service/administer/overview-unified-routing>)

## Continue to your next decision.

- [Configure automatic message logic](<https://lyntev.com/en/guides/whatsapp-business-automatic-message>)
- [Map the business’s customer service process](<https://lyntev.com/en/guides/map-business-process-before-automation>)
- [Explore AI-powered service on WhatsApp](<https://lyntev.com/en/whatsapp-ai-customer-service>)

This guide is part of [Improve customer service with AI.](<https://lyntev.com/en/guides#atendimento-whatsapp>)

- [How to distribute customer conversations across a team](<https://lyntev.com/en/guides/distribute-customer-conversations-team>)
- [How to organise quote requests through WhatsApp](<https://lyntev.com/en/guides/organise-quote-requests-whatsapp>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
