Routing Forms let you collect information from visitors before they book a meeting, then automatically direct them to the right scheduling page of the fitting team member based on their answers. Used well, they improve the quality of incoming bookings and save your team time by ensuring meetings always land with the right person.
Routing Forms are available on the Business plan and above.
How Routing Forms fit into your workflow
Routing Forms sit between your website or landing page and your scheduling pages. Instead of sending every visitor to the same booking link, a Routing Form acts as a smart gateway: it asks a few qualifying questions first, then directs each person to the most relevant scheduling page automatically.
This is especially useful if you have multiple teams, service lines, or regions—and different people should be handling different types of meetings.
Typical flow:
Visitor lands on your page → Fills out Routing Form → Gets directed to the right scheduling page → Books with the right person
Without a Routing Form, visitors either have to figure out themselves who to book with, or meetings end up going to the wrong team. A well-configured Routing Form removes that friction for both sides.
Before you start
Before building your Routing Form, take a few minutes to prepare. A small amount of upfront planning will save you from having to reconfigure things later.
Have your scheduling pages ready. Routing Forms direct visitors to pages that already exist in Zeeg. Make sure the relevant scheduling pages are created and configured before you set up your routing logic.
Know which questions you need to ask. Identify the minimum information required to route a visitor correctly. Think about what you genuinely need to know—not what would be nice to know.
Identify your team members and who handles which route. If you're routing to individual scheduling pages, confirm who is responsible for which type of meeting before building your logic (e.g. enterprise leads go to your senior AE, SMB leads go to your SDR).
Plan your fallback. Decide where visitors should land if their answers don't match any specific route. This could be a general scheduling page, a contact form, or a custom URL with a helpful message.
Keep your questions to a minimum
Every additional question is one more reason for a visitor to drop off before booking. The goal is to qualify and route—not to conduct a full survey.
Before adding a question, ask yourself:
Do I need this to decide who to route this person to?
Do I need this to follow up if they don't book?
If the answer to both is no, leave it out. Extra questions can always be collected on the scheduling page itself using invitee questions—those won't affect routing logic.
Keep your questions clear
Use short, direct field labels rather than full sentences. Visitors scan forms quickly, and simple labels reduce confusion and keep the form visually clean on mobile.
Instead of this | Use this |
What is your email address? | |
Which country are you located in? | Country |
How large is your company? | Company size |
What are you interested in? | Area of interest |
Set up routing logic carefully
Good routing logic is the backbone of an effective Routing Form. Here are the most common patterns and how to set them up in Zeeg.
Route by company size
Useful for separating SMB and enterprise leads to the right sales rep.
When "Company size" is "Enterprise" → Route to Enterprise Sales
When "Company size" is "Small business" → Route to SMB Sales
Route by service type
Useful when you offer multiple services handled by different teams.
When "What do you need help with?" is "Technical support" → Route to Support Team
When "What do you need help with?" is "Sales demo" → Route to Sales Team
Route by geography
Useful for global teams with region-specific reps.
When "Location" is "Europe" → Route to EU Team
When "Location" is "North America" → Route to US Team
Full example: a sales qualification Routing Form
Here's how a complete Routing Form might look for a SaaS company that wants to route inbound leads to the right sales rep based on company size and area of interest.
What the visitor sees (front end)
A short form with two questions:
Company size (required, dropdown)
1–10 employees
11–50 employees
51–200 employees
200+ employees
What are you interested in? (required, dropdown)
Sales demo
Technical support
Partnership
How the routing logic works (back end)
Condition | Route to |
Company size is "200+ employees" AND Interest is "Sales demo" | Enterprise AE – 30-min demo page |
Company size is "51–200 employees" AND Interest is "Sales demo" | Mid-Market SDR – 30-min intro call |
Company size is "1–10" or "11–50" AND Interest is "Sales demo" | SMB Sales – 20-min discovery call |
Interest is "Technical support" | Support Team scheduling page |
Interest is "Partnership" | Partnerships team scheduling page |
No match (fallback) | General contact page with message: "We'd still love to connect—reach us at hello@yourcompany.com" |
This structure means no lead ever lands on a generic booking page—every visitor is directed to the right person based on two simple questions.
Always configure a fallback route
Not every visitor will match one of your defined routes—for example, if they select an option you didn't anticipate, or if a required field is left blank. Without a fallback, those visitors hit a dead end.
In Zeeg, you can configure a Fallback destination for unmatched cases. Set it to one of the following:
A general scheduling page (e.g. a catch-all booking page)
A custom page with a message explaining next steps
A custom URL, such as a contact form or your support page
Customize the fallback message so it's helpful rather than generic. A message like "We'd still love to connect—reach us at hello@yourcompany.com" keeps the visitor engaged instead of leaving them at a dead end.
Collect additional details on the scheduling page
Routing Forms are for qualification and routing—not for collecting every detail upfront. Once a visitor is directed to the right scheduling page, use invitee questions on that page to gather the remaining information you need before the meeting.
This keeps the Routing Form short and friction-free, while still ensuring you have all the context you need.
Test your routing logic before going live
Before sharing your Routing Form with invitees, go through it yourself and test every possible route:
Fill in answers that should trigger each route and confirm you land on the correct scheduling page.
Test edge cases (e.g. selecting options that should hit the fallback).
Check that the fallback destination works as expected.
Confirm email notifications are sent to the right people.
Even a small misconfiguration in routing logic can send leads to the wrong team—so a quick end-to-end test is always worth it.
Common mistakes to avoid
Too many questions. Forms with more than 3–4 questions see significantly higher drop-off. If you're tempted to add more, ask whether that information could be collected on the scheduling page instead.
Vague dropdown options. Labels like "Other" or "General inquiry" create ambiguity and are hard to route meaningfully. Be specific with your options so visitors always find something that fits.
No fallback configured. Leaving the fallback empty means unmatched visitors see a dead end. Always set a fallback, even if it's just a link to your contact page.
Routing to pages that aren't published or available. If a scheduling page is hidden or misconfigured, visitors routed there won't be able to book. Double-check that all destination pages are live before sharing your form.
Skipping the test. It's easy to assume the logic works as intended—but small configuration errors (like a typo in a dropdown option) can silently break a route. Always test before going live.
Monitor your form submissions
Once your Routing Form is live, check the Submissions section regularly to review how it's performing. You can also export that data. Use it to:
Identify which routes receive the most traffic
Spot drop-off patterns (e.g. questions with low completion rates)
Catch unexpected answers that aren't matching any route
Refine your questions and routing logic over time
FAQ
Can I use more than one Routing Form?
Yes. You can create multiple Routing Forms for different use cases—for example, one for sales inquiries and another for support requests.
Can I route to an external URL?
Yes. When setting up a route destination, you can select Custom URL and enter any external link, such as a contact form or landing page on your website.
What happens if a visitor doesn't match any route?
They will be directed to the Fallback destination you have configured. If no fallback is set, they may see a default message—so it's always recommended to configure a meaningful fallback.
Do invitees see the routing logic?
No. Visitors only see the form questions. The routing logic runs in the background and they are simply directed to the appropriate scheduling page (or fallback) based on their answers.
Can I require specific questions to be answered before the form submits? Yes. When adding questions to your form, you can mark any field as required. Visitors will not be able to proceed without completing those fields.
Will changing routing logic affect past submissions?
No. Changes to routing logic only affect new submissions going forward. Past submissions remain unchanged in the Submissions section.
Can I embed a Routing Form on my website?
Yes. Routing Forms can be embedded on your website the same way as regular scheduling pages. From the form's Share options, copy the embed code and paste it into your site.
Can I connect a Routing Form to a round-robin or team scheduling page?
Yes. When setting up a route destination, you can select any scheduling page in your Zeeg account—including round-robin and team scheduling pages. This is useful when you want to qualify leads first and then distribute them across a team automatically.
Can I use Routing Forms with Zapier?
Yes. If you have a Business subscription or above, you can connect Zeeg to Zapier and trigger workflows based on Routing Form submissions—for example, adding a contact to your CRM or notifying a Slack channel when a form is filled out.