Customer or teammate has been unresponsive
Build Workflows that trigger automated messages and manage inactive conversations.
Written By Markus from Featurebase
Last updated 3 months ago

Overview
Improve your support team’s efficiency by automating how inactive conversations are handled. Using purpose-built triggers and actions, you can send automated follow-ups, set expectations, or close/snooze conversations after a chosen period of inactivity.
If customer has been unresponsive

This trigger is ideal for automatically managing conversations where the customer hasn’t replied for a set amount of time.
Go to Automations → Workflows
Click + New Workflow and choose Create from scratch.
Select the trigger Customer unresponsive under the During conversation tab.
Set the inactivity timer to control how long to wait for a customer response before triggering the workflow. The duration must be longer than 30 seconds and shorter than 14 days.
Note: This workflow only runs if the last message was sent by a teammate. It won’t trigger if the last message came from a bot.
Example
You can choose to build this workflow in a number of ways. Here’s an example:
Set the trigger timer to 10 minutes - meaning the workflow activates after 10 minutes of no customer response. You can also configure trigger channels, audience, and scheduling.

Add a message - “Just checking if you’re still there? Let us know if you need any help.”
Add a Wait action - Delay the next step for a chosen amount of time and decide whether it can be interrupted by teammate or customer replies.
Add a follow-up message: “This conversation will now be closed”
Add a Close conversation action
Now click Save to preview your new Workflow or set it live!

How it works:
The workflow triggers when a customer has been inactive after a teammate reply for the defined period.
If a teammate starts a new conversation from the inbox, the workflow triggers only if the customer replies and then becomes unresponsive.
Messages sent via Outbound campaigns will not trigger this workflow.
If teammate has been unresponsive

This trigger helps set reply expectations for customers when your team is offline or reroute conversations to another inbox.
Go to Automations → Workflows
Click + New Workflow and choose Create from scratch
Select the trigger Teammate unresponsive under the During conversation tab.
Set the inactivity timer to control how long a teammate can go without responding before the workflow runs.
The duration must be longer than 30 seconds and shorter than 14 days.
The timer is based on the customer’s first message, not their last - if they send multiple messages in a row, the timer starts from the first one.
Note: This trigger also only triggers if the last message before the customer’s reply was sent by a teammate, not by a bot.
Example
You can choose to build this workflow in a number of ways. Here’s an example:
Set the trigger timer to 10 minutes - meaning the workflow activates when no teammate replies within 10 minutes of the customer’s first message.

Configure the trigger - set up the trigger channels, audience, and scheduling. For example, you might want this workflow to trigger only when your team is offline.

Add a message: “Thank you for your patience. We’ll get back to you as soon as possible.”
Alternatively, add a Show expected reply time step to display your office hours
You can end the workflow here if the teammate should handle the conversation once they’re back online
Add an Assign conversation action to reroute it to a inbox or teammate. You can also apply other actions like Mark as priority.
Click Save and close to preview or Set live to activate the workflow.

Note:
The workflow triggers after a customer starts a conversation or when it leaves the bot inbox before a teammate’s first reply.
If you’re using Simple automation to suggest help articles, the system will wait for the customer to finish viewing the article before moving forward.
During this time, other triggers (like teammate inactivity) will pause until the customer closes the article or sends another message.