Lead routing overview (email vs. integrations)

How lead routing works in Roof AI Core

With Roof AI Core, leads (such as listing inquiries and showing requests) are routed via email notifications to the recipient(s) you chose during setup.

Best-practice recipient setup

Send notifications to a monitored team inbox (shared mailbox or alias), not one person’s inbox. Follow-up speed is a big driver of outcomes.

If you want CRM delivery later

Core is designed to get you live fast via email routing. If you eventually want leads delivered directly into your CRM / lead router, this requires upgrading to either Roof AI Intelligence or Lifecycle.

The two routing modes

Roof AI can route leads in two ways:

1. Email notifications to recipients you choose
2. CRM / lead router routing depending on your tech stack configuration

Tier notes

• Intelligence: Email notifications, plus routing through lead email parsing (useful when your downstream system depends on structured emails)
• Lifecycle: Everything in Intelligence, plus custom lead routing (CRM, lead router, or custom endpoint) and advanced workflows as configured

What your team receives (depending on setup)

• Lead notification emails (all Intel/Lifecycle customers)
• Routed lead details in your CRM / lead router if routing is configured (Lifecycle; Intelligence may rely on parsing-based routing)

Best-practice recipient setup

Use a monitored inbox (team alias / shared mailbox), not a single person. It keeps routing reliable and prevents missed follow-up

The two routing modes

Roof AI can route leads in two ways:

1. Email notifications to recipients you choose
2. CRM / lead router routing depending on your tech stack configuration

Tier notes

• Intelligence: Email notifications, plus routing through lead email parsing (useful when your downstream system depends on structured emails)
• Lifecycle: Everything in Intelligence, plus custom lead routing (CRM, lead router, or custom endpoint) and advanced workflows as configured

What your team receives (depending on setup)

• Lead notification emails (all Intel/Lifecycle customers)
• Routed lead details in your CRM / lead router if routing is configured (Lifecycle; Intelligence may rely on parsing-based routing)

Best-practice recipient setup

Use a monitored inbox (team alias / shared mailbox), not a single person. It keeps routing reliable and prevents missed follow-up

What an integration does

Instead of relying only on email, an integration can deliver the lead payload directly into your CRM or lead router so your existing workflows (ownership, follow-up tasks, automation) can fire.

When you should use one

• You already have strong CRM workflows
• You need advanced routing rules (office, zip, agent / team, etc.)
• You want consistent, structured fields mapped into the right places

What you’ll typically need

• Your CRM / lead router destination details
• Field mapping expectations (what goes where)
• A verification pass after routing is connected (use your testing checklist)

If you’re email-only today

You can start with email notifications and move to CRM / lead router routing later – just treat the routing destination as a deliberate setup decision and keep one “source of truth” for follow-up.