The reassignment action in Automations can be used to reassign a lead to a specific agent, first to claim group, round-robin group, pond or lender. When a reassignment happens because of an automation, the person, group or pond will be notified per usual.
How to use Reassignments
Reassignments can be triggered by a new property inquiry, a new saved or viewed the property, a tag being added or a stage being changed so you can customize your workflow whichever way you'd like! Here are some ideas to get you started:
When an existing lead has a new inquiry and hasn't been contacted in 90 days and was created more than 90 days ago and is not in the nurture, past client or closed stage, reassign the lead to a first to claim group.
Try it out!
Using Reassignments with other Actions
Reassignments can be used along with adding a note and starting an action plan. The reassignment will always happen before the Note is added or the Action Plan begins. This ensures that all merge fields will be correctly filled out.
Using Reassignment with First to Claim Groups
When using a FTC group in the reassignment step, the other actions will happen immediately. That means that the current assignee will be used in the merge fields.
Reassigning leads who haven't been followed up with
To find the best ways to reassign new leads that haven't been followed up with yet, check out this Recipe: Automatically reassign lead if no contact attempts have been made.