A routing form asks two or three questions before showing times, and the answers pick the host or destination. It is a documented requirement on the routing page. The routing forms guide explains how to design the rules.
Before you start
- The few answers that change where someone goes.
- Existing ownership rules, applied first.
- A useful fallback for no match.
How to complete this task
- List the few answers that genuinely change the destination.
- Create explicit routes for owner, region, need, or qualification.
- Define a useful fallback when no rule matches.
- Submit a test for every branch and inspect its destination.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
Everyone lands on the same host.
Your rules overlap and the first matching branch wins. Order rules from most to least specific and re-test each one.
A visitor matched no rule and saw nothing.
Every routing form needs a fallback destination. A dead end costs you the enquiry entirely.
Routing ignores existing account ownership.
Ownership must be checked before distribution, otherwise an existing customer is routed to a new seller. Test with a known existing account.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
