Automation engine
The right lead, on the right desk, without anyone watching.
Compass turns lead assignment into a set of rules you can read out loud. If the score is over 80, send it to the senior team. If the budget is under 1 Cr, send it to Town Center. Capacity-aware, fair, with quiet hours, fallbacks, and a complete audit trail on every lead.
Anatomy of a rule
When this is true, do that. In plain words.
Every rule has three parts: when it fires, what it checks, and what it does. We resisted the urge to build a programming language. A team lead writes a rule in a minute, reads it back the same day, and changes it the next week.
When
If
score ≥ 80 AND budget ≥ ₹2 Cr AND source = websiteThen
- Assign to Senior Sales (round-robin, capacity ≤ 12/day)
- Set SLA: first-touch within 15 min
- Send WhatsApp template welcome-priority
- If untouched after SLA, escalate to Anika (team lead)
The condition library
Conditions are everything the lead is, and everything the day is.
You can branch on what the lead carries (the score, the extracted profile, the source) and on what the world is doing (capacity, time of day, day of week, who is on shift). Combine with AND or OR. Negate with NOT. Group with parentheses.
Score
Intelligence-engine score
Hot, warm, cold, or a numeric threshold (≥ 80, ≤ 40).
Profile
Extracted preferences
Layout, location, budget band, urgency, financing signal.
Source
Where the lead came from
Organic, paid campaign, partner, referral, walk-in.
Language
Detected from form or browser
Routes Hindi or Marathi leads to a rep who speaks them.
Company
Which Compass company
Cross-company rules are vendor-admin only.
Project
Project interest, if expressed
Map to the team that owns the project.
Time of day
And day of week
Different rules for weekends, late nights, festivals.
Capacity
Live team capacity
Skip teams over their daily ceiling, fall through to the backup.
The action library
Assignment is the first action, but never the last.
A rule can route a lead, set an SLA, post a WhatsApp message, pin a follow-up, escalate after a quiet window, or all of the above in sequence. Actions are composable. They run in the order you list them. Failures fall through to the next rule.
- 01
Assign to a team
Round-robin or weighted, capacity-aware, with named fallbacks.
- 02
Assign to a specific rep
For high-value leads with a relationship history, or for VIPs.
- 03
Set or shorten the SLA
Hot leads inherit a 15-minute clock, cold leads a 24-hour clock.
- 04
Send a templated message
WhatsApp, email, or SMS. Templates are versioned and approved.
- 05
Escalate on silence
If untouched after the SLA, route up. Twice, then to the company admin.
- 06
Tag and segment
Apply tags that downstream reports and exports can group on.
Fairness primitives
Routing is easy. Routing fairly is the work.
An assignment system that always picks the same star rep burns out the star and starves the bench. Compass ships with the fairness primitives you would otherwise rebuild yourself, the hard way, three times.
Round-robin
Even distribution by default.
Within a team, leads cycle through reps in order. The newest joiner gets their share from day one.
Capacity ceilings
Daily limits per rep.
When a rep is at their cap, the engine skips them. Caps are set by the team lead, not a ticket.
Quiet hours
Respect the clock.
No assignments after 9pm. Held leads release at 9am, with the SLA recalculated.
Fallbacks
Every rule names its backup.
If the primary team is at capacity, the fallback team is named in the rule itself, not improvised at midnight.
Worked examples
Three rules a team actually writes on day one.
- Rule 01On lead create or re-score
Hot leads go to the senior team
If
- score ≥ 80
- budget ≥ ₹2 Cr
Then
- Assign to Senior Sales (round-robin, cap 12/day)
- SLA: first touch in 15 minutes
- WhatsApp 'priority-welcome' template
- Escalate to team lead on silence
Score-based priority routing for the leads most likely to convert.
- Rule 02On lead create
Sub-1 Cr leads go to the Town Center team
If
- budget < ₹1 Cr
- project interest in Town Center or unspecified
Then
- Assign to Town Center Sales (round-robin)
- SLA: first touch within 30 minutes
- Tag 'affordable'
Budget-based routing to the team that owns affordable inventory.
- Rule 03On lead create
Late-night leads wait until morning
If
- time between 21:00 and 09:00 IST
Then
- Hold lead in queue, do not assign yet
- At 09:00, run the standard routing rule
- Send 'received-overnight' acknowledgement to the buyer
Respect quiet hours. Hold the lead, ping the rep at 9am.
The audit trail
Every routed lead knows which rule sent it where, and why.
When a rep asks "why did I get this lead," the answer is one click away. When a manager asks "why didn't I get this lead," the answer is also one click away. The audit trail records the rules that fired, the rules that considered the lead and skipped it, and the final disposition.
- 09:14:02Lead createdSource: website, score 92
- 09:14:02Rule evaluatedhot-leads-to-senior-team · matched
- 09:14:02Rule skippedsub-1cr-to-town-center · budget condition failed
- 09:14:02AssignedSenior Sales · @priya (round-robin)
- 09:14:02SLA setFirst-touch · 15 min
- 09:14:03WhatsApp sentpriority-welcome v3
- 09:29:11First touchCall connected · 47s · disposition: callback
Keep reading
Routing is half the battle. The other half:
- Lead intelligenceScore the lead before you route it.Routing on score is only as good as the score. The intelligence engine is what makes the rules worth writing.Read
- InventoryPair the lead to a unit, not just a rep.Match the extracted profile against live inventory. The rep walks in with two specific units to offer.Read
- SecurityRouting across companies is contained.Vendor admins write cross-company rules. Company admins cannot. The model enforces itself.Read
Next
Show us your estate. We will show you ours.
A 30-minute working call. Bring a real brand, a real project, and a real role. We will run the workspace against your actual hierarchy.
Reply within 24 hours, IST business days. Calls scheduled in your timezone.