Reassign leads nobody answers
Decide what happens to a lead that sits unanswered, or gets accepted and then forgotten: hand it back to the pool after a set time, or write a chain of rules that move it on when its status, its age or its last update says so. This is the third stage of an assignment rule.
Before you start
- You need a rule to put it in. Open one with the pencil on its row, or build one first — Create an assignment rule.
- Reassignment needs more than the base assignment package. If the tiles are locked, the panel above them reads Reassignment requires the Redistribution package or higher. Contact your workspace admin to upgrade. Advanced needs a higher package than Simple, and a tile you cannot use carries a padlock and an Upgrade pill instead of being clickable.
- A new rule reassigns nothing. Every rule starts on No reassignment until you change it here.
Steps
Open the Reassignment stage
In the rule form, press Reassignment on the rail down the left — or Reassign, the third chip, on a phone. It is the same long scroll, so you can also just keep scrolling past the members.
Under the heading: What happens to a lead nobody accepts or actions in time. This stage is optional; the rule saves without it.
Pick a mode
| Tile | On the tile | What it does |
|---|---|---|
| No reassignment | Leads stay with the original assignee. | Nothing is ever moved. Always available |
| Simple | Reassign after fixed response / update timeouts. | One pair of timeouts for the whole rule |
| Advanced | Custom rules per condition (status, date, etc.). | An ordered chain of rules, each with its own condition and its own target |
Choosing No reassignment replaces the settings with a panel reading No reassignment configured — Leads assigned through this rule stay with the original assignee. Pick Simple or Advanced above to reassign on a timeout or a condition.
Set the two timeouts, if you chose Simple
Simple is two clocks: one for the offer, one for the lead afterwards.
| Field | Under the field | What it measures |
|---|---|---|
| Response timeout | Not accepted in time, reassign. 0 = off. | The offer was never accepted |
| Lead update timeout | Not actioned in time, reassign. 0 = off. | The lead was accepted, and then nothing happened to it |
Each is a number plus Minutes, Hours or Days.
0 means off, not “immediately”. A timeout of 0 never fires. If you set both to 0 the panel tells you — Both timeouts are off, so this rule won’t reassign anything. Set one, or switch to No reassignment. — but the rule still saves, and it will sit there reassigning nothing.
If the rule is round robin with auto-acceptance on, Response timeout is not there at all. The lead is taken the moment it is assigned, so there is no offer to expire; only Lead update timeout is left, and the warning above becomes The lead update timeout is off, so this rule won’t reassign anything. Set it, or switch to No reassignment. Turn auto-acceptance off, one stage up, and the field comes back.
Or build a chain, if you chose Advanced
Press Add rule under Advanced rules (0). An empty list reads No rules yet — Add a rule to define the condition that reassigns a lead.
Order decides everything. Once you have two rules a line appears above the list: Checked in order — the first rule whose condition matches wins. Drag a rule by its handle to reorder. Put your most specific rule at the top; a broad rule sitting first will catch leads the ones below it were written for.
Each rule is a card, numbered, with a one-line summary while it is collapsed — no update for 2h → Aisyah, added date older than 30m → the pool, or any status change → the pool for one you have not filled in yet. Adding a rule opens the new one and collapses the others, so you write them one at a time. Nothing is lost when a card folds.
Drag a card by the handle on the left to move it, or select the handle and use Arrow Up and Arrow Down. The order changes as you drag; Esc during a drag puts everything back where it was.
First match wins, so the order of these cards is the rule.
The switch on a card turns that one rule off without deleting it — it then shows a Disabled pill. The trash beside it (Remove) deletes it.
Fill in one advanced rule
An open card has three bands.
When it fires, who gets the lead, and what else should happen.
When — the Trigger condition dropdown:
- Status change — reveals From statuses and To statuses. It fires when a lead moves from any status you picked on the left to any status on the right.
- No update within time limit — reveals Trigger after no update for, a number plus Min, Hours or Days.
- Date-based — reveals Base date (Added date or Last actioned date), Comparison (is before, is after or is older than), then either a Threshold for is older than or a Date to compare with, and a list of Statuses this date rule applies to.
A duration on an advanced rule cannot be 0. Here 0 would mean “the moment it arrives”, so the save is refused with Rule 2: set a time greater than 0. The smallest value is 1, and new rules start at 30 Minutes.
Then reassign to — two tiles:
- Pool of members — The next available member from this rule’s member pool.
- Specific member — Always the same designated backup user. Choosing it reveals Backup user (Select a member…), which offers everybody in the workspace, not only the members on this rule. That is how an escalation desk or a supervisor gets the lead without joining the rotation.
Then the same two clocks as Simple — Response timeout and Lead update timeout — this time for leads this rule has moved.
Also — three switches and a field list:
| Switch | What it does |
|---|---|
| Send notification | Notify the assignee when reassignment fires. |
| Blacklist member | Mark the original member blacklisted on this rule when triggered. |
| Remove record | Drop the lead’s previous-assignment record after reassignment. |
Blacklist member is how somebody stops receiving leads without anybody touching the Members view: the person the lead was taken from is paused on this rule. You will see them afterwards on the Members view with a red Paused sub-line and a N paused chip, and that is where you resume them — Choose who receives leads.
Visible fields when reassigned decides how much of the lead the new assignee sees — Required fields are always shown. Required fields are padlocked pills you cannot un-pick, with the tooltip Always shown — this field is required.
Save the rule
Reassignment is saved with the rest of the rule: Create assignment, or Save changes when you are editing. There is no separate save on this stage, and no half-saved state — see Create an assignment rule.
Two settings on the person, not on the rule
Both live behind the gear on the Members view, and both save immediately — they are not part of the rule’s save, and they apply to that person on every rule they are on.
- Off-hours reassignment — Reassign leads that arrive outside this member’s working hours to the next available member.
- Holidays — a date range someone is away. Its own description says leads will not be assigned to them during it.
Both are set up in Choose who receives leads.
How long a timeout can be
- 90 days is the ceiling for any duration — 129,600 minutes, 2,160 hours, or 90 days.
- Changing the unit re-caps the number, so 500 minutes becomes 90 when you switch that field to days. Check the number after changing a unit.
- Simple timeouts can be 0, meaning off. Advanced ones cannot.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Reassignment requires the Redistribution package or higher. Contact your workspace admin to upgrade. | The workspace’s assignment package does not include reassignment | Only No reassignment is available until the package changes. Ask whoever manages the subscription |
| A tile with a padlock and an Upgrade pill | That mode needs a higher package than the workspace has. Advanced needs more than Simple | Use the mode you do have, or ask about upgrading |
| Response timeout is missing | The rule is Round robin with Auto-acceptance on, so no offer ever waits to be accepted | Turn auto-acceptance off on the Settings stage, or switch the method to Shotgun |
| Both timeouts are off, so this rule won’t reassign anything. Set one, or switch to No reassignment. | Both are 0, and 0 means off | Put a number in one of them |
| The rule saved but nothing is ever reassigned | Most often both timeouts are 0, or the mode is still No reassignment | Open the rule and check this stage. The row’s Reassignment pill reads Simple · off when it is 0 |
| Advanced reassignment needs at least one rule. | The mode is Advanced with an empty list | Press Add rule, or choose Simple or No reassignment |
| Rule 2: set a time greater than 0. | The second card in the chain has a duration of 0 | Give it 1 or more. 0 is only allowed on Simple timeouts |
| The wrong rule in the chain is firing | The chain is checked top to bottom and the first match wins | Drag the more specific rule above the broader one |
| The cards you had open all collapsed | Adding a rule opens the new one and folds the rest | Nothing is lost. Press a card’s summary to open it again |
| A number you typed changed by itself | Durations are capped at 90 days and re-capped when the unit changes | Retype it after choosing the unit |
| Someone stopped getting leads and nobody paused them | A rule with Blacklist member on reassigned a lead away from them, which pauses them on that rule | Resume them on the Members view — Choose who receives leads |
Next
- Choose who receives leadsStop sending leads to someone who is on leave, on a course or off the floor — for one lead source or for all of them — and set the hours and holidays assignment should work around.
- Create an assignment ruleBuild the rule that decides who gets the leads from one lead source: which leads it takes, whether they go out one at a time or to everybody at once, who receives them, and what those people see.
- How assignment worksAssignment hands each new lead to someone on your team the moment it arrives, so nobody has to sit and share out a list by hand.