Skip to main content

Workflow Action: Remove Assigned User

Discover how to effectively use the "Remove Assigned User" action in Stack to optimize your workflows. This guide will walk you through its purpose, benefits, and how to set it up, along with practical use cases and answers to common questions.

What is Remove Assigned User?​

The "Remove Assigned User" action in Stack is designed to unassign a user from a contact, leaving the contact without a direct user assignment. This is particularly useful when a contact's status changes, and they no longer need direct user attention. It allows for flexibility in managing contacts, enabling them to re-enter workflows or remain unassigned for future processing.

Key Benefits​

  • Reset Contact Assignment: Clears user assignments, allowing contacts to be re-engaged or reassigned as needed.
  • Automated Workflow Management: Automatically removes user assignments based on specific triggers, reducing the need for manual updates.
  • Improved User Availability: Frees up users to focus on contacts that require their attention.
  • Enhanced Workflow Flexibility: Facilitates seamless movement of contacts between workflows without outdated assignments.

Configuring the Action: A Step-by-Step Process​

Add the Action​

  1. In your workflow builder, click the "+" icon to add a new action.

Select Action​

  1. Choose the "Remove Assigned User" action from the list of available options.

Name the Action​

  1. Provide a descriptive name such as "Reset User Assignment" or "Clear Assigned User" to keep your workflow organized.

Save the Action​

  1. Once the name is set, click "Save" to finalize the action.

Test and Publish​

  1. Test your workflow to ensure it functions as expected, then enable the "Publish" toggle to activate it.

Use Cases​

Sales Pipeline Cleanup​

  • Scenario: A contact's opportunity status changes to "Closed Won" or "Closed Lost." The sales team no longer needs to follow up.
  • Solution:
    • Trigger: Opportunity Status Changed
    • Action: Remove Assigned User
    • Outcome: The contact is unassigned from the salesperson, allowing them to focus on active opportunities.

Task Completion in Customer Support​

  • Scenario: A support agent completes a task, such as resolving a ticket. The contact no longer requires direct assignment.
  • Solution:
    • Trigger: Task Completed
    • Action: Remove Assigned User
    • Outcome: The agent is unassigned, enabling them to manage new support tickets efficiently.

Frequently Asked Questions​

What happens to a contact after the assigned user is removed?

Once the assigned user is removed, the contact remains in the system without an active user assignment. It can be reassigned through other workflows or triggers.

Can this action be combined with multiple triggers in a single workflow?

Yes, you can combine the "Remove Assigned User" action with multiple triggers, such as "Task Completed" and "Opportunity Status Changed," to create dynamic workflows.

Will this action remove the assignment history?

No, removing an assigned user does not erase the contact’s assignment history. You can track previous assignments through activity logs or reporting tools.

How do I ensure this action doesn’t interrupt other workflows?

To prevent conflicts, test the workflow before publishing and review all trigger conditions carefully. Ensure the action is applied only where necessary.

Can I reassign a contact immediately after using the Remove Assigned User action?

Yes, after removing the current assignment, you can add a follow-up action in the workflow to reassign the contact to a new user using the "Assign to User" action.