Table of Contents

Step: Assign To

Shing-Yi Tan Updated by Shing-Yi Tan

This Step assigns the Contact to:

  • A specific user
  • A user in a specific Team
  • A user in the Workspace
  • Unassigns the Contact

Configuration

There are two key configurations in the Assign To Step:

  • Action
  • Assignment Logic

In Action, Contacts can be directed to one of four assignment actions:

  • A specific user: Contact assigned to a chosen User
  • A user in a specific Team: Contact assigned to anyone in a chosen Team
  • A user in the Workspace: Contact assigned to any User in the Workspace
  • Unassign: Contact is removed from their assigned User or Team

Once you’ve selected an Action, decide how you want to distribute your Contacts across your Users with Assignment Logic.

In Assignment Logic, you can choose one of two options:

  • Assign to users round-robin: New Contacts assigned equally to every User in turn
  • Assign to the user with least open Contacts: Contacts assigned to the User with the fewest open Contacts
These options are only available for A User in a specific Team and A User in the Workspace assignment options.

Advanced Settings

There are two settings you can use that are independent of each other:

  • Only assign to online users: Contacts assigned to Users who are currently online.
  • Only assign to users with fewer than XX open contacts assigned to them: Contacts will be assigned to Users with fewer open Contacts than the specified threshold.
These two settings are only available for A User in a Specific Team and A User in the Workspace assignment options.

You can also add a Timeout Branch to your Workflow. This sets a specific timeframe within which a Contact should be assigned to a User.

The timeout period can be set for up to 7 days or the default period of 7 days will be implemented. Add Steps to define the journey for Contacts who do not respond in time, or the Workflow will end when the timeout is reached.

How It Works

Contacts will be assigned to Users based on certain assignment actions and conditions.

If Advanced Settings is switched ON and there are no Users meet the conditions, Contacts will wait in a queue until they get assigned or until the timeout period ends.

Potential Failure

There are three possible causes for failure in the Assign To step:

  • If the Contact isn’t assigned to anyone within the default 7-day timeout period, and there’s no Timeout Branch to continue the journey.
  • If the chosen User has been deleted from Workflows.
  • If the chosen Team a Contact is assigned to has no Users or is empty.

In such cases, the Contact will exit the Workflow.

Best Practices

Here are some best practices for this step you can follow to optimize your workflow:

  • Limit the number of Contacts each agent handles at a time, especially during high daily loads to avoid overwhelming them.
  • Manage customer expectations effectively by including a Send a Message Step after the Assign To Step takes effect. This automatically informs customers which agent will be handling their inquiry.

Suggested Use Cases

Here are some ways you can use the Assign To Step:

FAQ and Troubleshooting

What happens if there is no one in an Assign To team?

The Contact will not be assigned and will move on to the next Step. If there is no next Step, the Workflow will end.

Feeling stuck? Do not fear.

Need assistance? Contact us for support. Help is here!

Step: Ask a Question

Step: Branch

Can't find what you're looking for? 🔎

Talk to an expert here!

Contact Support
Company
About Us Roadmap Partner Program
Terms & Policies
Privacy Policy Cookie Policy Terms of Service
Resources
Developer Hub WhatsApp Pricing Calculator WhatsApp Link Generator
© 2024 Respond.io.
Status Security
ISO 27001 Certified.
Powered by HelpDocs (opens in a new tab)

Powered by HelpDocs (opens in a new tab)