Inbound Router
Create a router to qualify and route meetings that come in via a form submission.
Campaign Router
Configure how leads should be routed when a meeting is booked through one of your marketing campaigns.
Relays
Book meetings on behalf of another rep and handoff meetings from one team to another.
Comparison of Inbound, Campaign, and Relay Routers
Use this table to understand when to use each router based on your use case, how they handle forms, routing, and qualification.| Router | When to Use and How it Works | Form Approach | Routing & Qualification |
|---|---|---|---|
| Inbound | Used when you’re capturing leads from website forms and need to qualify and route them instantly. It connects to any form, enriches data if required, qualifies based on your rules (like job title or company size), and routes to the right rep | Form-first - Prospect fills the form first. RevenueHero latches onto the form, enriches if required and routes after submission. | Performs qualification and enrichment based on form input and enrichment source if added. Routes using ownership and distribution rules. |
| Campaign | Used when you’re running outbound campaigns or email sequences and want to offer a 1-click booking experience. If data is pre-filled in the URL, it skips the form and routes based on ownership or round robin. If not, it does a simple round robin and shows a form after slot selection to collect information. | Calendar-first - prospect picks a slot first. Form is shown after slot selection, or skipped entirely if data is already prefilled in the URL. | No qualification or enrichment. Routes are based on pre-filled URL data, either to the owner or using round robin. |
| Relay | Used to book meetings on behalf of someone else (like SDR → AE handoff). Ideal for internal handoffs or CS flows. Captures info via a RevenueHero form and routes based on that input or CRM data. | Form-first - shows a form to capture prospect details before slot selection. | Does not qualify or enrich. Routes based on form or CRM data. Routes using ownership rules and distribution pods, and has a fallback pod. |