What's new?

The Wait action now supports User Replied as a wait condition. In addition to waiting for a contact to reply, you can now keep the contact waiting until a team member responds to the conversation before continuing to the next step. Combined with the timeout option, you can now build powerful SLA workflows that automatically escalate if no user reply is sent within your target response time.

How it works

When configuring a Wait action, select User Replied as the wait condition and optionally define a timeout. The workflow pauses until a user replies or the timeout is reached – whichever happens first. If a reply is detected, the workflow continues immediately. If the timeout expires first, you can route the contact through escalation steps such as notifications, reassignments, or reminders.

How to use it

• Add a Wait action to your workflow.
• Select User Replied and configure an optional timeout.
• Define what should happen after a user replies or when the timeout is reached.

Why we built it

Response-time SLAs are critical for sales and support teams. This enhancement lets you automate first-response tracking, reduce manual monitoring, and ensure conversations are escalated when response targets are missed – all without building complex workflow logic.

Simple examples

• A support workflow waits up to 30 minutes for User Replied. If an agent responds within the SLA, the workflow continues normally. If the timeout is reached first, it alerts a supervisor and reassigns the conversation.
• A sales workflow waits 15 minutes for a representative to reply to a new lead. If no reply is sent before the timeout, the workflow creates an urgent task and notifies the sales manager to help prevent missed opportunities.

Additional Notes

• The contact resumes as soon as a user sends a reply or when the configured timeout is reached.
• If no timeout is configured, the workflow waits until a user reply is received.
• Ideal for first-response SLAs, escalation workflows, and internal response-time automations.

Preview

What's new?

You can now start workflows when a user replies to a conversation. This trigger fires whenever a user (team member) sends a reply to a contact, making it easier to automate internal processes after an agent responds instead of waiting for a customer reply.

How it works

Add the User Replied trigger to any workflow and choose the conditions that should start it. Once a user replies to a contact through a supported conversation channel, the workflow runs automatically and can continue with actions such as notifications, tagging, assignments, or follow-up automations.

How to use it

1. Open Automations > Workflows and add the User Replied trigger.
2. Configure any trigger filters required for your workflow.
3. Publish the workflow to automate actions whenever a user replies to a contact.

Why we built it

Many automations need to react to your team's actions- not just customer activity. The User Replied trigger helps you build workflows that track agent engagement, trigger internal notifications, update records, or kick off the next step immediately after a team member responds.

Simple example

• A sales representative replies to a new lead's SMS. The User Replied trigger automatically updates the opportunity stage to Contacted and notifies the sales manager.
• A support agent replies to a customer's email. The User Replied trigger adds a Support Responded tag and creates a follow-up task to check in after 48 hours.

Additional Notes

• The trigger activates only when a user sends a reply, not when a customer responds.
• Use this trigger for internal workflow automation based on team activity.

Preview

What's new?

You can now start workflows when a user replies to a conversation. This trigger fires whenever a user (team member) sends a reply to a contact, making it easier to automate internal processes after an agent responds instead of waiting for a customer reply.

How it works

Add the User Replied trigger to any workflow and choose the conditions that should start it. Once a user replies to a contact through a supported conversation channel, the workflow runs automatically and can continue with actions such as notifications, tagging, assignments, or follow-up automations.

How to use it

1. Open Automations > Workflows and add the User Replied trigger.
2. Configure any trigger filters required for your workflow.
3. Publish the workflow to automate actions whenever a user replies to a contact.

Why we built it

Many automations need to react to your team's actions- not just customer activity. The User Replied trigger helps you build workflows that track agent engagement, trigger internal notifications, update records, or kick off the next step immediately after a team member responds.

Simple example

• A sales representative replies to a new lead's SMS. The User Replied trigger automatically updates the opportunity stage to Contacted and notifies the sales manager.
• A support agent replies to a customer's email. The User Replied trigger adds a Support Responded tag and creates a follow-up task to check in after 48 hours.

Additional Notes

• The trigger activates only when a user sends a reply, not when a customer responds.
• Use this trigger for internal workflow automation based on team activity.

Preview

What's new?

You can now start workflows when a user replies to a conversation. This trigger fires whenever a user (team member) sends a reply to a contact, making it easier to automate internal processes after an agent responds instead of waiting for a customer reply.

How it works

Add the User Replied trigger to any workflow and choose the conditions that should start it. Once a user replies to a contact through a supported conversation channel, the workflow runs automatically and can continue with actions such as notifications, tagging, assignments, or follow-up automations.

How to use it

1. Open Automations > Workflows and add the User Replied trigger.
2. Configure any trigger filters required for your workflow.
3. Publish the workflow to automate actions whenever a user replies to a contact.

Why we built it

Many automations need to react to your team's actions- not just customer activity. The User Replied trigger helps you build workflows that track agent engagement, trigger internal notifications, update records, or kick off the next step immediately after a team member responds.

Simple example

• A sales representative replies to a new lead's SMS. The User Replied trigger automatically updates the opportunity stage to Contacted and notifies the sales manager.
• A support agent replies to a customer's email. The User Replied trigger adds a Support Responded tag and creates a follow-up task to check in after 48 hours.

Additional Notes

• The trigger activates only when a user sends a reply, not when a customer responds.
• Use this trigger for internal workflow automation based on team activity.

Preview

What's new?

You can now start workflows when a user replies to a conversation. This trigger fires whenever a user (team member) sends a reply to a contact, making it easier to automate internal processes after an agent responds instead of waiting for a customer reply.

How it works

Add the User Replied trigger to any workflow and choose the conditions that should start it. Once a user replies to a contact through a supported conversation channel, the workflow runs automatically and can continue with actions such as notifications, tagging, assignments, or follow-up automations.

How to use it

1. Open Automations > Workflows and add the User Replied trigger.
2. Configure any trigger filters required for your workflow.
3. Publish the workflow to automate actions whenever a user replies to a contact.

Why we built it

Many automations need to react to your team's actions- not just customer activity. The User Replied trigger helps you build workflows that track agent engagement, trigger internal notifications, update records, or kick off the next step immediately after a team member responds.

Simple example

• A sales representative replies to a new lead's SMS. The User Replied trigger automatically updates the opportunity stage to Contacted and notifies the sales manager.
• A support agent replies to a customer's email. The User Replied trigger adds a Support Responded tag and creates a follow-up task to check in after 48 hours.

Additional Notes

• The trigger activates only when a user sends a reply, not when a customer responds.
• Use this trigger for internal workflow automation based on team activity.

Preview