How to route portal leads to the right agent automatically
· SyncYak team
A new lead email lands in a shared inbox at 4:50 on a Friday. Someone has to read it, work out which agent covers that zip code, and forward it. If that someone is out, the lead waits. Multiply that by every portal, every office and every weekend, and routing becomes the slowest step in your speed-to-lead process.
The fix is to stop treating routing as a human task. A lead email already contains what you need to decide who gets it: a zip code, a listing address, a source. If you keep a roster that says who owns what, a lookup can do the forwarding in seconds. This post walks through a routing setup that uses a Google Sheet as the roster and needs no code.
What routing actually needs
Every routing rule, however elaborate, reduces to two things:
- A field pulled from the email: zip code, listing ID, property address, lead source or the sender.
- A table that maps that field to an agent, with the details you need to reach them.
Round robin, territory, listing-based and source-based routing are all variations. Territory routing matches on zip code. Listing routing matches on the listing the lead asked about. Source routing sends every lead from one portal to one team. The part that stays constant is the table, and the best place for the table is somewhere your operations team already edits: a spreadsheet.
Step 1: Get the fields out of the email
Portal emails are written for people. The name, phone number and property sit inside paragraphs of HTML, and the layout changes whenever the portal redesigns its template. Before you can route, you need those values as separate fields.
SyncYak Parse does this with ready-made templates for Zillow buyers and sellers, Zillow mortgage leads, Realtor.com, IDX website registrations and other common sources. A catch-all template picks up the rest, so a redesigned email still delivers the lead. Forward your portal emails to a Parse inbox, or set the inbox address as the one the portal writes to. Each inbox has an address on parse.syncyak.com, and sub-addresses such as leads+zillow@ reach the same inbox, which helps when you want to tell sources apart.
The result is a set of named fields: name, phone, email, zip code, property and so on. Those are what the lookup matches against.
Step 2: Build the roster sheet
Create a Google Sheet with one row per routing rule. A small territory roster looks like this:
| zip | agent_name | agent_phone | agent_email |
|---|---|---|---|
| 78701 | Dana Ruiz | 512-555-0101 | [email protected] |
| 78702 | Dana Ruiz | 512-555-0101 | [email protected] |
| 78704 | Marcus Lee | 512-555-0102 | [email protected] |
The phone numbers and names above are placeholders. The structure is what matters: the column you match on goes first, and the columns you want attached to the lead go after it.
A few habits keep a roster healthy:
- Use one row per zip code, even when one agent owns many. It is easier to audit than a cell full of comma-separated values.
- Keep the match column consistent. If zip codes are text in the roster, make sure they stay text, so a leading zero in a northeastern zip code is not dropped.
- Add a catch-all owner for the leads that match nothing, whether that is a team lead or a shared queue.
Because the roster is a sheet, changing an assignment is an edit, not a deployment. When an agent goes on vacation or a territory is split, someone updates a row and the next lead follows the new rule.
Step 3: Add the lookup
A lookup tells Parse to find the roster row whose column matches a parsed field, and copy the columns you pick into the lead. In this example you match the parsed zip field to the roster's zip column and copy agent_name, agent_phone and agent_email.
Share the roster sheet with the SyncYak address shown in your Parse console, paste its link, and choose the match column and the columns to copy. Lookups are not part of the free plan; they start on the Hobby plan, which includes one. Pro includes five, and Business has unlimited lookups. Check pricing for the current plans.
Decide what happens when nothing matches. You can deliver the lead without agent details, or hold it until someone replays it. For most teams, delivering is the safer choice: a lead with no owner is better than a lead nobody has seen. Pair it with a catch-all row or an alert so an unmatched lead gets a human look quickly.
Step 4: Deliver the routed lead where the agent works
Once the lead carries its agent, send it onward. Common patterns:
- A Google Sheet per team or agent. Each parsed email adds one row. Filter the sheet by
agent_email, or write to a tab per office. - A Zapier Zap. Start a Zap with Webhooks by Zapier (Catch Hook), paste its URL into the inbox as a destination, and use the
agent_emailfield to create the contact in that agent's CRM and send them a text. Make and n8n work the same way. - Your own webhook. If you run a platform, receive the parsed lead with the agent fields attached. Check the
X-SyncYak-Signatureheader, an HMAC-SHA256 of the timestamp and the body signed with the inbox's secret, before you trust the payload.
A routed payload carries the parsed fields and the lookup columns together, so the receiving system never needs its own copy of the roster.
Testing the setup before real leads arrive
Forward three or four old lead emails to the inbox, covering a matching zip code, one that is missing from the roster, and a source you did not expect. Then check:
- The parsed fields look right, especially phone and zip code.
- The matched lead carries the right agent columns.
- The unmatched lead behaves the way you decided in step 3.
- Retries work. Failed deliveries are retried, so a Zap that is switched off for an hour does not lose leads.
Run this check again whenever you add a new portal or change the roster layout.
How SyncYak helps
Parse turns the lead email into fields, the lookup attaches the owner from your own sheet, and the destination delivers it, all within seconds of the email arriving. The free plan covers 100 emails a month and two inboxes, which is enough to run the whole flow with real leads before you commit. For a brokerage that wants one inbox per office on its own domain, custom domains start on Hobby. The lead routing for brokerages page shows the same setup for an office, and the Parse product page lists the destinations and templates in full.
If your leads also need to land in a CRM, the Zillow leads to Google Sheets guide covers the sheet side in detail.
Ready to try it? Create a free account, forward one real portal email to a Parse inbox, and see which fields come out before you build the roster.