Auto-response about non-business hours (chats)

Last update: 16.09.2022

To ensure that customers who contact support outside business hours know when to expect a response, set up automatic sending of business hours messages:

af29710b0303bfffcb2698651dc1de2b.png

To do this, you need:

  1. Specify working hours (administrator account — section "Team" — subsection "Business schedules").

  2. Create a rule for new cases that will send an auto-response when new chats arrive.

  3. Create a rule for updated cases that will send an auto-response to new messages in existing chats.

  4. Create a rule that will remove the label after the agent's response.

The rule for new cases

0b03916c53f70ba443229ad5f116afb6.png

The rule for updated cases

9ee69571b8165cab28a0e8a84ae6716f.png

The label, in this case, is added so that the customer does not receive an auto-response again if he/she decides to ask an additional question some time after receiving the auto-response and sends another message. This situation is discussed in more detail in another article.

The rule for label removal after an agent's response

d975b9e3885cab1d920090a58a6def4e.png

The rule for label removal at the beginning of the working day

If during weekends or non-business hours your agents occasionally look through customer cases and respond to them if possible, but do not monitor chats all the time, it is more logical not to remove the “Auto-reply during non-working hours” label immediately after the agent's response. Otherwise, if the customer contacts you again, he/she will again receive a notification about non-business hours and the dialogue will look awkward.

In this scenario, it is better to remove the label at the beginning of the working day. For such logic, instead of a rule for updated cases that removes the label immediately after the agent's response, create a rule for existing cases, set the condition "Hours since agent response — is less than — 1" in it, and do not forget to consider your working hours.

d549bc90653a6cdcab27f46676f0b6d9.png

Was this article helpful?