Where to put your booking flow

There is one booking flow and one set of rates behind all of these. What changes is how the customer reaches it.

• Your website — one embed snippet drops the flow into a page you control.
• WordPress and Wix — the same embed, pasted into a shortcode, block or embed element.
• GoHighLevel — the flow inside a funnel, triggered from a workflow.
• Facebook and Google Ads — a campaign link that carries its source through to the reservation.
• Email — the intake link in any campaign or transactional send you already run.
• QR code — printed on a truck, a yard sign or a leave-behind card.

1. 1Inbound calls you cannot takeThe hosted link needs no site changes at all. Send it and let the caller build the inventory while you are on the next job.
2. 2Traffic already on your siteEmbed the widget on the page people land on. Anyone who was going to fill in a contact form gets a priced quote instead.
3. 3Paid campaignsGive each campaign its own link so the reservation that eventually books can be traced back to the ad that produced it.
4. 4Physical presenceA QR code on the truck turns a job you are already doing into intake for the neighbours watching it.

Channels are cheap to add and expensive to evaluate by feel. Because each link carries its source into the session and through to the booked reservation, the comparison is between booked moves rather than between click counts.

Session records go further than the source: you can see where a session stalled and what the customer changed before submitting, which is usually more useful than knowing that it stalled at all.

The hosted link needs nobody. The widget is a single snippet pasted once. A developer is only involved if you want to drive sessions from your own systems through the API, or receive signed webhook events into a CRM, dispatch board or warehouse.

There are no first-party SDKs yet. The API is plain REST and JSON, so any HTTP client works today, and the published OpenAPI document can generate a client in your language now.