All topics
Get started8Account, team & permissions44Units & fields70Records, views & tasks39WhatsApp & Cortex Chat68Email & social27Lead ads & distribution38Automations52Documents & quotes32Dashboards40Cortex AI18Developers & API12
Help Center·448 guidesAll topicsContact support

Distribute up to 100 clients at once from the table

Select the records in the table, press Distribute in the selection bar, and choose a scenario or a rule. They’re distributed one after another, and you get a report of every record that worked or failed, and why.

5 min

Lead distribution is a paid Add-on. If you can’t find it in your account, contact support to turn it on.

Before you start · 1 thing · for managers
An active scenario or rule
  • You need: Override lead assignment
  • An active scenario or rule.

Steps

1
Open the table view and filter the records, such as “Assignee is empty”.
2
Select up to 100 records.
3
Press Distribute in the selection bar, and under Distribute using, choose a scenario or a rule.
4
Turn on Reassign leads that already have an owner if some of them already have owners and you want to change them, and type the reason.
5
Press Distribute.
A report shows: how many worked, the list of failed records with the reason for each, and who got each record.

Why one at a time?

Each assignment moves the turn forward and adds to the employee’s capacity count. Distributing one after another makes sure that someone who reaches their limit at the 40th record doesn’t get the 41st, and that the turn really moves around.

Records are handled in the order you selected them.

A failed record doesn’t stop the rest

A record that has an owner and no replacing, or that you can no longer see, goes on the failed list, and the batch carries on.

Result
What it means
Full success
Every record was assigned.
Partial
Some failed; check the reasons.
Failed
No record was assigned.

This is also the way to redistribute clients who were left without an owner.

If something goes wrong

What you see
Why
What to do
Records failed because they already have an owner
You didn’t turn on replacing.
Run the batch again for the failed ones, with replacing on.
A record failed because it doesn’t exist or you can’t see it
It was deleted, or it’s outside your permissions.
The last records all failed
Everyone filled up during the batch.
Raise the limits, or finish later.

A real example

Shield Security Co.
The situation

An employee resigned and left 60 open clients.

What they did
  1. They filtered that employee’s clients in the table and selected them.
  2. They distributed them with the “Eastern team” scenario, with replacing turned on and the reason “Resigned”.
The result

All of the clients moved within a minute, and the reason is recorded on each client’s record.

A made-up company, to show the idea. The numbers are rounded.

Good to know

Up to 100 records per batch.
The same record can’t be in a batch twice.
A turned-off scenario or rule rejects the whole batch.
Did this guide solve it?
If not, we’ll ask what was missing.
Open in Corteksa
Did this guide solve it?

We read every answer. To get a reply, use Contact support.