Skip to main content

Automate responses to customers when you’re offline

Learn how to use Data connectors and Workflows to automatically reply to customers when your team is offline or unresponsive.

Written by Eden

Using Data connectors, you can create automated responses to share with customers who match Workflows you have in place. With an auto-responder in place, you can set expectations with your customers during office hours or when you are offline. We’ll go through how to best set up your Data connectors and Workflows to seamlessly automate replies and support your customers.


Set up the Data connector

Headers

When setting up your Data connector, you will need to first update the headers being used for your request. The headers of the Data connector should include the following content and use the same format as shown when looking at the API documentation for the Reply to a conversation endpoint:

Data connector headers configuration showing Content-Type and Authorization header fields with the Reply to a conversation endpoint URL

You will need to insert the dynamic attribute Conversation ID in place of <ID> in the endpoint URL.

Request body

For the Request Body, you will need to format the request using the same formatting that is shown in the REST API documentation for the Reply to a conversation endpoint:

Data connector request body showing a JSON payload with message_type reply, type admin, and a body field containing the automated response text

Testing

Once you have added your content to the Request Body, you can test out the Data connector using a conversation in your workspace. Enter the conversation's ID in the Test value field and click the "Test" button.

If the test is successful, you will see the automated response appear in your test conversation.

Tip: You can find a conversation's ID in the URL when the conversation is open in your inbox.

From there, you can Save and set live your Data connector.

Note: Your Data connector must be set live before you add it to a Workflow. The Workflow won't trigger the connector until both are live.


Set up the Workflow

1. Create or edit a Workflow with the Teammate has been unresponsive trigger — for example, set it to fire after a teammate has been unresponsive for 5 minutes.

Workflow builder showing a Teammate has been unresponsive trigger set to 5 minutes

2. Add Branches to your Workflow path.

Workflow path with two branches added after the Teammate has been unresponsive trigger

3. Click the first branch to define the conditions for when to send the Data connector, such as, if Team assigned is "Sales" and Office hours is "Outside". Add your Data connector to this branch.

Branch condition configured with Team assigned is Sales and Office hours is Outside, with the Data connector action added to that branch

4. Click Save then Set live. Any conversations that match the conditions will trigger the Data connector.


💡Tip

Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts


Did this answer your question?