Run your standard playbook on every deal
Visual rule builder. Triggers, conditions, AI actions, SLA enforcement. The work you used to need a 'process person' for.
Turn your repeatable judgment into a rule
Trigger library
Lead created, app submitted, condition expired, commitment issued, payment NSF — 200+ events.
Conditions
Filter by stage, amount, lender, agent, geo, source, anything. AND / OR / NOT logic.
AI actions
Have Harvey do the work. 'Send re-engagement email written by Harvey'.
Email / SMS / call
Send templated outreach, schedule a call back, drop a voicemail — automatically.
Schedules
Daily 8am pipeline review, weekly conditions sweep, monthly NSF reconciliation.
SLA enforcement
Lead untouched > 5min? Page. > 30min? Reassign. Deal stuck > 7 days? Escalate.
Audit log
Every rule run is logged. Skip reasons, action results, error chains, retry attempts.
Per-tenant
Enterprise: HQ defines default rules. Tenants override + extend. No forks.
Twilio + Email
First-class integration with Twilio, SendGrid, Postmark. Logs back to deal automatically.
See what fired, when, and why
- 12:14:08Stale lead nurtureDrafted 3 emails — Harvey
- 12:08:42Commitment expiry watchReminded borrower to sign
- 12:00:00Conditions sweepFound 12 expiring < 7d
- 11:54:11NSF retry — autoRetried EFT $3,712
- 11:42:00Renewal alert (90d)Paged 2 brokers
Automations — common questions
- What can Mortgage360 automate?
- Follow-up sequences, renewal campaigns, document chasing, lead routing, task assignment and SLA escalation — triggered by what actually happens on a deal rather than by a date somebody remembered to set.
- Do I need technical skills to build an automation?
- No. Automations are built from triggers, conditions and actions in a visual editor, and the platform ships with a library of working ones you can use as-is or fork and change for your brokerage.
- What triggers an automation?
- Events on the record — a deal changing stage, a document arriving, a renewal window opening, a lead going untouched past your SLA, a call outcome being logged. Because dialling and email are built in, the triggers see real activity rather than what somebody typed in.
- Can a brokerage enforce automations across agents?
- Yes. A brokerage can publish automations that every agent inherits, and an agent editing one creates their own copy rather than changing it for everybody. That is how a compliance-relevant sequence stays intact.
- Will automated messages break CASL compliance?
- Consent state is held on the contact, and sends check it before they go. Unsubscribe handling and the required identification are built into the templates rather than left to whoever writes the message.
- Can I see what an automation actually did?
- Yes. Every run is logged against the contact and the deal — what fired, what it evaluated, what it sent. An automation you cannot audit is one you eventually stop trusting and switch off.