Booth Studio

Forms.

A form is how details reach you from people outside your business: inquiry forms for your website, booking details forms for your events, and sign-up forms for vendors. This guide walks through making, branding, publishing and filing each kind.

Making a form

A form is how details reach you from people outside your business. Most often it is an inquiry from your own website: a visitor answers your questions - one at a time, or all on one page - and when they send it Booth Studio files the answers as a Contact and a Lead, the same way an inquiry typed in by hand would be filed. New form on the Forms page asks for a name, what it is for - a new inquiry, a client’s booking details or a contact sign-up - a layout and where to start.

  1. Start from the Event inquiry template. A finished inquiry form that asks for name, email, phone, the kind of event, company, the date - then a start time once a date is given, and an end time once a start time is - the venue and city, guest count, what they are interested in, a budget, a notes box and an optional marketing permission question. The event types and services it offers are read from your own settings, and either question is left out while its list there is empty. Change what you like.
  2. Or the template for the other kinds. A Booking details form starts from the Booking details template - guests, the venue, who your crew should ask for on the day, setup time, where the booth goes, unloading, parking, power, Wi-Fi, a backdrop and a message - or from one of three questionnaires: Event questionnaire, Wedding day details or Corporate activation brief (see Questionnaire templates). A Contact sign-up starts from the Vendor sign-up template - name, business, email, phone, website, job title, address, the services they offer, a message and marketing permission.
  3. Or start blank. An empty form with a welcome screen named after it and a plain thank-you screen. Add the questions you want in the order you want them.
  4. Then edit. Either choice creates the form and opens the editor. The form saves itself as you work, and the state beside the title says where it stands.

The editor is three panels. The questions are on the left, in order; the middle is a live preview of the form as a visitor will see it, with a switch between desktop and mobile views; and the settings are on the right, where the welcome and thank-you copy, the button labels and the branding live. Selecting a question on the left shows its own settings in place of the form’s.

  • Wide screens show all three. Questions, preview and settings side by side. On a laptop the left column turns over to the settings instead - Form settings at the top of the list, or selecting a question - and Questions takes you back, so the preview keeps its room and stays in view.
  • A phone shows three tabs. Questions, Preview and Settings, one at a time. The preview on a phone is the same form the visitor gets, at the size they will get it.

The forms list

Forms lists every form with its status, how many submissions it has had and when it was last changed. Any held or failed submissions are flagged beside the count in the attention colour, because they are the ones waiting on you. On a phone, and on an iPad held upright, each form is a card with its status and how many submissions it has had on a row of their own. Open a form and come back with Back, and the list is where you left it.

  • Preview beside the list on a big screen. On a 27" or wider screen, clicking a row shows that form beside the list: what it is for, where it stands, its five latest submissions and its questions in order, with the CRM field each one fills. The arrow keys move through the rows. View all submissions opens the editor on its Submissions; double-click, Enter or Open edits the form.
  • More columns where there is room. On a wide screen Purpose, Layout and Last submission become columns of their own instead of a line under the form name.

What a form is for

Every form is one of three kinds, chosen in New form and shown in the Forms list beside its layout. The kind decides what a submission becomes, which fields its questions can fill, and which of your custom fields it offers.

  • New inquiry. For your website. Every submission becomes a new lead - everything this guide says about lead fields, publishing and embedding is about these.
  • Booking details. Sent from an event. Your client’s answers update that event: on-site details, the venue, who to ask for on the day, and the like. It has no public page; it opens only from a personal link you send.
  • Contact sign-up. For vendors and partners. Every submission becomes a contact, with the role, status and tags you choose. Publish it to a link or embed it, like an inquiry form.

Add question offers each kind its own fields - Lead fields, Event fields or Contact fields - and a question’s settings say Fills the lead’s, Fills the event’s or Fills the contact’s to match. A booking details form never changes an event’s dates, money, people or status: a client who wants a different date says so in their message.

  • A form keeps its kind. The kind is fixed once the form is made, so its published versions and the submissions they took always mean the same thing. To use a form you already built for another purpose, choose Duplicate as… from its menu on the Forms page and pick the kind. Every question is kept; one linked to a field the new kind can’t fill becomes an ordinary question whose answer goes into a note, and the copy opens in the editor, unpublished, with the publish check saying what still needs attention.

Conversational or classic

Every form has one of two layouts, chosen in New form and shown in the Forms list under each form’s name. The questions, the logic, the branding and what happens to a submission are the same for both; only the way a visitor moves through the form differs.

  • Conversational. One question at a time, full screen, with a Next button, a progress bar and a review of every answer before Send. It suits a longer inquiry on a phone, where one question at a time never feels like a wall of fields.
  • Classic. Every question on one page with a single Send button at the bottom, like a regular website form. It suits a short form, or a page where visitors expect to see everything at once. A question that depends on an earlier answer appears in place below it.

In a classic form the welcome screen becomes a heading above the questions, and there is no Next button or progress bar. An answer that cannot be right, such as an email without an @, is pointed out when the visitor moves on from it. Pressing Send checks everything at once and takes the visitor to the first answer that needs attention.

Change the layout any time in the Form tab of the editor’s settings. Settings that only one layout uses are hidden, not lost, so switching back finds them as they were. A published form keeps its layout until you publish again.

Questions and CRM fields

Add question offers three kinds of question. A lead field - a CRM field - is a question whose answer lands in a named place on the contact or the lead: a name, an email, the event date, the venue. Each can be used once per form, and picking one pre-fills the label, the type and any limits the CRM needs, so a guest count is a whole number and a budget cannot go below zero. The next section lists them all.

A custom field is one of your business’s own questions - “Print size”, “Internet password” - whose answer is kept on the lead where the team can read and edit it. They have a section of their own below.

A blank question is anything else you want to ask, of any type. It needs no mapping: its answer is written into the lead’s inquiry notes as Label: answer, so nothing a visitor tells you is lost.

  • Question types. Short text, long text, email, phone, date, time, number, amount, single choice, multiple choice, dropdown and consent. A lead field is offered only the types that can fill it, so an event date is always a date and an email is always an email. A time reads in the visitor’s own 12- or 24-hour style.
  • Required, description and placeholder. Every question has a label, an optional description under it and a Required switch. Text and number questions take a placeholder; left blank, the field shows a plain default such as “Type your answer here…”, and the Placeholder setting shows you which. A visitor cannot pass a required question without answering it.
  • Options. Single choice, multiple choice and dropdown questions carry a list of options you write. Multiple choice can also set the fewest and the most a visitor may pick. Event type and Interested in are filled from your settings when you add them, and Refresh from settings picks up anything you have changed there since. A custom field’s options belong to the field and are changed on the field, not on the question. The form you change a field from takes its new options at once; Refresh from the field brings any other form up to date with them.
  • Amounts and dates. An amount question shows a currency from the ones you bill in, and a date question can refuse dates in the past or be held between two dates.

Drag a question to reorder it. A rule that points at a question follows it through relabelling, reordering and duplicating - the form keeps track of which question is which. A rule can only look back, though, so keep a question after the one it watches.

Lead fields

The top of Add question is every field a lead is built from, in the order an inquiry reads: Contact, Customer address, Event, Venue, Services & budget, Message and Consent. A field already on the form is greyed with a note saying so, and so is one that would clash with a question you already have, or whose list in Settings is still empty, so the list doubles as a checklist of what the form collects.

  • Contact. First name, Last name, Full name, Company, Phone and Email fill the contact. Ask for a full name, or for a first and a last name - not both: the two would write the same name twice and one would quietly lose, so the publish check names the clash. Either way the lead shows the whole name.
  • Customer address. Customer address, Customer city and Customer postal code are where the client lives or bills from. They fill the address of a contact the form creates. They are not where the event is - that is the venue.
  • Event. Event type fills the lead’s event type, and Event date, Event start time and Event end time become its event date and hours; Event name and Guest count fill theirs. A time is a time on the event day, so a start or end time needs an Event date question on the form, and an end time needs a start time - the publish check says which is missing. An end time earlier than the start is read as running past midnight. If a visitor gives a time with no date, an end with no start, or an end the same as the start, the times are kept in the lead’s inquiry notes rather than lost.
  • Venue. Venue name, Venue address and Event city are where the event happens, and fill the lead’s venue and its address. On the lead page the two addresses stay apart: the client’s is Address under Lead details, the venue’s is Venue address under Event details.
  • Budget - an amount or a range. Budget - amount asks for a number and fills the lead’s Budget, in the currency the question shows. Budget - range is a list of ranges in your own words - it starts with four, from “Under $1,000” to “$5,000 or more”, for you to rewrite to suit; the range the visitor picks lands on the lead as its Budget range, in exactly those words, and is never turned into a number. Use one or the other - both fill the same budget. An amount too large to be a real budget is kept in the inquiry notes instead.
  • Services, message and consent. Interested in offers your catalogue and fills what the lead is interested in. Message / inquiry is the visitor’s own words and opens the lead’s inquiry. Marketing permission is covered at the end of this guide.

Address lookup. Where address lookup is available for your business, the Customer address, Venue name and Venue address questions suggest places as the visitor types. Picking one fills the question and, when the form asks them, the questions that go with it: a customer address fills Customer city and Customer postal code, a venue name fills Venue address and Event city, and a venue address fills Event city. The parts no question asks, such as the suite, province or state and country, travel with the submission, so a new contact, or the lead’s venue, still gets the whole address.

The venue: picked or typed. A form that asks where the event is takes the venue either way. Picking it from the suggestions fills in its address, which is what the lead’s tax is worked out from. A venue the lookup does not know - a new hall, a backyard, a name spelled differently - can simply be typed: a typed venue is accepted, and what the visitor typed is what is filed on the lead, with no address made up for it. Add the address on the lead when you quote. While lookup is working the form does ask for one or the other: a client who has not booked a venue yet ticks We haven’t booked a venue yet instead; the venue questions empty and lock, the lead arrives with “Venue not booked yet” in its inquiry, and its quote uses your default tax rate until you add the venue. This holds whether or not the venue questions are marked Required.

A box the visitor has already filled in is never overwritten by a pick, and a filled answer they change afterwards keeps their change. Without lookup - or when the day’s lookups for your business have run out - these are ordinary text boxes, and the venue is not asked for at all unless you mark it Required.

Name, email, phone, company and customer address questions also tell the visitor’s browser what they are, so it can offer to fill them in with one tap. A text question that fills no lead field - a custom field or a blank question - is marked for the browser and password managers to leave alone, so the visitor’s own password is not offered into a field such as “Internet password”.

Custom fields

Some questions are yours alone - “Print size”, “Black and white or colour photos”, “Internet password” - and the answers belong on the lead rather than buried in its notes. A custom field is one of those questions, defined once for your business. Add it to a form from the Custom fields group in Add question, or with Add to form in the Custom fields section of the editor’s Form tab, and each answer is kept on the lead, on its Additional details card, where anyone on the team can read and correct it.

  • Four types. Text for a typed answer, Dropdown for one pick from a list, Select one for one pick shown as choices, and Select multiple for any number of picks. The type is chosen when the field is made and never changes, because the answers leads already hold are shaped by it.
  • Owners and Admins make them. New custom field… at the foot of the Custom fields group, or New custom field in the Form tab, asks for a name, a type, the options for the choice types and whether this form requires an answer, then adds the field to the form. Edit beside a field in the Form tab renames it, changes its options or archives it. Making or changing a field needs an Owner or an Admin; anyone on the team can fill one in on a lead.
  • Shared by every form. A custom field belongs to your business, not to one form. Two forms that both ask “Print size” fill the same field, so the lead page shows one row and every lead answers it the same way. Making a field with a name and type you already have gives you that field rather than a twin. Each field can be asked once per form.
  • Kept on leads and events, or on contacts. Each field lives in one place, decided by the form you make it from and fixed from then on, like its type. A field made on an inquiry or booking details form is kept on Leads & events: an inquiry’s answer lands on the lead, it is copied onto the event when the lead is booked, and a booking details form can read and update it there. A field made on a contact sign-up form is kept on Contacts. A form only offers the fields that live where it writes, and one name can’t be used in both places - the dialog says where the other field lives.
  • Filling the event’s Wi-Fi password or Print size. A Leads & events field can put its answer straight into one of the event’s own details when the lead is booked. In the field’s dialog, When a lead is booked offers Keep it as its own answer, Put it in the event’s Wi-Fi password (for a Text field) or Put it in the event’s Print size (for a Select one or Dropdown field). The answer then goes into the event’s On-site details - unless the booking already has one - and the field is not kept on the event. For Print size, each option fills the size its name mentions, so “4x6 postcard” fills 4x6; the dialog shows each one, and an option that names no size, like “Square”, stays on the lead. Only one field can fill each. Setting it on a field you already have reaches events already booked too: each gets its answer copied in, unless it already has one, and new bookings fill it automatically. Setting it back to Keep it as its own answer changes only leads booked from then on. The field list says “Fills Wi-Fi password when booked”, and Booking details forms ask the event’s own Wi-Fi password and Print size instead of the field.
  • Required is per form. Whether a custom field must be answered is the question’s own Required switch, so one form can insist and another can leave it optional. The lead page never insists: a lead typed in by hand, or from an older form, simply shows the field empty until someone fills it in.
  • Archiving a field, retiring an option. Edit can archive a whole field, and removing an option there retires it. Nothing is deleted: a lead that already holds the field or the option keeps showing it, and an archived field with a value reads on the lead without being editable. From then on neither is offered when you add a question or fill in a lead.
  • Published forms keep asking until you publish again. A published version is frozen, so a form published before the archive keeps asking the field - or offering the retired option - and keeps saving the answers on new leads until you publish it again. A draft that still asks an archived field, or offers a retired option, cannot be published: the publish check names the question until you restore the field or remove or unlink the question - or, for a retired option, press Refresh from the field.
  • Restoring a field. An Owner or an Admin can bring an archived field back from Custom fields › Archived on the editor’s Form tab, with Restore. It is offered again straight away, and editable again on every lead. A retired option has no Restore of its own: add an option with its name again in Edit, and that same option comes back, still held by the leads that chose it.

A blank question is still the right choice for something you only need to read once. Its answer goes into the lead’s inquiry notes, as before.

Showing a question conditionally

Any question can be shown only when an earlier answer matches. Open the question’s settings, choose the earlier question to watch, and say what its answer has to be: equal to a value, not equal to it, or simply answered. A venue question can wait until the visitor has said what kind of event it is; a follow-up can appear only for one choice.

  • Earlier questions only. A rule can only look back. A visitor answers in order, so a question cannot depend on one they have not reached.
  • Hidden questions are skipped. A hidden question is not asked, not required and not sent. If the visitor goes back and changes the answer it depended on, it appears or disappears as it should.
  • Choice and consent values. For a choice question the rule offers its options; for a consent question it offers yes or no. Deleting an option a rule points at warns you first.
  • Changing the question it watches. Pick a different earlier question and the rule keeps whatever still fits it. A comparison the new question cannot answer is cleared, so the rule becomes “is answered”, and a line under Condition says what was cleared, with Undo to put it back. Choose “is” again to pick an answer.

Branding

The form should look like your website rather than like Booth Studio. Look sits at the top of the Form tab in the settings, where the form takes a background colour, a text colour and an accent colour, one font, and a logo: your business logo, a picture you choose, or none. Four starter themes fill in the colours and a matching font at once, and everything can be changed afterwards. A starter keeps a font you uploaded, so trying its colours never takes your brand font away.

  • Contrast warnings. Text on the background, the label on the accent button and the accent against the background are measured as you pick. When one falls under the readable threshold the panel says so, and the Publish drawer lists the same warnings. When error messages can’t be shown in red on your background, the panel says that too, and they use your text colour with a warning mark. It warns rather than stops you, so the decision stays yours.
  • One font. Your own uploaded fonts are listed first, under Your fonts, then the built-in families and the system fonts. Upload a brand font under Brand fonts in Settings › Appearance and it joins the list. The same font carries into the public page and the preview. If a brand font is removed from Settings, forms using it switch to a system font straight away, and the editor says so under Font.
  • Welcome and thank-you copy. The welcome screen has a title, a message and a button. The thank-you screen has a title and a message. The welcome screen can be switched off, in which case the form opens on its first question. In a classic form the welcome screen is a heading instead: a title and a message above the questions, with no button.
  • Button text. What the Next button and the final Send button say. “Send inquiry” reads better than “Submit” on a form about an event. On an optional question the visitor has not answered, the button reads Skip until they answer it. A classic form has only the Send button.

This version brands a form with colours, one font, a logo and copy. It does not carry pictures on questions or picture choices.

Previewing

The preview in the middle of the editor is the real form: the same screens, the same keyboard behaviour and the same branding a visitor will get. Selecting a question on the left jumps the preview to it, so you can read what you just wrote where it will be read. In a classic form the preview scrolls to the question instead and marks it with a short line in your accent colour, and a question that only appears for some answers is shown while it is selected, with a note saying so.

  • Desktop and mobile. The toggle above the preview shows the form at desktop width or inside a phone-sized frame. Check both; a long label that fits a laptop can wrap three times on a phone. On an iPad, or wherever the preview is narrow, it opens on the phone frame.
  • Both at once on a big screen. On a 27" QHD or a 34" monitor the preview shows the desktop form and the phone side by side, so there is no toggle - every change shows in both.
  • Sending in the preview sends nothing. Walk the whole form through to its thank-you screen. Nothing is stored and no lead is created from the preview.

Publishing and embedding

A form has a draft, which is what you edit, and a published version, which is what visitors see. Editing the draft changes nothing live: the public form keeps serving the version you published until you press Update. The list says Draft changes when the two differ.

  1. Fix what the publish check names. A form can be published once it asks for a name and an email or a phone, all required and always shown, so every submission can become a contact, and once every question has a label and every choice a name - a visitor never sees “Untitled question” or “Option 2”. As you work, the editor’s Before publishing list names what it can see in the draft itself, such as a question with no label, a choice left blank, a name question left optional or a start time with no Event date question. The Publish drawer lists those too, and also checks the draft against your business as it stands: that the event types, services and currencies it offers are still yours, that no custom field it asks is archived or offers a retired option, and that Settings › Contact & location holds the details the marketing permission names, with its words still within the length a question can hold once those details are filled in. Each problem names its question - by its label, or “Question 3” while it has none - and pressing it takes you straight to that question. Publish and Update published version both refuse while anything on that list remains, and so does Booth Studio itself, whichever way the form is published.
  2. Publish. Publishing freezes the draft as a numbered version and gives the form a public link. The link is minted once and stays the same through every update.
  3. Share the link or embed the form. Copy the public link to send or post anywhere. To put the form on your own website, copy the embed code and paste it into your page wherever the form should appear - the HTML block in a site builder, or the page itself. The form sizes to its content, so it never needs a scrollbar of its own.
  4. Update when the draft is ready. Once the draft has changes the public page does not show yet, the Publish drawer offers Update published version, which publishes the draft as the next version. Somebody part-way through the old version can still finish it for a week afterwards.
  • Unpublish keeps the link. Unpublish sits at the foot of the Publish drawer, below the link and the embed code. It takes the form offline and shows visitors that it is not available. The address is kept, so publishing again brings the same link back to life.
  • Archiving takes it offline. Archiving takes the public form offline as well as out of the working list. Restoring it does not republish it; press Publish again when you want the link working.

The embed records the page the form was filled in on, so the lead can say which page of your website it came from.

A Booking details form has no public link or embed code: publishing makes it ready to send from your events, and the Publish drawer says so. You never need to unpublish it to edit - publish again, and every link already sent opens the new version. Unpublishing or archiving it stops every link you sent until you publish it again, and the confirmation says how many clients hold one.

Submissions and leads

When a visitor sends the form, Booth Studio looks for a contact with the same email or phone and links the submission to them, or creates a new contact - with the address the form asked for - if there is none. A Lead is then created with the source Website, with the form named on it and the page it was submitted from. Lead field answers fill their fields, custom field answers fill the lead’s Additional details, and any other answer is written into the lead’s inquiry notes.

  • An existing contact is never changed by a form. Anyone can type anyone’s email into a public form, so a form never rewrites a contact that already exists. When what the visitor sent differs from what the contact holds - a new phone number, another company, a different address - it is written on the lead’s inquiry as “Submitted phone: …” and the like, for you to copy across if it is right.
  • The bell and an email. A new inquiry appears in the bell at the top of the app, and opening it goes straight to the lead. It goes to the lead’s owner if it has one, otherwise to every owner and admin, by email as well. The email can be switched off for the whole form in the form’s settings, and each person can switch the bell entry or the email off for themselves in Settings › Notifications.
  • Held for review. A submission that looked automated - sent faster than a person could type, or with a hidden field filled in - is held rather than filed. Nothing is discarded: the visitor still sees the thank-you screen, and the submission waits under Submissions with Accept, which files it as a contact and a lead, and Discard. Owners and admins are told in the bell, and by email no more than once an hour for each form.
  • Failed submissions can be retried. If filing a submission fails after the visitor sent it, the answers are kept and the row reads Failed. Retry files it from the stored answers, or Discard closes it when it is no longer worth filing. The visitor is never shown the failure.
  • Two panes on a big screen. On a 27" or wider screen Submissions opens wide: the list on the left, and the chosen submission - its answers, the lead or contact it became, and Accept, Discard or Retry - on the right. It opens on the first one that needs a decision. The arrow keys move through the list.
  • Sending twice does not file twice. If a visitor’s connection drops and they press send again, the same submission is recognised and one lead is created. The Forms list shows how many submissions each form has and flags any that failed.

Submissions on a form show the answers as the questions were worded in the version the visitor saw, with the contact and the lead it became. A lead created from a form carries the form and the page on its details card, and keeps them even if you re-file the Source later.

Booking details forms

A booking details form collects what your crew needs to know from a client who has already booked - the venue contact, where to unload and park, power, Wi-Fi, the backdrop - and writes it onto that one Event. You build it like any other form, publish it, then send it from the event: open the event and choose Send form. The client gets a personal link that knows which event it is for, so their answers land there and nowhere else. The Events guide covers sending it.

  • Opened only through a personal link. The client’s page leads with the form’s title, then the event’s name and date, and starts filled in with what the event already holds, so they only correct what is wrong. That includes the Wi-Fi password when the form asks for it, so anyone the client forwards the link to can read it - leave that question off if you would rather they could not. Opened without a link, the form says it is sent to people personally.
  • What it can change. Guest count, the venue’s name, address and city, the venue contact and phone, the loading and booth locations, power, space, parking, delivery and access, the setup time frame and preferred setup time, Wi-Fi, print size, props, backdrop, a PO number and your Leads & events custom fields. The message goes onto the event as a note. Never the event’s name, dates, times, stage, owner, services, money or contacts.
  • Leaving an answer as it was changes nothing. An answer the client left exactly as it was shown is not taken as a change, so sending the form again without touching it changes nothing on the event. A blank answer never clears what the event holds.
  • Your changes are never overwritten. If someone on your team changed a detail after the client opened or sent the form, the client’s answer for it is not applied - it goes into a note on the event instead, together with anything the event could not take, such as an answer too long for its field.

A link stops working when you switch it off, when you send that person a newer one, when they are removed from the event, when the form is unpublished or archived, when the event is cancelled, archived or on its Done stage, or once the event has taken place.

Questionnaire templates

Three starting points ask a client the planning questions a questionnaire used to ask, as a booking details form. In New form, choose Booking details as what the form is for, then pick one under Start from. Each is a finished form in its own colours: publish it as it is, send it from an event with Send form, and change any question like any other form.

  • Event questionnaire. For any kind of event, in the Forest colours: when the event starts and what the booth should plan around, indoors or outdoors, where the booth goes, the nearest outlet, which floor and how the crew gets in, what the prints should say and their colours, props and a backdrop, whether guests can send themselves their photos, Wi-Fi, a hashtag, who to ask for on arrival and their number, and a message.
  • Wedding day details. In Ivory & Plum: the ceremony and reception times, the moments to plan around - first dance, speeches, cake cutting and more - guests, the venue, indoors or outdoors, where the booth goes, power, when setup can start, print wording, the wedding colours, props, a backdrop, sharing and Wi-Fi, a hashtag, permission to share a few photos, and the day-of coordinator.
  • Corporate activation brief. In Paper: the brand, the kind of event, what the booth should do, attendees and audience, a link to the logo and brand guidelines, brand colours and photo wording, whose backdrop, props, whether guests’ emails are collected and what else they are asked, the opt-in wording, Wi-Fi, the venue, the stand, space, power, load-in and its window, parking, show services, insurance, the on-site contact and a PO number.
  • Questions that appear when they apply. Outdoor cover is asked only once the booth is outdoors, which props only once props are wanted, and the Wi-Fi password only once there is Wi-Fi. In the brief, the guest-data questions wait for an opt-in, show services for a trade show and the certificate details for a venue that needs one.
  • Two or three required questions, never more. Indoors or outdoors - in the brief, the kind of event and whether guests’ emails are collected - and who to ask for on arrival. Indoors or outdoors and the email question each offer Not sure yet, so a client who has not decided can still send what they know.
  • Nothing the event already knows is asked again. No date, booked hours, package, price or print size: a client who wants another date or time says so in the last question. Whichever of guests, the venue, the on-site contact and phone, where the booth goes, power, space, loading, setup, parking, delivery and access, Wi-Fi, props, backdrop and PO number a template asks arrives filled in from the event, and the client’s answer updates it. Every other answer goes into a note on the event as “Question: answer” lines.

With no backdrops in your settings, the backdrop question is left out. The wedding template’s photo permission is a tick box the couple can leave unticked; it is kept with their answers and is not marketing permission.

Contact sign-up forms

A contact sign-up form is how vendors and partners - a white label supplier, a photographer you work with - put themselves into your Contacts. Publish it to a link or embed it, like an inquiry form. In the editor’s Form tab, New contacts sets the role, status and tags each new sign-up gets; the Vendor sign-up template starts them as a Supplier with the status Vendor.

  • Matched on email only. A sign-up with an email no contact has becomes a new contact, with their details, the role, status and tags you chose, their answers to your Contacts custom fields, and a note with their message and any other answers. A sign-up asks for a name and an email, required and always shown: the email is how an existing contact is recognised.
  • An existing contact is never changed. When the email already belongs to a contact, nothing on that contact changes - no details, tags, role or custom fields. A note is added instead, saying what the form said differently and what it would have set.
  • Same phone, different email. When the phone number they gave belongs to someone else, the new contact is still made, and its note starts with “Possible duplicate of …” so you can check before merging.