Set up email forwarding and troubleshoot parsed leads
Point your lead notification emails at the SAMI OS parser address and fix forwarded emails that never become contacts.
When a portal like Zillow or Realtor.com emails you a new lead, SAMI OS can read that email and create the contact for you. You do this by forwarding each lead notification to the parser address SAMI OS generates for that source.
Forward lead emails to your parser address
Every parser source you create gets its own unique destination address. Forwarding to that address is what lets SAMI OS match the email to the right source and parse it into a contact.
Open the email forwarding setup page
Head to Settings → Integrations → Email forwarding. This page shows the generated parser address you forward to.
Copy the generated parser address
Copy the exact destination address shown for the source. Each source has its own address, so copy the one that matches the portal you are setting up.
Add a forwarding rule in your inbox
In Gmail, Outlook, or your portal's notification settings, create a rule that forwards incoming lead emails from that portal to the parser address. Confirm any verification email the provider sends.
Send a test lead
A source's scope decides who owns the lead. A Personal source assigns every parsed contact to the agent who created it; an Organization source shares the leads across the team. Pick the scope that matches how you route that portal's leads.
When a forwarded email does not create a contact
SAMI OS matches each inbound email by its recipient address and only against sources that are Active. If nothing was created, work through these checks in order.
- Confirm the source is Active. A Disabled source is skipped entirely, even if email reaches its address. Re-enable it from Email forwarding by switching its status back to Active.
- Check you forwarded to the correct generated address. A typo or an old address means no source matches, so the email is ignored. Paste the address straight from the setup page rather than typing it.
- Verify the scope. If leads land but on the wrong person, the source scope is probably Personal when it should be Organization (or the reverse). Update the scope and re-test.
- Make sure forwarding actually fires. Some providers require you to confirm a verification email before forwarding starts. Until that is confirmed, no email reaches the parser.
SAMI OS reads the address the email was sent or forwarded to, not the original sender. If your forwarding rule strips or rewrites the recipient, the email may not match any source. Forward to the parser address directly instead of bouncing it through another mailbox.
Use a separate source for each email format
Each parser source learns the layout of one notification format. If you receive leads from several portals, create a separate source for each one so SAMI OS can map every field correctly. Mixing two formats into one address leads to missing names, phones, or property details.
When you add or manage these sources, you can route the resulting contacts further with Workflows or hand them to a SAMI Bot for instant first contact.
Related articles
Last updated 2026-06-21