How to Design Smart Routing Forms for Bookings

How to Design Smart Routing Forms: Questions and Rules for Your Bookings

Your business offers several services and wants each visitor to find the right meeting. The first instinct is often to add questions: name, company, phone number, service, budget, team size…

However, collecting more information does not guarantee a better booking. A form becomes useful when each question has a purpose: understanding someone's needs, choosing the appropriate destination or preparing the conversation.

Designing smart routing forms means connecting three things: clear questions, relevant answers and understandable routing rules.

A Useful Form Starts with the Decisions You Need to Make

This guide explains how to do that with examples you can adapt to your business.

1. Define Destinations Before Writing Questions

Before opening your form editor, list the options you can actually offer.

A destination might be an initial consultation, a product demo, a specialist session or a team sharing responsibility for a service.

For each destination, establish:

Which need it addresses.
Which meeting type is appropriate.
Who can handle the appointment.
Which information distinguishes it from other destinations.

For example, a business may offer product demos and training for existing customers. If these services need different teams and meeting durations, separating them in the form makes sense.

If an answer neither changes the destination nor helps prepare the meeting, it may not need to influence routing.

2. Separate Contact Details, Routing Questions and Context

Not all fields serve the same purpose.

Information type	Example	Purpose
Contact details	Name and email address	Identify the person and communicate appointment details
Routing	Which service do you need?	Choose the appropriate booking option
Context	What would you like to resolve during the meeting?	Help the professional prepare

This distinction prevents every piece of information from becoming a filter.

A short project description can help prepare a demo without determining who handles it. Similarly, asking about company size makes sense only if the information affects the service or is used during the conversation.

Start with essential fields and add others when you can explain their purpose.

3. Turn Answers into Specific Rules

Conditional logic determines what should happen when a condition is met.

Before configuring it, write each rule in a simple format:

If someone answers X, they should continue to Y.

For example:

Question	Answer	Intended destination
What do you need?	Explore the product	Sales demo
What do you need?	Learn how to use it	Customer training
Which service would you like to discuss?	Tax advice	Tax advisory team
Which region should handle your enquiry?	Northern region	Team responsible for that region

These are design examples. Implementation depends on the destinations and options configured in your tool.

Use distinctions that visitors understand. Translate internal department names into customer-facing options rather than expecting people to know your organisation.

4. Three Smart Form Examples

Example A: A Product Demo Request

A company sells two products and has specialists for each.

The form first asks which product interests the visitor. That answer determines the demo offered.

It can then ask for a short description of what the visitor wants to achieve. This provides context without necessarily changing the booking journey.

The structure is:

Product interest → relevant demo → available time.

If several people handle that demo, appointment distribution takes place within the appropriate team.

Example B: An Initial Professional Consultation

A consulting firm offers tax, employment and accounting advice.

The first question identifies the advisory area. If existing customers and first-time visitors need different appointment types, a second question can distinguish them.

Avoid requesting extensive documents before they are necessary. The service area and a short description may be enough to route the booking.

The structure is:

Advisory area → initial or follow-up consultation → appropriate appointment.

Example C: International Customer Enquiries

A business serves different markets and assigns enquiries according to regional responsibilities.

It can ask about the service region and, where necessary, the preferred meeting language.

Language and territory are not interchangeable. Someone requesting a meeting in German may be based outside Germany.

The structure should reflect the business:

Service territory → responsible team → available language options.

If everyone in the team works in the same languages, language may not need to be a routing condition.

5. Decide When to Combine Routing and Round Robin

First identify the team qualified to handle the enquiry. Then, where appropriate, distribute appointments among its members.

A tax enquiry, for example, should reach professionals handling that service. Round-robin distribution can operate within that group, according to configured rules and availability.

Avoid distributing enquiries across all users when only some can resolve them.

TuCalendi's smart forms page presents responsibility-based assignment, round-robin distribution and backup routing. When designing your journey, establish who can handle each request and what alternative should be offered when availability is limited.

6. Plan for Answers That Do Not Fit

A form should accommodate visitors who do not know which option to select.

“I'm not sure” can be a useful answer if it leads to a general consultation or another support route your business has prepared.

Also review what happens when:

An answer could match two destinations.
Someone requests a service you do not offer.
No appointment times are available.
The intended professional cannot handle the request.

Avoid ambiguous rules. If two conditions can apply simultaneously, check how the tool resolves that situation before publishing.

7. Adapt Questions for Each Language

A multilingual form needs more than translated labels.

Options should retain their meaning and lead to the intended destination in each version. Pay particular attention to service names, territories and terms such as “consultation”, “demo” and “follow-up”.

Use natural wording and ensure instructions make sense to someone unfamiliar with your business.

Distinguish the language used to complete the form from the languages available for the meeting.

8. Test the Complete Journey

Do not stop at checking that the form submits.

Test each relevant combination and confirm that:

Answers lead to the correct destination.
Expected booking options appear.
The process works on mobile.
Instructions and confirmations are consistent.
Necessary information reaches the professional.
Visitors have a clear next step if they are unsure or no appointments are available.

Ask someone uninvolved in the setup to try it. If a question needs explaining, review its wording or answer options.

Putting Your Design into Practice with TuCalendi

TuCalendi's smart forms combine custom fields, conditional logic and multilingual options to guide bookings.

Before configuring them, prepare a table with three columns: question, answer and destination. Add team distribution rules where needed.

Start with one service. Once its journey works, introduce further options while keeping the form easy to understand.

Create a Clear Path to Each Meeting

A smart form does not need to be long or complicated. It needs enough information to help each person find the right service.

Define destinations first, write understandable questions and test what happens after each answer.

Want to organise your company's questions and routing rules? Request a TuCalendi demo and discuss your booking journeys with our team.