GuidesGuide · forms and scheduling

Build a qualification flow before booking.

Ask what changes the next step, publish the reviewed form and verify that a suitable visitor reaches a valid booking path.

Prepare customer intake See the qualification solution

Expected result

A test response reaches the right next step with its context intact.

The questions are clear, validation works and the authorized agent can retrieve the structured response associated with the published revision.

Where it changes the work

Step 01

Define what changes the decision

Ask only for the need, timing and constraints that affect eligibility, routing or preparation.

Step 02

Review and publish a form revision

Check the public language, required answers and validation. Each response remains associated with this version.

Step 03

Connect a valid booking outcome

Use the intended event type, duration, location, availability and approval policy.

Step 04

Submit and retrieve a synthetic response

Test suitable and alternate paths, then verify that the authorized agent can read only the selected form.

Context before calendar time

Ask only what changes the decision.

Good intake makes the next step faster for the visitor and gives your agent structured information it can actually use.

01 · Services

Direct each request to the right service

Use answers to offer a relevant result instead of sending every visitor to the same calendar.

02 · Projects

Collect scope, timing and constraints before the call

Let an authorized agent prepare with the exact form version the visitor answered.

03 · Booking

Offer a meeting when the request is ready

Carry the reason and answers into scheduling without exposing the events that block other times.

A form with an operational next step

Collecting answers is only half of intake.

A standalone form stores submissions. instanceof.ai can route the result, expose it to an authorized agent and connect it to scheduling.

Standalone forminstanceof.ai

OutcomeStandalone formEvery submission lands in the same listinstanceof.aiRules offer the relevant next destination

ContextStandalone formA person summarizes the response againinstanceof.aiThe selected answer remains structured and versioned

BookingStandalone formA separate link loses the original reasoninstanceof.aiIntent and answers continue into the reservation

Questions before you connect

What you should know before you connect.

Are real credentials shown in this guide?

No. Use the protected configuration in your workspace and client. Never place a secret in page content or prompt history.

Can I adapt this to another MCP client?

Yes. Capabilities and permissions stay the same, but connection and runtime isolation steps may vary by client.

How should I test the flow?

Use clearly identified synthetic data, verify the result and remove the test when it could be confused with customer work.

Continue with the right detail

01Understand the request before the meeting starts.

Collect the context that matters, route the visitor to the right next step and let your agent prepare with structured answers.

02Let people choose a time inside your rules.

Share a booking page that respects working hours, time zones, notice, buffers and time away. Your agent can maintain the setup and follow reservations.

03Ask. Collect. Take the next step.

Intake, event registration, feedback and NPS. Your agent builds the questions and reads structured responses.

Build a qualification flow before booking.

Prepare customer intake