Your sales playbook, automated.
With a source connected and routing enabled, route a lead by locality. Remind the owner when a lead passes its configured idle period. Set a follow-up after a lead-stage change.
Routing rules come with Professional Team and Custom, and we set your workspace up with you.
Trigger → condition → action — that's it
No code, no Zapier subscription, no glue. Pick a trigger that already exists in SaudaFlow, add the conditions that matter, choose the action. The engine runs server-side and is rate-limited per tenant.
- Triggers: lead created, stage changed, visit missed, booking created or cancelled, document status changed
- Conditions: up to five, on the event's fields, all must hold
- Actions: notify people; on lead events, follow up or reassign
- Dry-run mode before you arm it
Lead routing that knows your team
Route incoming leads by territory, language, project or load. Round-robin that skips anyone unavailable, weighted shares you set, or spillover when an agent hits their cap.
- Territory + language + project + load
- Round-robin / weighted / spillover
- Unassigned leads stay visible in the queue
- Pause routing per agent without losing the queue
Follow-ups — tracked on a clock
New lead → first-response target (30 minutes by default), flagged when missed. Log the call and choose the next follow-up. Quiet for your configured period → an owner reminder.
- Due and overdue follow-up reminders for every owner
- Closed leads leave the lead follow-up clock
- Per-source routing (99acres vs MagicBricks vs walk-in)
- First-response targets and overdue leads
Notifications that earn the buzz
Choose alert channels by role and person: in-app, push to the Android app and e-mail. Delivery follows your preferences.
- Quiet hours per user
- Only critical alerts break quiet hours
- Push caps per person
- A digest of what quiet hours held back
Rules you can read and change
Each rule is a trigger, up to five conditions and up to three actions. Every change is in the audit log, and a rule that keeps failing switches itself off and tells your admins.
- Booking cancelled → tell finance
- Lead stage changed → notify a person
- Lead stage changed → follow-up next day
- Document status → notify a role
Test before you arm it — every rule
Dry-run a workflow before it touches a real lead, and watch what each rule did after it goes live. Misfires surface in the rule log, not in an angry customer call.
- Dry-run mode before you arm a rule
- Per-rule run log with input + outcome
- Switch any rule off in Settings
- Rate-limited per tenant so a loop cannot flood anyone
What your rules do — and which leads they match — stays inside your workspace, behind the same tenant isolation as your leads, and every change to a rule is audit-logged. A rule's actions are alerts, follow-ups and reassignments for your own team; no rule sends anything to a buyer.
See it for yourself.
Twenty minutes on a call, on demo data, talking through your own pipeline. Your leads, your team, your CRM.