All documentation · Customers & deals

Forms and booking pages

Build forms that write straight into your CRM, control how submissions match existing leads, and publish booking pages with availability, buffers, and hosts.

9 min read · Reviewed

Forms and booking pages are how leads get into Clyentra without anyone typing them in. A form captures a person; a booking page captures a person and puts time on a calendar. Both write straight into your CRM, so a submission is a lead, not an email you have to re-key.

They live under Marketing: Forms are at /marketing/forms and booking pages at /marketing/bookings — under Marketing, not Sales. They feed the sales pipeline, but they're built where the rest of your outbound surface lives. See marketing-hub.

Building a form

The heading at /marketing/forms is Forms & Surveys — "Build forms that capture leads and feedback straight into your CRM." Hit New Form to start.

You can Start from a template: Contact Info, RSVP, Event Registration, Order Form, or Customer Feedback. Or start blank — a new form arrives with a Name field and a required Email field already in place, because a form that can't identify who filled it in isn't much use.

Field types

Add field gives you: text, email, phone, number, textarea, select, radio, checkbox, date, rating, nps, and section (a divider for grouping). The nps and rating types are what make this a survey builder as well as a lead capture tool.

Map fields to lead fields — this is the part that matters

Every field has a Map to lead field select. This is the bridge between a form answer and a CRM record. Map to: Full name, First name, Last name, Email, Phone, Company, Website, Industry, City, State, Country, or Notes — plus any custom fields you've defined — or choose Don't map for questions that are only ever questions.

There is also an Add lead field button, which drops in a field already wired to a lead property. Use it when you know you want the data on the lead record, and let the form builder do the mapping for you.

An unmapped field is data you'll have to copy by hand: Anything left on Don't map still gets stored with the submission, but it never reaches the lead record. If you want a rep to see it in the lead sidebar, map it — Notes is the catch-all.

Lead matching — one person, one lead

Under Settings → Lead matching you decide what happens when someone who's already in your CRM fills in a form. Five strategies:

StrategyUse it when
Match by email or phone (recommended) — the defaultAlmost always. The widest net; catches the same person however they identified themselves.
Match by email onlyPhone numbers in your data are unreliable or shared.
Match by phone onlyPhone is your primary identifier and emails are throwaway.
Match by email and phoneBoth must agree. Strictest — fewest false merges, most duplicates.
Always create a new leadEach submission is genuinely a separate event, e.g. an event RSVP form.

Clyentra spells out the promise: "The same person submitting different forms is matched to one lead — every submission is still kept." Matching does not lose data. It stops you ending up with four Dana Reeds and a rep who has no idea which one is real.

The same panel holds a Success message — default "Thanks! Your response has been recorded." Change it to say what actually happens next: someone will call, or a proposal is coming.

Design and publish

The Design tab has Accent color, Page background, and a Show organization name & logo toggle, with a live preview beside it. That's enough to make the page look like it belongs to you rather than to a form vendor.

  1. Add and map your fields. Keep it short. Every extra field is a person who doesn't finish.
  2. Set lead matching. Leave it on Match by email or phone (recommended) unless you have a specific reason not to.
  3. Style it. Accent color, Page background, and your logo.
  4. Save. The save control is a split button: Save & Publish puts it live, Save as Draft doesn't.
  5. Grab the link. Once published you get Copy link and Preview. The public URL is /forms/{slug}.

Bots are handled: Every published form carries a hidden honeypot field. You don't configure it and visitors never see it — it quietly absorbs a lot of junk that would otherwise become junk leads.

Reading submissions

The Submissions tab lists everything that came in: Submitted, Email, Phone, Score, and Lead ID. Each row has an Open lead link straight into the CRM record, and you can Export CSV.

The Score column is your lead score, already computed. A form submission is not a raw inbox item — it arrives scored, and if Automatically route new leads is on, already assigned. See lead-routing.

Booking pages

At /marketing/bookings the heading is Booking — "Public pages that capture a lead and schedule an appointment." Note both halves of that sentence: a booking is a lead and a calendar event. Hit New booking page to build one.

There's a shortcut: Design with AI — "Describe your business and we'll draft the page, copy and theme." It gives you a starting draft you then edit like any other page.

The booking builder

Eight sections: Page design, Details, Availability, Scheduling rules, Host(s), Intake fields, Custom domain, and Status.

SettingDefaultWhat it controls
Duration30 minutesLength of the appointment
Weekly availabilityMon-Fri 09:00-17:00The hours you're bookable
Max days ahead60How far into the future someone can book
Slot interval (min, 0 = duration)How often a slot starts. 0 means slots are back-to-back at the meeting's own length.
Buffer before (min) / Buffer after (min)Breathing room around each booking
Min notice (min)How close to now someone can grab a slot
TimezoneThe zone your availability is expressed in

Min notice is the setting that saves your morning: Without it, a prospect in Berlin can book you for eight minutes from now. Set a min notice that reflects how much warning you actually need to prepare.

Meetings can be Virtual, In person, or Phone. At least one host is required — a booking page with nobody to meet is not a booking page. Under Intake fields, Clyentra tells you what it already collects: "Name, email and phone are collected by default. Add extra questions:" — so ask only for the things you don't already get.

Publishing and your own domain

Status is Draft or Published, and the card action is Publish / Unpublish. The public URL is /booking/{slug}. An unpublished page tells visitors: "This booking page is unavailable."

For a branded link, use Custom domain: point a CNAME — say book.yourbrand.com — at the app, and your booking page answers on your own domain instead of ours.

What guests see

Guests pick a slot from your live availability. If someone else takes that slot between the page loading and the guest submitting, Clyentra catches the collision rather than double-booking you: "That time was just taken — please pick another."

After booking, guests get a manage link at /booking/manage/{token} where they can Reschedule or Cancel booking themselves. The link can expire — a guest who follows a stale one sees "This booking link is invalid or expired."

What happens to the lead afterwards

A submission or a booking becomes a lead like any other: it gets scored, it gets routed, and it can trigger a workflow. The Welcome new leads and Follow-up task for new leads workflow templates in workflow-automation both fire on lead creation — which means a form submission at 2am can have an acknowledgement sent and a task waiting for a rep by the time anyone wakes up.

Questions people ask

Why are forms and booking under Marketing instead of Sales?

Because they're public-facing pages, they live with the rest of your outbound surface: forms at /marketing/forms, booking at /marketing/bookings. What they produce — leads — lands squarely in Sales, at /customers/leads.

Someone filled in two of my forms. Do I get two leads?

Not with the default matching strategy. Match by email or phone (recommended) ties them to one lead: "The same person submitting different forms is matched to one lead — every submission is still kept." Pick Always create a new lead only if each submission really is a separate event.

A form field I added isn't showing up on the lead record.

It's probably still set to Don't map. Open the field and pick a target in the Map to lead field select — Full name, Email, Phone, Company, Industry, City, Notes, or one of your custom fields. Unmapped answers are kept with the submission but never reach the lead.

How do I stop people booking me with no notice?

Set Min notice (min) in Scheduling rules. While you're there, Buffer before (min) and Buffer after (min) keep back-to-back meetings from colliding, and Max days ahead (default 60) caps how far out anyone can book.

Can two people book the same slot?

No. If a slot is claimed between the page loading and a guest submitting, Clyentra rejects the second booking with "That time was just taken — please pick another."

Can guests cancel or move their own booking?

Yes. Every guest gets a manage link at /booking/manage/{token} with Reschedule and Cancel booking. Note the link can expire — an old one shows "This booking link is invalid or expired."

How do I run my booking page on my own domain?

Use the Custom domain section in the builder and point a CNAME — for example book.yourbrand.com — at the app. Guests then see your domain instead of the default /booking/{slug} URL.

Every Clyentra guide