Skip to content

Enquiry forms

Clients can enquire in three ways: on your public enquiry page, through the form embedded on your own website, or through a form you already use that sends its answers to Knotless. New enquiries arrive in Bookings → Enquiries.

Go to Settings → Client-facing → Enquiry forms. The page has four tabs: Share a link, Embed, Connect a form and Theme.

On the Share a link tab, switch Public enquiry page to Active. Then:

  • Choose the Booking type for the link: Event (wedding and venue enquiries), Appointment (service bookings) or Combined (the client picks on the page). Each has its own link, so you can send couples straight to the wedding enquiry and other clients straight to service booking.
  • Copy Your enquiry page link and share it on your website, social media or email signature.
  • Preview page shows the page as clients see it.

The link looks like knotless.co.uk/providers/your-link-name/enquiry.

The Share a link tab, with the public enquiry page active and its link

The public enquiry page as a client sees it

Under Your link name you can change the part after /providers/. Use lowercase letters, numbers and hyphens (2–50 characters, with at least one letter). If another business already uses the name, add something to make it yours, such as your town. Click Save link. Team members can’t change it.

Changing the name changes your enquiry page link and your embed code straight away. Links and embed code that use the old name stop working, so update them wherever you shared them.

The form’s questions are set by Knotless; you choose the booking type and the look.

  • Event: the client’s name, email and phone, the event date and time, the venue (with an optional address and its country; venues from Google Maps are suggested as they type, and one they pick arrives already matched), how many people need your service, and a message about their plans. On a team account, it also asks which services they need. When your price list times a service per person (see How many team members a day needs), it also asks how many people need each one, for example “How many people need hair?”.

    • On a team account, the client answers “How many people need hair?” for each service they ticked, so a mother of the bride who only wants hair and a bridesmaid who only wants makeup are each counted once. The total is then optional (“How many people in total?”), for when some people want both; left blank, it’s the largest of the numbers. It isn’t asked when only one ticked service has a number. If they tick a service your price list doesn’t time (so it has no number), the total is asked and required, because only the total says how many people need that service. Another day asks the same way, and 0 means nobody needs that service that day.
    • Otherwise the form asks how many people need your service, and “How many people need hair?” is optional: left blank, it’s everyone.
    • “The bride isn’t getting ready with us (wedding party only)”, a tick box, unticked to start with. Ticked, the booking has no bride: see Wedding party.
    • “I’m a planner enquiring for a couple”, a tick box above the name. Ticked, the form asks for the planner’s name and email (and optionally her phone and company), and the name, email and phone below it become the couple’s, with the couple’s email optional. The couple is the client. The planner is added to the booking as a planner and made the main contact, so your emails go to her, and the “we’ve received your enquiry” email goes to her too. Her email never becomes the client’s, so each couple she enquires for is a client of their own.

    The quote is priced from these numbers. You see them on the enquiry (“Hair: 2 · Makeup: 3”) and in each day’s People per service on the booking. If you’ve set a booking minimum and chosen to mention it, the form says so above the button, for example “Our booking minimum is £500.00 of services (travel is extra).”

  • Appointment: the client’s details, the Service (from your services, with prices) and a Preferred date & time.

On a team account, the form also lists the team members who offer each service. See Preferred providers.

Under the button, the form shows a short privacy notice.

On the Embed tab, the Embed booking form card gives you one line of code to paste into your website.

  1. Switch Embed booking form to Active. Until you do, nothing shows on your website where you pasted the code.
  2. Choose the Display mode: Inline (the form sits on your page) or Modal (a button opens the form). For a modal, set the Button label.
  3. Choose the Booking type. Form ID names the form inside Knotless; you can leave it as it is.
  4. Click Save embed settings.
  5. Under Your snippet, click Copy and paste it into your website where you want the form.

The snippet is a <script> tag. Your website needs to allow third-party scripts.

The Embed tab, showing the display mode, booking type and your snippet

The Theme tab sets how your enquiry page and embedded form look:

  • Quick presets: Default, Ocean, Forest, Sunset, Minimal or Lavender.
  • Colours: Primary, Accent, Background, Card and Text.
  • Font style: System (Modern Sans), Serif (Classic) or Rounded (Friendly).
  • Page layout: Minimalist, Split Screen, Editorial or Playful. Choose one and click Apply layout.

Preview shows your changes as you go. Click Save changes in the bar at the bottom. Reset goes back to the defaults.

The Theme tab, with presets, colours, font style and the preview

If you already have a contact form on your website (Wix, Squarespace, WordPress…), you can send its enquiries to Knotless. Open the Connect a form tab.

You’ll find two things there:

  • Your webhook URL: https://api.knotless.co.uk/webhooks/forms/[your-id]
  • Your form key: a secret that identifies your account

Send the form key with every request as an X-Knotless-Form-Key header:

POST https://api.knotless.co.uk/webhooks/forms/123
Content-Type: application/json
X-Knotless-Form-Key: kf_your_key_here
{ "fullName": "Ada Lovelace", "email": "ada@example.com" }

If your form tool cannot send custom headers, you can append the key as a query parameter instead:

POST https://api.knotless.co.uk/webhooks/forms/123?key=kf_your_key_here

This works, but it is less secure: query parameters end up in server access logs and browser history. Use the header where you can. Requests without a form key are rejected.

The Connect a form tab with the webhook URL and the form key hidden

Click Rotate next to Your form key if your key is ever exposed, and confirm Rotate key. The old key stops working immediately, so update your website form with the new one straight away or enquiries will start failing.

Under Your connected forms, add a mapping for each form: its Form name (the same name your website sends with each enquiry), then which Booking field each Form field fills, such as Client’s name, Client’s email or Event date. Click Save Mapping.

If your form has a tick box for when the bride isn’t getting ready with you, map it to No bride (wedding party only). A ticked box (sent as true, on, yes or 1) makes the booking wedding party only; anything else, or not mapping it, means the bride is getting ready too.

If your form asks whether a planner is enquiring, map that answer to Enquiring as (planner or couple) (the answer planner turns it on), and her details to Planner’s name, Planner’s email, Planner’s phone and Planner’s company. The planner’s name and email are then needed, and the client’s email is the couple’s and optional.

When an enquiry arrives from a form you haven’t set up, it shows in Bookings → Enquiries with Set up form. Process on a mapping retries that form’s enquiries that are waiting or failed.

Your form doesn’t need to ask for the venue’s country. When Knotless finds the venue on Google Maps, it fills in the country for you, so the enquiry can be priced. If Google wasn’t sure about the venue, the country is filled in when you choose Yes, it’s right on the booking. A venue that isn’t found stays without a country: add it on the booking, then click Calculate price.

Building your own form with Knotless field names

Section titled “Building your own form with Knotless field names”

If you (or your web developer) are building the form yourself, you can skip the mapping step. Name the fields the way Knotless does and add one more header to the request:

X-Knotless-Form-Schema: 1

With that header, no mapping is needed, even for a new form or website. Without it, nothing changes: the enquiry uses your form’s mapping as described above. Any other value, such as 2, is rejected with a 400, so a typo can’t quietly send enquiries down the wrong path.

These field names fill the booking. Every one is optional except fullName and email (with enquirerRole: "planner", email is optional and plannerName and plannerEmail are needed instead), and a booking is created once the event date, venue and party size (or how many people need each service) are there too. Without them, the enquiry arrives as a client to finish, like any other enquiry with missing details.

Field What it is
fullName The client’s name
email The client’s email
phone Phone number
eventDate The event date, as YYYY-MM-DD
ceremonyTime Ceremony time, as HH:mm
readyByTime When they need to be ready, as HH:mm
eventDateTime Date and time together (2027-06-12T14:00), instead of the two fields above
venue The venue’s name, as the client typed or picked it
venueAddress The venue’s address
venueCountry The venue’s country: a two-letter code such as GB, or its name
partySize How many people need your service. Optional with headcount_<service>: left out, it’s the largest of those numbers
headcount_<service> How many people need that service: headcount_hair, headcount_makeup (see below)
preferred_<service>_<1-3> The client’s 1st, 2nd and 3rd choice of team member for that service: preferred_hair_1 (see below)
noBride true when the bride isn’t getting ready with you (the wedding party only). Optional: left out, the bride is in
enquirerRole planner when a planner is enquiring for the couple. fullName, email and phone are then the couple’s
plannerName The planner’s name (needed with enquirerRole: "planner")
plannerEmail The planner’s email (needed with enquirerRole: "planner"). Never used to find or create the client
plannerPhone The planner’s phone
plannerCompany The planner’s business
info Their message
leadSource How they heard about you
instagramHandle Their Instagram
venuePlaceId The Google place ID of the venue they picked (see below)
venueSessionToken The Google Places autocomplete session token for that pick (see below)

Any other field is kept on the booking as an extra answer, labelled from its name: budget shows as “Budget”.

On a team account, send the client’s ranked choices for each service as preferred_<service>_1, preferred_<service>_2 and preferred_<service>_3, for example preferred_hair_1 and preferred_makeup_1. They become the client’s ranked preferred providers for that service, so you can check who’s free and assign from the booking without a workflow. No mapping or answer table is needed.

Each answer is the team member’s key from your enquiry context (GET https://api.knotless.co.uk/api/public/forms/provider/<your-slug>/enquiry-context lists every service’s team members with their key, name and tier, and the service’s choiceFields). A key keeps working if you rename someone. You can send the team member’s name instead: it’s matched ignoring capitals, as long as only one person on your team has that name. “No preference”, “Any” or an empty answer means no choice.

An answer that can’t be used never stops the enquiry from coming in: someone who doesn’t offer that service, a name two people share, a key or name Knotless doesn’t know, or a service your team doesn’t offer. The booking shows a notice for each instead, naming the service.

To ask how many people need hair and how many need makeup, rather than one total, send one field per service: headcount_hair, headcount_makeup, and so on, each a whole number from 0 to 50. If you also send partySize, it’s the total, for when some people want both; without it, the total is the largest of the numbers for services your price list times. A partySize over 50 isn’t used: the enquiry arrives as a client to finish. A form that builds the request in code can instead send serviceHeadcounts, a list such as [{ "serviceSlug": "hair", "count": 2 }].

The quote is priced from these numbers, as it is for your Knotless enquiry form. All of them are optional: a service without a number is quoted for everyone in the party, and a number that isn’t a whole number from 0 to 50, or a service your price list doesn’t time, is ignored rather than stopping the enquiry, and never sets the total.

If your form suggests venues as the client types, using Google’s Places Autocomplete (New), send the picked venue’s place ID as venuePlaceId and the autocomplete session token as venueSessionToken, as well as the venue’s name in venue. Knotless checks the place with Google once, using your session token, and saves the venue as confirmed, so you don’t need to confirm it on the booking.

If Google doesn’t recognise the place ID, or it isn’t in the right format, Knotless looks the venue up from its name instead, as it does for any other form. A session token in the wrong format is left out: the place is still checked and confirmed, just without the session. Knotless doesn’t keep the session token once it has been used.

POST https://api.knotless.co.uk/webhooks/forms/123
Content-Type: application/json
X-Knotless-Form-Key: kf_your_key_here
X-Knotless-Form-Schema: 1
{
"fullName": "Ada Lovelace",
"email": "ada@example.com",
"phone": "07700 900123",
"eventDate": "2027-06-12",
"ceremonyTime": "14:00",
"venue": "Gleneagles Hotel",
"venuePlaceId": "ChIJN1t_tDeuEmsRUsoyG83frY4",
"venueSessionToken": "3f2b8c4e-6a1d-4e7f-9b0a-2c5d8e1f4a7b",
"headcount_hair": "3",
"headcount_makeup": "5",
"preferred_hair_1": "6f1c2a4e-8b3d-4c5e-9a7f-1b2c3d4e5f60",
"preferred_hair_2": "Jess",
"preferred_makeup_1": "Lauren",
"info": "Bride plus four bridesmaids",
"budget": "£1,500"
}

Send this from your website’s server, never from the visitor’s browser: the request carries your form key, which must stay secret. A form that runs only in the browser should post to your own server, and your server forwards it to Knotless with the key.

Form submissions are rate limited per IP address and per provider. Normal enquiry traffic will never hit these limits; automated or repeated test submissions might. A limited request gets a 429 response with a Retry-After header telling you how long to wait.

Your hosted enquiry page and embed are throttled separately from submissions, so previewing your own form can never use up the allowance that real enquiries need.

Form tools resend a submission when they don’t hear back in time. Knotless records each submission once, so a resend of the same submission won’t create a second enquiry, booking or notification. A resend gets the original result back, marked "duplicate": true.

  • If your form tool gives each submission an id, send it as an Idempotency-Key header (up to 255 characters). Each submission needs its own key: reusing a key for a different submission is rejected with a 422. Typeform, Tally and Webflow submission ids are recognised automatically.
  • Without a key, an identical submission from the same page within 24 hours counts as a resend. When you test your form, change a field between test sends or each one after the first will be treated as a resend.
  • If a resend arrives while the first copy is still being processed, it gets a 409 with a Retry-After header. If the first copy failed before anything was saved, the resend tries it again.
  • In the rare case that processing is cut off part way, the enquiry shows in your inbox: as failed (use Retry) if nothing was saved, as needing details if only the client was saved, or with its booking if the booking was created.

On a team account, your own website form can ask the client which team member they’d like, for example with “1st choice”, “2nd choice” and “3rd choice” dropdowns, including separate hair and makeup choices. Knotless turns the answers into the client’s ranked preferred providers. (A form that sends Knotless field names doesn’t need this: see The client’s preferred team members.)

  1. Open the form’s mapping: in Settings → Client-facing → Enquiry forms → Connect a form, add or edit the form under Your connected forms, or choose Set up form on an enquiry from that form on the Bookings page.
  2. Map each choice field, for example to Hair – preferred provider, 1st choice or Makeup – preferred provider, 2nd choice. Up to three choices for hair, three for makeup and so on.
  3. Under Preferred provider answers: Hair (and Makeup), pick the team member each answer your form sends means. Answers your form has already sent are listed, with how often each was seen, and you can type in others with Add an answer. An answer such as “No preference” or “Any” can be set to No preference.

Answers must match exactly what your form sends (spaces at either end are ignored, but capitals count). Knotless doesn’t guess at names. An answer left as Not set shows as unrecognised on the booking.

The client’s choices become their ranked preferences on the booking. If a choice is skipped (say, only a 1st and 3rd choice), the ranks close up, and someone picked twice keeps their best rank.

An answer that isn’t in the table, or names someone who can’t currently take that service, never stops the enquiry from coming in. The booking’s Team & automation tab shows a notice instead, for example “Hair: Unrecognised provider choice: “Jess” (1st choice)” or “Makeup: Provider choice not available: …”. Team leads get an Update form answers link to add the answer for future enquiries.

For an enquiry saved without event details (as a contact only), use Create booking: the new booking gets the choices the enquiry matched, for people who can still take the service. Workflows that start when that booking is created run first, so they don’t see these choices. The notice is removed when the enquiry’s answers are deleted under data retention.

  1. The client sees a confirmation, and may get a confirmation email.
  2. Knotless usually creates a booking with the status Pending, in Bookings → Enquiries, matching the venue on Google Maps.
  3. An enquiry without event details is saved as a client only. Open it from Enquiries and use Create booking when you have the details. The new booking keeps how many people need each service, for the services your price list times; a number for any other service is ignored, as it is when the booking is created for you.
  4. Workflows that start on Booking Created run.

Next: Shared pages.