Publish a booking page with intake questions

Publish a booking page with intake questions

Checks your existing booking pages, creates a Bridge booking page with your hours and intake questions, turns it on and returns its link.

Set up the tools below, then run the steps in order for the user, carrying each step's results into the next. The run is done when the user has the outcome below.

Outcome

• A live Bridge booking page with the duration, hours, notice and intake questions you asked for.
• Its public link, with a short line to put on your website, email signature or outreach.
• A note on why the page is not live yet, when a host still needs to connect a calendar.

Inputs

Ask the user for these before you start.

• page_name: what people see when they book, e.g. Intro call with Acme
• duration_minutes: the meeting length, e.g. 30
• hours: when people can book, with a time zone, e.g. Mon to Fri 10:00 to 16:00 America/New_York
• notice: the minimum notice and how far ahead people can book, e.g. 4 hours notice, up to 30 days ahead
• intro: the line people read before booking, e.g. A 30-minute call to see if Acme fits your team
• questions: what to ask each booker, with which are required, e.g. Company website (required); What do you want to cover?

Set up

Bridge (tool:bridge/list-booking-pages, tool:bridge/create-booking-page, tool:bridge/get-booking-page, tool:bridge/update-booking-page, tool:bridge/set-booking-page-status)

Use the MCP server. Add it to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "bridge": { "url": "https://api.meetonbridge.com/mcp" } } }

• List booking pages: call the MCP tool list_booking_pages
• Create a booking page: call the MCP tool create_booking_page
• Get a booking page: call the MCP tool get_booking_page
• Update a booking page: call the MCP tool update_booking_page
• Turn a booking page on or off: call the MCP tool set_booking_page_status

Note: Needs a paid Bridge plan (Professional or above); not on the free Starter plan or a trial. At sign-in the user grants read, or read and write, access. Call get_bridge_context first for the tools the plan and connection allow.

Notes:

• Create a booking page: Starts inactive unless status is active, which fails until every host has a calendar connected. Use addQuestions to keep the default Notes question; questions replaces the whole form.
• Get a booking page: Required form questions must be answered in book_meeting's answers.
• Update a booking page: Only the fields passed change, as soon as it is called; existing bookings are not moved. Status is set with set_booking_page_status.
• Turn a booking page on or off: Turning a page on publishes its link as soon as it is called, so ask the user first. It fails until every host has Google or Outlook Calendar connected.

Before step 1, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Steps

1. Check for a page with List booking pages (Bridge). Look for a page with the same name or purpose as page_name. If one exists, ask the user whether to update it instead, and keep its id.
2. Create the page with Create a booking page (Bridge). Create page_name, turned off, with duration_minutes, hours, notice, intro as its description, questions as addQuestions and email reminders a day and an hour before. Keep its id and public link.
3. Check the details with Get a booking page (Bridge). Read the page back and compare its hours, time zone, notice, reminders and questions with what the user asked for, and check that every host's calendar is connected. Keep any difference.
4. Fix any difference with Update a booking page (Bridge). Correct each difference from step 3.
5. Turn it on with Turn a booking page on or off (Bridge). Once the user agrees to publish, set the page to active. Keep its status and public link.
6. Write the share line yourself. Draft one sentence with the public link for a website, an email signature and an outreach email, and give the user all three.

Notes

A page can take bookings only when every host has Google or Outlook Calendar connected; until then, step 5 fails and says why. Each meeting booked through it gets a Bridge video link and lands on the host's calendar.

Name and email are always asked. addQuestions keeps the page's optional Notes field after your questions; passing questions instead replaces the whole form.

Rules

• Use only the services set up above. The read-only calls they need, like listing ids or polling for results, are fine.
• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.