Skip to content
Saudaflow

AI voice agent — in development. See how it works →

Get a demo
Pricing
Sign inDownload the Android app

Saudaflow is sold through a short call — we set up your workspace, your projects and your team with you. No card, no self-serve signup.

Routing Engine

The right lead, to the right agent, in 60 seconds.

Territory, language, current load, and past conversion all factor in. Round-robin when fair matters. Weighted when revenue matters. Spillover when speed matters.

Included in every plan. Zero setup fees, and we set your workspace up for you.

< 60s
p95 route time
4 modes
Round-robin / weighted / skill / spillover
Per-source
Rule overrides
WORM
Routing audit trail

Territory-aware from minute one

Plot agents on a map. Plot projects on a map. Inbound leads land with the agent whose territory matches the buyer's pincode or the project they enquired about.

  • Pincode + locality + project triangulation
  • Custom territories per builder
  • Cross-territory escalation when no match
  • Per-agent active radius override
TodayThu 6 Aug · 9 follow-ups due · 3 SVs
PSPriya Sharma3BHK · Lodha VistaHot₹1.85 Cr
RMRahul Mehta2BHK · Godrej MeadowsSV Sat₹1.12 Cr
AKAisha Khan3BHK · Prestige LakesideFollow up₹2.4 Cr
VPVikram Patil1BHK · Mira RdNew₹72 L
+ New lead

Language match — buyer + agent

A buyer enquiring in Marathi gets a Marathi-speaking agent. Same for Hindi, Tamil, Telugu, Kannada, Bengali. Reduces drop-off in the first 24 hours.

  • Buyer language detected from message + form
  • Agent languages on profile
  • Fallback chain: native → regional → English
  • Translation hand-off if no match
A WhatsApp enquiry becomes a lead — deduped, source-stamped, assigned.

Load-balanced — nobody gets crushed

Each agent has a configurable cap on open leads. Once they're at capacity, the engine routes around them. Manager can pause an agent without losing the queue.

  • Per-agent open-lead cap
  • Auto-pause on out-of-office
  • Manager override with audit
  • Caller availability + on-call awareness
A gate check-in, geo-pinned and timestamped, landing on the manager view.

Weighted by conversion track record

Agents who close the lead-source you're assigning get more of those leads. Trailing 90-day window. Auto-rebalances. Newcomers get a shadow allocation so they learn.

  • Per-source close-rate weighting
  • Trailing 90-day window, decayed
  • Shadow allocation for ramp-up agents
  • Manager can pin a high-value lead manually
The full break-up for A-1104, shared on WhatsApp and delivered.

Round-robin / weighted / spillover

Pick the mode that fits the source. Walk-ins: round-robin. 99acres high-intent: weighted. After-hours: queue-and-fan-out at 9 a.m. The engine just runs.

  • Per-source mode selection
  • Spillover threshold + target queue
  • After-hours queue, morning fan-out
  • Holiday-aware queue draining
The caller-ID banner drops before the second ring, with the lead attached.

Pause, reassign, recover — gracefully

Agent called in sick? Pause them — leads route around. Returning tomorrow? Resume — the queue picks up where it left off. No orphan leads.

  • One-tap pause from manager dashboard
  • Reassign in bulk with notification
  • Recovery audit: who got which lead, when, why
  • Lost-lead recovery: auto-reroute after N hours of silence
A stage advancing from Contacted to Site visit, with the visit fixed.
Private by design, audited by default

Routing rules are encrypted at rest. Lead fields used for routing (pincode, language) are decrypted only inside the per-tick evaluation window and re-encrypted before any audit-log write. Which agent got which lead — and why — stays inside your workspace; every staff access is audit-logged and visible to you.

See it for yourself.

30 minutes on your own pipeline, then we set the workspace up for you. Your leads, your team, your CRM.

Lead routing by territory, language and load · Saudaflow