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

Lead distribution: how Corteksa decides who gets each new client

The Distribution Engine assigns every new record with no owner to an employee, following rules you set: which clients the rule covers, who gets them, by which method, and what happens if no one is available.

8 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 · 2 things · for owners and managers
Active employees, a unit for clients
  • You need: View distribution rules (to see them), and Create distribution rules (to set them up)
  • Active employees.
  • A unit for clients.

How it works

You find distribution in Settings → Distribution Engine. The engine works in the background, within seconds of the record being created.

The decision in four stages

Stage
The question
Guide
1. Rule order
Which rule is checked first? The most specific, then the priority.
2. Matching
Is the client from the right sessions, and are the conditions, such as the source, met?
3. Eligibility
Which of the assignees is active, within their working hours, and under their capacity?
4. Choosing
Who gets the client among the eligible ones?

If a rule matches and no one is eligible, its fallback applies: Leave Unassigned, Assign to Default User, or Delay and Retry.

When does automatic distribution run?

How the record is created
Distributed?
From the app, the mobile app, the API, a public form, the assistant or an automation
Yes, if it has no owner
A new chat that creates a client in Cortex Chat
Yes
Yes
Only the rows with no owner
Moving the record to another unit
No
A record created with an owner
No; the manual choice is respected

Automatic distribution runs once, when the record is created. To redistribute existing records, use manual distribution or bulk distribution, with the option to replace the current owner.

Rules and scenarios

A rule runs on its own on new clients. A scenario is only a list of employees and a method, which you use by hand or from an automation. An active rule also works for manual distribution.

The tools

Tool
What it’s for
Try a sample client and see which rule would catch it and who would get it.
The number of assignments for each employee and each rule.
Why this client went to this employee, and who changed the rule.
The employee knows straight away that a client was assigned to them.
Distribute from inside a workflow.

All the numbers are in Every lead ads and distribution limit in one place, and all the errors in Fix lead ads and distribution problems.

If something goes wrong

What you see
Why
What to do
A new client with no owner
No rule matches, or no one is eligible.

A real example

Namaa Academy
The situation

Two senior employees want 30% each, and the two new employees 20% each. Clients arrive until midnight.

What they did
  1. A rule with the Weighted Fair method, at 30/30/20/20.
  2. Working hours for each employee, and a limit of 15 clients a day.
  3. A fallback: Assign to Default User, set to the sales supervisor.
The result

Distribution matches the shares at the end of every week, and night-time clients go to the supervisor instead of staying without an owner.

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

Good to know

Only active rules run, and each rule works on one unit.
The first matching rule that has an eligible employee wins.
Deleting a rule doesn’t change the clients it assigned.
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.