Meeting routing forms overview

Short answer: Match form answers with the correct host, event, or destination. Begin with “List the few answers that genuinely change the destination.” and verify the result through the public participant path.

Before you change the setup

Identify the exact organizer, event type, public link, and time zone involved before editing anything. Save the current behavior or take a screenshot so the test has a reliable before-and-after comparison.

How to complete this task

List the few answers that genuinely change the destination.Start with the intended outcome and the record that controls it.
Create explicit routes for owner, region, need, or qualification.Review every related setting before saving so one rule does not mask another.
Define a useful fallback when no rule matches.Keep private data and guest-facing information clearly separated.
Submit a test for every branch and inspect its destination.Complete the same path an external participant will use.

Verify the participant result

Run one successful case and one edge case. Confirm the public title, local time, available choices, duration, location, confirmation, calendar file, and private management path as applicable. Then check the organizer view and any email delivery record. A saved setting is not proof that the scheduling lifecycle worked.

Troubleshoot meeting routing forms

These are the failures reported most often for this specific task, with the cause that explains 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.

Meeting routing forms overview acceptance checklist

Use the following evidence map while completing this specific task. It ties each action to an observable result so another person can repeat the setup or diagnose it without guessing.

1. List the few answers that genuinely change the destination.

Write down the intended result, the organizer or account that owns it, and the exact event type or public link in scope. This prevents a correct change from being applied to the wrong record.

2. Create explicit routes for owner, region, need, or qualification.

Inspect the related rules and dependencies before saving. Record the previous value and the new value, including the time zone, provider account, or team owner when one controls the outcome.

3. Define a useful fallback when no rule matches.

Review what an invitee can see and what remains private. Keep only the context needed to complete the meeting task, and make the fallback understandable when information is missing.

4. Submit a test for every branch and inspect its destination.

Complete this step from a signed-out participant session. Preserve the resulting URL or event code, displayed state, message, calendar output, and any provider response needed to prove the task worked.

Evidence type	What to record
Controlling input	The account, event type, setting, public link, and time zone used in the test.
Participant result	The exact choices, context, confirmation, or error visible while signed out.
Lifecycle result	What changes after confirmation, finalization, cancellation, reschedule, or retry.
Failure boundary	The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.
Owner	The person responsible for correcting the setting, provider connection, content, or customer communication.

Evidence type

What to record

Controlling input

The account, event type, setting, public link, and time zone used in the test.

Participant result

The exact choices, context, confirmation, or error visible while signed out.

Lifecycle result

What changes after confirmation, finalization, cancellation, reschedule, or retry.

Failure boundary

The missing permission, unavailable dependency, invalid input, or conflicting rule that prevents success.

Owner

The person responsible for correcting the setting, provider connection, content, or customer communication.

RELATED CAPABILITY

Meeting routing

Use concise forms to match each guest with the correct page, teammate, region, specialty, or account owner. This page explains meeting routing requirements. Confirm production availability before depending on this capability.

Review scope

Meeting routing forms overview: frequently asked questions

Short answers to the questions organizers ask most about meeting routing forms.

What is a routing form?

A short set of questions asked before any times are shown, whose answers decide which host, meeting type, or alternative destination the visitor reaches.

How many questions should it ask?

Two or three. Ask only what changes the destination — every extra question loses visitors without improving the routing decision.

What should happen when nothing matches?

Send them somewhere useful: a general booking page, a contact form, or documentation. A dead end costs you the enquiry entirely.

Does routing respect existing account ownership?

It must. Check ownership before applying distribution rules, otherwise an existing customer is routed to a new seller. Test that case explicitly.