Create an assignment rule
Build 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. It is one form with three stages and a single Save.
Before you start
- Assignment is on the Core and Max plans.
- Your role needs the create side of the Lead Distribution permission — listed in Settings → Roles as Lead Assignment.
- Have the lead source ready. You can type a brand-new source straight into the form, but only if your role can also create on the lead table. Otherwise you pick from the sources that already exist.
- Know who is receiving. You can add and remove members later, but a rule cannot be saved with nobody on it.
Steps
Open the form
Press New Rule in the top row of the Assignment screen. On an empty workspace, press New rule on the panel in the middle of the table instead.
The window that opens is titled New assignment rule. When you come back to change a rule later it is titled Edit assignment rule — the pencil on the row, Edit in the kebab on a phone, or Edit rule at the bottom of the sheet that opens when you tap a card. There is no read-only view of a rule; Edit is the only way in, and nothing is saved until you press the button at the end.
One continuous form. The rail on the left says where you are and what each stage currently holds.
It is one long scroll, not a set of tabs. The three stages are
| Stage | What it asks for | Needed? |
|---|---|---|
| Settings | The source, the condition that fires the rule, and how leads are handed out. | Required |
| Members | Who receives leads from this source, and what they see when one is offered. | Required |
| Reassignment | What happens to a lead nobody accepts or actions in time. | Optional |
On a computer the rail on the left carries a live summary of each stage, a tick when it is complete or an amber circle when it is not, and a count underneath — 2 of 3 complete. Clicking a row on the rail jumps the scroll to that stage. On a phone the rail is a row of three chips: Settings, Members and Reassign.
Pick the lead source
Open the dropdown at the top. If your role can add lead sources the placeholder reads Select or add a lead source… and you can type a name that does not exist yet to create it — a toast confirms Lead source “Facebook Ads” ready. If it reads Select a lead source… you can only choose from the list.
A rule can never be pointed at a different source afterwards. When you edit an existing rule this field is a locked row with a padlock and the sentence A rule is bound to its lead source and can’t be re-pointed. To route a different source, create a new rule for it. Choose carefully now; the only undo is a new rule.
Choose which leads the rule takes
Under When it runs, the Trigger dropdown has three options:
- When lead fields match — filter on the value of dropdown fields.
- When lead date matches — filter on when the lead arrived or was last worked.
- When fields AND date match — both at once.
A Field filter appears for the first and third. It is a stack of blocks, one per field, with the word and printed between them: every block has to match, and within a block any one of the values you pick is enough.
- The Status block is always first and cannot be removed. It shows as a locked token with the caption always part of the criteria.
- Status leads with an Any pill, then the statuses themselves. Any is lit while you have picked nothing, and it means “do not filter on status at all”. Picking a status clears it.
- Add field adds another field block — up to three fields on top of Status. The button stops being offered once every dropdown field is in use, and is greyed out at the limit.
- Other fields have no Any pill. Leaving one empty is not “any value”, it is unfinished: Pick one appears beside its pills and the save is refused. To stop filtering on a field, delete its block with the trash button.
- If your database has no dropdown fields at all, the area reads No dropdown fields configured., and a field with no options of its own reads This field has no options.
Status is always in the condition. Any means do not filter on status — it is not the same as an empty block below.
A Date filter appears for the second and third options. Pick the date to compare — Added date or Last actioned date — then the comparison:
- is older than asks for an age and a unit: Minutes, Hours or Days.
- is before or is after ask for a calendar date.
A rule that constrains nothing is perfectly legal: it reads all leads in the table and takes everything that arrives on its source.
Decide how leads are handed out
Assignment timing — two tiles:
| Tile | On the tile | What happens |
|---|---|---|
| Real-time | Assign leads the moment they arrive. | Each lead goes out as it lands |
| Batch | Collect leads and assign them on an interval. | Reveals Batch interval and Unit (Minutes / Hours / Days), minimum 1 |
Assignment method — two more:
| Tile | On the tile | What happens |
|---|---|---|
| Round robin | Offer each lead to one member at a time, in turn. | One person is asked, then the next, in rotation |
| Shotgun | Offer to every member at once; first to accept wins. | Everyone is offered the lead and the first to accept keeps it; the rest lose the offer |
A new rule starts on Batch, 30 Minutes, Shotgun. Change what you need and leave the rest.
Choosing Round robin reveals one more switch, Auto-acceptance: Skip the accept/decline prompt and assign each lead to the next member automatically. Turn it on and nobody is asked to accept — the lead simply lands with the next person in the rotation.
Auto-acceptance removes the response window entirely. With it on there is no accept step to time out, so Response timeout disappears from the Reassignment stage and from every advanced rule. Switch the method back to Shotgun and it comes back. Nothing on the Reassignment stage explains where it went — this switch is the explanation.
Timing on one side, method on the other. Auto-acceptance only appears with Round robin.
Leave Advanced configuration alone unless you need it
The last group on this stage, Advanced configuration, is closed by default — Fine-tune how this rule treats manual and settled assignments. It opens itself if either switch inside is already on.
| Switch | What it does |
|---|---|
| Overrule manual assignment | Allow this rule to re-assign leads a member assigned by hand. Off by default, manual assignments are left untouched. |
| Protect settled assignments | Skip leads that have already been accepted, so moving them between sources won’t hand them to a different rule. |
Add the people who receive
Scroll on to Members. The heading counts as you go — Team members (3) — and the line under it is the whole capacity story: Everyone here receives leads from this source, with no daily cap. There is no per-person limit and no ranking; everyone on the rule is in the rotation.
Press Add members. A window titled Add team members lists the workspace with a Search members… box; tick the people you want. Anyone already on the rule is ticked, locked, and marked Already added. The button at the bottom counts only the new ones — Add (2 new). If the search finds nobody you get No members found / Try a different name or email.
Each row on the rule then shows a gear (Working hours) and a trash (Remove) on the right. Working hours are the one thing here that saves on its own, immediately — they belong to the person, not to this rule, so they stay set even if you cancel out of the form. See Choose who receives leads.
- A red Paused pill on a row means that member is not being sent leads from this source. You cannot change it here — pausing lives on the Members view, in Choose who receives leads.
- A row reading Removed member and a number, with No longer in this workspace — remove them from this rule. underneath, is somebody who has left. Nothing cleans those up for you; press the trash.
- With nobody on the rule you get No members assigned yet and an Add your first member button. The rule cannot be saved in that state.
Choose what the assignee sees
The second group on this stage is What the assignee sees: Pick which lead fields the assignee can see when the lead is offered to them. Required fields are always shown. Tick the fields you are happy to show. Required fields are already ticked, cannot be unticked, and are marked (required). If your database has nothing shareable the area reads No shareable fields configured.
Under the grid, Show lead details before accept — When on, the assignee can see the visible fields above before deciding to accept. With it off, the person being offered the lead sees only New lead and the line Details hidden by assignment settings until they accept.
Who receives, and how much of the lead they can see before they answer.
Save the rule
The bottom of the window tells you whether you can. On the left, amber Still needed: Settings, Members naming what is unfinished, or green Ready to save. On the right, Cancel and Create assignment — or Save changes when you are editing.
It is one save. The settings, the members and the reassignment go in a single request, so a failure never leaves you with half a rule. A toast confirms Assignment created or Assignment updated. If you changed nothing on an edit you get No changes to save. and the window closes.
If something is missing, the save stops, a red toast names the problem, and the form scrolls to the control at fault and focuses it. The messages are in the table at the end of this page.
Reassignment is optional, and a new rule starts with none. If you want leads that nobody answers to move on, do that stage too — Reassign leads nobody answers.
Closing without saving
Cancel, the ✕, Esc, or a swipe down on a phone. If you have changed anything you are asked first: Discard unsaved changes? with Keep editing and Discard & close. A form you have not touched closes without asking.
Turning a rule off, and deleting it
- The Enabled switch on the row takes effect immediately — Assignment enabled / Assignment disabled — and flips itself back if the server refuses. A disabled rule stops taking new leads and keeps everything it has already done.
- Delete asks first: Delete assignment rule? — This rule will stop distributing new leads. Existing lead assignments stay where they are. So deleting a rule never un-assigns anybody. Success reads Assignment rule deleted.
If you only want to stop leads reaching one person, do not touch the rule. Pause them instead: Choose who receives leads.
Limits worth knowing
- Status plus three other fields in one condition. Add field is greyed out at that point.
- Any time you type is capped at 90 days — 129,600 minutes, 2,160 hours, or 90 days. Change the unit and the number is re-capped, so 500 minutes becomes 90 when you switch to days.
- Batch interval and the is older than age both start at 1; neither can be 0.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Pick a lead source. | Nothing is selected in the first dropdown | Choose a source. On an edit this cannot happen — the source is locked |
| Set a batch interval greater than 0. | The timing is Batch and the interval is empty or 0 | Type how long to collect for, or switch the timing to Real-time |
| Pick at least one option for every field in the condition. | A field block below Status has nothing ticked, and shows Pick one | Tick a value, or delete that block with its trash button |
| Enter how old a lead must be — the age must be greater than 0. | The date comparison is is older than with an age of 0 | Type an age of 1 or more |
| Pick the date this rule compares against. / That isn’t a valid date. | is before or is after with no date, or a date the form cannot read | Choose the date from the calendar rather than typing it |
| Add at least one team member. | The Members stage is empty | Press Add members and tick at least one person |
| Advanced reassignment needs at least one rule. | The mode is Advanced with an empty list | Add a rule, or change the mode — see Reassign leads nobody answers |
| Rule 2: set a time greater than 0. | An advanced reassignment rule has a duration of 0, which there would mean “immediately” | Give it 1 or more |
| The save fails with a message about another rule matching the same leads | A rule already on this source could take the same leads as this one | Narrow one of the two conditions so they describe different leads |
| Response timeout is not on the Reassignment stage | The rule is Round robin with Auto-acceptance on, so there is no accept step to time out | Leave it, or turn auto-acceptance off, or switch the method to Shotgun |
| Add field has gone | Every dropdown field is already in the condition, or you are at the limit of three besides Status | Remove a block you no longer need |
| The lead source dropdown has a padlock on it | You are editing an existing rule, and a rule is bound to its source | Create a new rule for the other source |
| A Paused pill on a member cannot be clicked | Pausing is read-only inside the rule | Change it on the Members view — Choose who receives leads |
| Couldn’t add the lead source “Facebook Ads” | Creating the source from inside the form did not go through | Try again, or add the source first and then come back to the rule |
| You cannot delete the lead source itself | A source cannot be deleted while an assignment rule still points at it | Delete the rule first, or keep the source and disable the rule with its Enabled switch |
| Failed to save assignment | The save was refused and no reason came back | Nothing was half-saved. Try again, and if it repeats send us the source name — message support |
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.
- Reassign leads nobody answersDecide 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.
- 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.