Using the Remove Assigned User Workflow Action
What the Remove Assigned User Action Does
This workflow action automatically clears the currently assigned CRM user from a contact, leaving the contact unassigned. It’s commonly used when a contact no longer needs direct oversight—for example, after a sale closes or a support issue is resolved. By removing the assignment, the contact becomes available for other automated processes or future reassignment.
Benefits of Automatically Removing User Assignments
- Resets contact ownership: Clears user assignments so contacts can re-enter workflows or be assigned to new users.
- Reduces manual effort: Automates the unassignment process based on triggers like status changes or task completion.
- Improves team efficiency: Frees up users from contacts that no longer require their attention.
- Enhances workflow flexibility: Prevents outdated assignments from blocking contact movement between workflows.
How to Set Up the Remove Assigned User Action
Add the Action
In your workflow builder, click the “+” icon to add a new action step.
Select the Action
Choose “Remove Assigned User” from the list of available actions.
Name the Action
Give the action a clear, descriptive name—like “Clear Assignment After Task Completion”—to help identify its purpose in the workflow.
Save the Action
Since no additional configuration is required, simply save the action after naming it.
Test and Activate
Test the workflow to confirm it removes assignments correctly, then publish the workflow to make it live.
Common Use Cases
Sales Pipeline Management
Situation: A contact’s opportunity status changes to “Closed Won” or “Closed Lost,” meaning no further sales follow-up is needed.
Solution: Use a trigger like “Opportunity Status Changed” to activate the Remove Assigned User action. This unassigns the salesperson, freeing them to focus on active opportunities.
Customer Support Workflow
Situation: A support agent marks a task or ticket as completed for a contact.
Solution: Trigger the action when a task is completed. The agent is automatically unassigned, making them available for new support requests.
Frequently Asked Questions
What happens to a contact after the assigned user is removed?
The contact remains in the CRM but is no longer assigned to any user. It can be reassigned later through another workflow or action.
Can I use this action with multiple triggers?
Yes. The Remove Assigned User action can be triggered by various events—like task completion, status changes, or custom triggers—within the same workflow.
Does this action delete assignment history?
No. Previous assignments remain visible in the contact’s activity log and reports.
How can I avoid disrupting other workflows?
Test the workflow thoroughly before publishing and ensure the trigger conditions are specific to avoid unintended unassignments.
Can I reassign a contact immediately after unassigning?
Yes. Add an “Assign to User” action immediately after the Remove Assigned User action to reassign the contact to a new user right away.