Distribute leads, tickets, and any CRM records across your team with assignment logic round-robin cannot express: balance existing workloads, cap each rep’s book, skip whoever is out today, previewed before it runs, automated after.
Records
24
Assigned
24
Unavailable reps
1
| Lead | Owner (Before) | Owner (After) | Available |
|---|---|---|---|
| Acme inquiry | , | Jane | Yes |
| Northstar demo | , | John | Yes |
| Vertex trial | , | Jane | Priya: No |
Insycle turns record assignment into a controlled sequence: segment records with CRM filters, choose a distribution method, let availability and capacity constrain the result, preview every before-and-after owner, then automate the saved policy with a complete audit trail.
Native routing deals records like cards: next rep, next rep, next rep. It cannot see that Jane already holds forty open leads and John has nine, that Priya’s book hit its cap on Tuesday, or that Marcus is unavailable until Monday. The hot lead lands in an empty chair and speed-to-lead dies in the queue.
How workload-aware assignment works
First, segment the records with any CRM fields. Next, choose Balanced, Weighted, Even, or Random distribution. Then let the schedule and limits you set in Insycle determine who can receive each record. Preview the complete owner change in a CSV, run the update, and automate the saved template so the policy keeps operating.
Any field in the database can define the routing pool: unowned Technology contacts, EMEA deals over $50,000, or tickets tagged enterprise. Save one template per segment, then chain enterprise, mid-market, and general queues into a Recipe.
Assignment targets are reference fields, so the same engine can assign contact owners, deal owners, ticket owners, and several owner fields in one pass.
Technology inbound queue
Contact Owner
Reference field
Does not exist
Unowned only
Industry
Contact field
Equals Technology
Segment
Lead Status
Contact field
Equals New
Ready to route
Looks at how many records each rep already holds and distributes the new ones so everyone lands level. If 24 leads arrive and Jane starts with 10 while John has 5, Balanced sends Jane 2 and John 7, twelve each.
Fairness measured by outcome, not turn-taking.
Express deliberate unevenness in one number per rep: two records to each senior rep, one to the ramping hire, cycling in order.
A saved template remembers where it left off, so distribution remains even across runs, not only inside one run. Nineteen records across three reps become 7, 6, and 6.
The coin flip for situations where policy genuinely does not care which available rep receives the next record.
Distribution method
Balanced
Period
Last 30 days
Assign to
Contact Owner
Assignees
Jane · John · Priya
Every method consults Availability before assigning. An unavailable rep is skipped under Balanced, Weighted, Even, and Random alike.
Enter each rep’s working schedule once in Insycle, and every distribution method routes around it automatically. For vacation or leave, one Unavailable toggle removes a rep from every routing template at once, no pool edits and no template surgery.
Turn the toggle off and the rep resumes exactly where they left off. A rep with no schedule entered is treated as always available.
Coverage stops being a fire drill.
Jane Morgan
Mon-Fri · 9:00-5:00
John Smith
Mon-Fri · 8:00-4:00
Priya Kapoor
Vacation · resumes Monday
Control how much new work a rep receives today and how large their total book is allowed to become.
The per-run ceiling: no more than a set number of new records goes to any rep during one operation.
The book-size ceiling: Insycle checks what each rep currently holds and stops assigning when that total reaches the cap.
Records that exceed every cap appear as Not assigned in the CSV instead of being force-fed to someone.
Cap Per Rep
12 total
Assign Per Rep
8 this run
Preview mode produces the routing receipt: Owner (Before), Owner (After), the Assignees pool, and an Available column showing exactly who the distribution could see at run time. Adjust the policy, re-preview, and only then run Update.
Every preview and update lands in the Activity Tracker with before-and-after detail and the Run ID written back to the affected records.
Evaluated
486
Ready
472
Not assigned
14
| Record | Before | After | Available |
|---|---|---|---|
| Contact 1042 | , | Jane | Yes |
| Contact 1043 | , | John | Yes |
| Contact 1044 | , | Not assigned | Cap reached |
Save every segment as a template, the required container for the assignment history Balanced reads and the rotation memory Even preserves. Schedule templates hourly to monthly, chain them into a Recipe, or trigger the Recipe from a HubSpot Workflow so new contacts receive an owner within minutes.
The morning triage meeting becomes a report you glance at.
Check current load per rep in Group & UpdateSegment template
Enterprise · mid-market · general
Distribution method
Load · cap · availability
Owner assigned
Schedule · Recipe · HubSpot Workflow
Data Logic
This industry, size, and region maps to this territory, tier, team, or named owner, deterministic ownership declared in a Blueprint and measured for coverage and drift.
Assign
When the segment routes to a five-rep pool, Assign chooses who receives this record based on current load, caps, and who is available.
Deterministic ownership belongs in a Blueprint. Dynamic distribution belongs here. Most routing policies need both.
Explore Data Logic| Capability | Native round-robin | Manual triage | Insycle Assign |
|---|---|---|---|
| Distribution logic | Turn-taking | Manager judgment, when available | Balanced, Weighted, Even with memory, Random |
| Sees current workload | No | Sort of, from memory | Yes, Balanced reads each rep’s existing load |
| Book-size caps | No | No | Cap Per Rep checks current holdings first |
| Rep schedules | No | If the manager remembers | Availability per rep; one toggle for leave |
| Overflow behavior | Assigned anyway | Sits in the queue | Held as “Not assigned,” visible in the report |
| Dry run | No | , | Preview CSV: before/after, pool, and availability |
| Segments | Limited criteria | Whatever the manager scans | Any field, templated by segment, chained in Recipes |
| Audit | Thin | None | Activity Tracker and Run ID per record |
Teams use assignment rules to route new records the moment they arrive, balance workload across owners, and keep leads out of empty queues.
“It has been a game changer in automating the cleanup of my CRM data. I like the flexibility of creating custom recipes to use in workflows.”
Zachary K. · Marketing Operations Manager · Enterprise
G2 reviewRound-robin gives the next record to the next available rep. Balanced first counts how many records each rep already holds, then distributes new records so their resulting workloads are level. Even is Insycle’s traditional round-robin method and remembers where it stopped across runs.
Yes. Set each rep’s working schedule in Insycle and use the Unavailable toggle for vacation or leave. Every distribution method skips unavailable reps. Insycle does not claim to read Google or Outlook calendars; it follows the schedule you maintain in Availability settings.
Yes. Cap Per Rep checks each rep’s current holdings before assigning and stops at the book-size ceiling. Assign Per Rep separately limits how many new records a rep can receive in one operation. Overflow remains “Not assigned” in the report.
Yes. Use any CRM field to filter records into a segment, then apply a distribution method to that pool. For deterministic territory mapping, use Data Logic first to choose the team; use Assign second to distribute within that team.
Yes. Preview mode shows Owner Before, Owner After, the assignee pool, availability, and any not-assigned records before any owner field changes. Every preview and update is recorded in the Activity Tracker.
See the exact owner change, assignee pool, availability, and overflow before the routing policy goes live.
From assignment to integrity
Assign writes the owner. Observability notices when another process changes it and the record no longer matches the logic that assigned it.
See how teams monitor ownership logic
HubSpot
Salesforce
Pipedrive
Intercom
Mailchimp
