Last updated September 21, 2026
Lead Routing distributes eligible agency inquiries among your advisors. The complete setup connects three things: the specialties on the lead, the specialties your advisors cover, and an ordered list of routing rules.
Agency visibility means the form is shared; it does not determine who receives its leads. Check the routing badge on the Forms list and Form settings → Leads in the builder.
For example, map the answer Alaska Cruise to Alaska, then ensure an eligible advisor covers Alaska. Do not map a generic Cruise answer to one cruise brand unless the question actually identifies that brand.
Go to Settings → Advisors, open an advisor, and switch to the Payments tab:
Go to Leads → Partner performance to open Lead program (owners and admins only) and click Add rule. Each rule has:
Put specific rules first. If you want a fallback, add a separate rule below them, select Round-robin all, leave interest, budget, and source unrestricted, and choose Round-robin or Least-loaded under Balance by. Use the up/down arrow buttons to change rule order.
When a booking-partner program exists, automatic specialty, team, and broad pools are restricted to its members. A rule naming a specific advisor is a deliberate exception. Without a configured program, those pools use eligible agency members. A fallback still needs an available advisor under capacity. It cannot promise that every inquiry will be assigned.
The builder offers supported automatic modes. Older rules marked Manager assigns actually use round-robin; older Triage rules are skipped. Edit those legacy rules to choose a supported setting. Manual triage happens from the Leads queue.
The Coverage panel on the right shows every specialty tag and how many partners cover it — thin or uncovered tags are flagged so you can see gaps before leads fall through to the fallback.
Routing is only as smart as the tags on the lead. In the form builder, select a choice field, open its Leads tab, and expand Route leads by specialty. Click + Tags next to an answer and pick the specialties it signals — for example, on a "What kind of trip?" field:
When the form is submitted, the lead is tagged automatically and the rules take it from there. You can also tag any lead manually from its detail view — useful for phone inquiries you enter by hand.
Only map answers that actually say something about what the client wants to book. A seat preference or an allergy question tells routing nothing, so leave those blank. If you want to segment on them anyway, use Let clients tag themselves in the same panel instead — that writes an ordinary tag you can filter a campaign by, and it doesn't touch routing. See Form Builder for the difference between the two.
This section is hidden on a solo account, since specialty routing exists to choose between advisors and there is only one.
On the Routing rules page, set the Accept SLA to a number of minutes. For eligible leads assigned by the routing engine, if the advisor does not accept within that window, JourneyFuse automatically re-routes the lead to the next available advisor (the non-responder is skipped) and notifies the new assignee. Leave it blank to disable the deadline. Personal, existing-client, client-selected, and deliberate manual assignments are protected from automatic reassignment.
Sometimes there is nobody to move the lead to: no advisor lists its specialty, everyone is paused or full, or the rule can't resolve a pool. JourneyFuse stops re-trying that lead and sends "A lead needs manual assignment" so a person can place it by hand. The lead stays put until someone does, and you won't be emailed about it again unless the assignment changes.
By default that email goes to every owner and admin, which on a larger agency means several copies of the same alert. Under Settings → Notifications → Who handles lead routing, name one person and only they get the email. Point it at whoever works your queue, or at a shared agency mailbox that has been added as an admin on the account. Everyone still sees the alert in their in-app notifications either way.
On Leads, switch to Agency and the Table view tab to get the routing command center:
Booking-partner leads are hidden from the main pipeline by default so your agency's own pipeline stays clean — use the Show booking-partner leads toggle or the Booking partners tab to see them.
An assigned advisor gets one email and one in-app notification for each new lead. The email names the lead, shows what they asked for (email, phone, request and budget when given), carries any files uploaded on the form, and has Accept and Decline buttons. Replying to it writes to the lead directly. The lead also appears in their leads list with an Accept / Decline banner. Accepting records their acceptance. Declining an agency-routed or manually handed-off inquiry returns it to shared triage, unless the advisor is declining their own original inquiry; that ownership stays with them. Accept rates and response times feed the partner performance scorecard.
A lead from an agency form is read for specialties before it is placed, so it goes straight to the partner whose specialties match what the client asked for. That reading takes a few seconds, and during it the lead shows in the queue as matching a partner with nobody on it. Nobody is emailed until it is placed, and then only the partner who gets it. If the reading adds nothing or takes too long, the lead is placed by your routing rules alone.
This is part of JourneyFuse’s host agency software: advisor workspaces, commission splits and agency-wide visibility.
Pay your top advisors a slice of their mentees' commissions automatically — split, lock, and pay it out without spreadsheets.
Owner, Admin, Agent, and Support Staff — pick the right role so your team has the access they need without seeing what they shouldn't.
Bring your TESS export into JourneyFuse. Drag-drop the .xlsx, preview what comes over per sheet, then confirm — nothing imports until you say so.