Skip to main content

Intake Forms

Create customizable Intake Forms to capture inquiries from your website or social media, automatically create Contacts, Accounts, and Bookings, assign leads, send notifications, reduce spam with reCAPTCHA, and automate follow-up emails.

🎥 Watch the Intake Forms Masterclass for a walkthrough.

Intake Forms let you capture inquiries directly from your website, social media, or QR codes. When a guest submits a form, Event Temple automatically creates a Contact, Account, and Booking so your team can respond quickly and never miss a lead.

🔐 Note: Chain Admin permissions are required to create or edit Intake Forms within a Chain.


Create an Intake Form

  1. Go to Settings → Tools → Intake Forms

  2. Click Add New Form

  3. Enter a Form Name

  4. Click Create

  5. Customize the form

  6. Click Save

  7. Embed the form on your website or share it using the direct link or QR code.


Customize Your Intake Form

Intake Forms are fully customizable, allowing you to collect only the information you need.

Within the Fields tab you can:

  • Add Contact, Account, and Booking fields

  • Add section headers

  • Rename field labels

  • Mark fields as required or optional

  • Add Contact, Account, or Booking Custom Fields

  • Use dropdowns, checkboxes, and text fields to collect information such as:

    • Preferred room

    • Number of attendees

    • Preferred time slot

Tip: Shorter forms typically receive more submissions.

Available Fields

Contact Fields

  • First Name

  • Last Name

  • Email

  • Phone Number

  • Comment

  • Contact Custom Fields

Account Fields

  • Account Name (required when using Account fields)

  • Comment

  • Account Custom Fields

Booking Fields

  • Booking Name

  • Start Date

  • End Date

  • Booking Type

  • Referral Source

  • Comment

  • Booking Custom Fields


Prevent Duplicate Contacts

If a submission uses an email address that already exists:

  • The new Booking is linked to the existing Contact.

  • Existing Contact information is not overwritten.

This prevents duplicate Contacts and protects existing CRM data.


Capture Event Information

Event-specific fields (such as Event Type or Expected Attendance) cannot currently be added directly to Intake Forms.

Workaround

Create a Booking Custom Field instead.

For example:

  • Preferred Space

  • Number of Attendees

  • Preferred Time Slot

After submission, transfer this information to the Event as needed.


Submit Settings

Submit Settings determine what happens after a guest submits a form.

Confirmation Message

After submission you can either:

  • Display a custom Thank You message

  • Redirect guests to another webpage

You can also pass the guest's name and email through the redirect URL for personalized tracking.


Booking Assignment & Notifications

Each submission automatically creates a Booking that is assigned to:

  • A User

  • A Booking Stage

You can also notify additional team members by email.

Change the Assigned Booking Stage/User

  1. Go to Settings → Tools → Intake Forms

  2. Edit the Intake Form

  3. Open Submit Settings

  4. Select a new Booking Stage or User

  5. Click Save

Changing the assigned User will:

  • Update the Form Owner

  • Automatically add their email address to notification emails


Auto Responder

Automatically send an email after a guest submits a form.

  1. Enable Auto Responder

  2. Select an Email Template

  3. Optionally set a delay

The email is sent from the assigned User's connected email account.

If that email account becomes disconnected, the Auto Responder will stop sending and a warning will appear on the Booking.


Prevent Spam Submissions

To help reduce spam and automated form submissions, enable Google reCAPTCHA on your Intake Form.

Enable reCAPTCHA

  1. Go to Settings → Tools → Intake Forms

  2. Edit the Intake Form

  3. Open the Fields tab

  4. Select the Submit Button

  5. Enable Show reCAPTCHA

  6. Click Save

While reCAPTCHA cannot eliminate all spam, it significantly reduces automated submissions.

Did this answer your question?