Configuring booking form submission actions

Modified on Fri, 9 Jan at 3:20 PM

Configuring booking form submission actions

Submission actions control what happens when a customer submits a booking form. This guide explains how to configure field validation, assign resources to leads, redirect users after booking, and customize the resulting calendar event with dynamic content.

On this page

Configuring booking form submission actions

What are submission actions?

Submission actions define the behavior and outcomes when a customer successfully submits a booking form. They control validation, resource assignment, user experience, and the calendar event that gets created.

Common uses:

Validate booking data – Ensure required fields are filled correctly
Assign resources automatically – Link the booked resource (consultant, room, service) to the lead
Create calendar events – Generate appointments with custom titles, descriptions, and links
Guide user flow – Redirect to confirmation page or keep user on current page
Provide booking details – Include links to upload files, access customer portals, or view booking info

Accessing submission action settings

To configure submission actions for a booking form:

Go to Campaign Settings → Booking forms
Click Edit on the booking form you want to configure
Click the green On submission button (usually in the top-right area)
The Edit booking confirmation submission actions modal opens

Field validation settings

Apply field rejection rules

Control whether the form validates field values before allowing submission.

Options:

Yes - validate values – Form checks that all required fields are filled and valid before submission
No – Form submits without validation (not recommended for most use cases)

Recommended: Always use "Yes - validate values" to ensure data quality.

Show rejection message box

Display error messages to users when validation fails.

Options:

Yes – Show a message box with specific validation errors (recommended)
No – Validation happens silently (not user-friendly)

What users see:

When validation fails with rejection message box enabled, users see specific errors like:

"Please fill in your email address"
"Please select a valid date"
"This field is required"

Assign booked resource to lead

Automatically assign the booked resource (consultant, technician, room, equipment) to the lead record.

Options:

Yes – The resource selected during booking becomes the assigned person/resource on the lead
No – Booking is created but no assignment happens
Custom field mapping – Assign to a specific field or person based on rules

Use cases:

Consultant booking – Assign the consultant to the lead for follow-up
Service booking – Link the service provider to the lead
Room booking – Track which room/location was booked

On successful form submission

These settings control what happens immediately after a valid booking is submitted.

Note

The form is submitted using Ajax, meaning the page doesn't reload unless you configure a redirect.

Redirect to page on success

Choose where users go after successful booking submission.

Options:

Stay on page – User remains on the current page (form typically shows a success message or resets)
Redirect to URL – User is sent to a specific confirmation page or external URL
Redirect to web page – User is sent to a Hubhus web page (e.g., confirmation page with booking details)

When to stay on page

Embedded booking form on your website
Single-page booking experience
You want to show a success message without navigation
User might book multiple times (e.g., recurring appointments)

When to redirect

Show detailed booking confirmation with links
Provide additional information after booking (what to bring, how to prepare)
Collect payment or additional details
Track conversions with separate thank-you page

Resulting event configuration

Configure the calendar event that's automatically created when a booking is submitted.

Event title

The title of the calendar event. Supports placeholders for dynamic content.

Examples:

Consultation: %lead_name%

%event_service% - %lead_company%

Appointment with %lead_name% (%lead_phone%)

Common placeholders:

%lead_name% – Customer's full name
%lead_company% – Company name
%lead_phone% – Phone number
%lead_email% – Email address
%event_service% – The booked service name
%resource_name% – The assigned resource name
{{custom-field}} – Any custom field value

Event location

The location shown in the calendar event.

Options:

Auto – Uses the default location from booking form or resource settings
Custom text – Enter a specific address or location
Placeholder – Use dynamic location from lead data (e.g., %lead_address%)

Examples:

Auto

Main office - Meeting room 3

%lead_address%, %lead_city%

Virtual meeting - Teams link in description

Event description

Detailed information shown in the calendar event. Supports HTML, links, and placeholders.

Common patterns:

Upload link for customer files

<a href="%page[upload-billeder,url]">Upload images</a>

Provides a link where customers can upload required documents or photos before the appointment.

Direct link to lead profile

<a href="%lead_link_raw%">Go directly to customer</a>

Allows staff to quickly access the full lead profile from the calendar event.

Comments and special requests

Comments: {{comments-or-special-requests}}

Displays any notes or special instructions the customer provided during booking.

Contact information

Phone: %lead_phone%
Email: %lead_email%
Address: %lead_full_address%

Service details

Service: %event_service%
Duration: %event_duration%
Resource: %resource_name%

Complete example

<a href="%page[upload-billeder,url]">Upload images</a>
<a href="%lead_link_raw%">Go directly to customer</a>

Customer: %lead_name%
Phone: %lead_phone%
Email: %lead_email%

Service: %booking_service%
Comments: {{comments-or-special-requests}}

Event color

The color used to display the event in calendar views.

Options:

Auto – Uses the default color from the booking service or resource
Custom color – Choose a specific color for this booking form's events

Color strategy:

Use different colors for different service types (e.g., consultations = blue, installations = green)
Use Auto if you want resource-based coloring (each consultant has their own color)
Use consistent colors across similar booking forms for visual clarity

Useful placeholders for events

Lead information placeholders

%lead_name% – Full name
%lead_firstname% – First name only
%lead_lastname% – Last name only
%lead_phone% – Phone number
%lead_email% – Email address
%lead_company% – Company name
%lead_address% – Street address
%lead_postal_code% – Postal code
%lead_city% – City
%lead_full_address% – Complete address (street, postal code, city)

Event-specific placeholders

Note

Use %event_xxx% placeholders for calendar events. %booking_xxx% placeholders only work inside the booking form itself, not in event configuration.

%event_service% – Service name
%event_duration% – Duration (e.g., "60 minutes")
%event_date% – Event date
%event_time% – Event time
%event_datetime% – Full date and time
%event_start% – Event start time
%event_end% – Event end time

Resource placeholders

%resource_name% – Resource name (consultant, room, equipment)
%resource_email% – Resource email (if person)
%resource_phone% – Resource phone (if person)

Link placeholders

%lead_link_raw% – Direct link to lead profile (for internal staff)
%page[page-slug,url]% – Link to specific web page (e.g., upload page, confirmation page)

Best practices

Validation settings

Always enable "Yes - validate values" to ensure data quality
Always enable "Show rejection message box" for better user experience
Test validation by submitting incomplete forms to see error messages
Configure appropriate field requirements in the booking form itself

Resource assignment

Enable resource assignment when you need follow-up workflows
Disable if bookings are informational only (e.g., facility rentals)
Use assignment to trigger automations (e.g., send consultant confirmation email)
Consider using status changes based on assigned resource

Redirect strategy

Stay on page for embedded forms where navigation would disrupt user experience
Redirect for standalone booking pages where you want dedicated confirmation
Create confirmation pages with additional context (what to expect, how to prepare, cancellation policy)
Use redirects to track conversions with analytics

Event title best practices

Keep titles concise (50 characters or less for calendar readability)
Include the most important identifier (usually customer name or company)
Add service type if you have multiple booking forms
Include phone number if staff needs to call before appointment

Good examples:

Consultation: %lead_name%
%booking_service% - %lead_company%
Installation: %lead_name% (%lead_phone%)

Avoid:

Very long titles with all details (use description instead)
Generic titles like "Appointment" (not helpful when viewing calendar)
Unnecessary words like "Booking with" or "Meeting for"

Event description best practices

Include direct links to lead profile for staff convenience
Provide upload links if you need files before the appointment
Add all contact information (phone, email, address) so staff don't need to open lead profile
Include special requests or comments from customer
Add service details and duration for clarity
Use HTML formatting for better readability (<br> for line breaks)
Test links before going live

Event color organization

Use Auto if resources have their own colors (consultant-based coloring)
Use custom colors for service-based organization
Maintain consistent color scheme across booking forms
Consider colorblind-friendly color choices
Use contrasting colors for easy differentiation in busy calendars

Common configuration scenarios

Consultant booking scenario

Use case: Customer books time with a specific consultant.

Configuration:

Apply field rejection rules: Yes - validate values
Show rejection message box: Yes
Assign booked resource to lead: Yes
Redirect to page on success: Redirect to confirmation page
Event title: Consultation: %lead_name%
Event location: Auto (uses consultant's office location)

Event description:

<a href="%lead_link_raw%">Go to customer</a>

%lead_name%
Phone: %lead_phone%
Email: %lead_email%

Comments: {{comments}}

Event color: Auto (each consultant has their own color)

Service/installation booking scenario

Use case: Customer books an installation or service visit at their location.

Configuration:

Apply field rejection rules: Yes - validate values
Show rejection message box: Yes
Assign booked resource to lead: Yes
Redirect to page on success: Redirect to upload page
Event title: Installation: %lead_name% (%lead_city%)
Event location: %lead_full_address%

Event description:

<a href="%page[upload-photos,url]">Upload photos</a>
<a href="%lead_link_raw%">Go to customer</a>

Service: %booking_service%
Customer: %lead_name%
Phone: %lead_phone%
Address: %lead_full_address%

Special requests: {{special-requests}}

Event color: Green (installations)

Facility/room booking scenario

Use case: Customer books a meeting room or facility.

Configuration:

Apply field rejection rules: Yes - validate values
Show rejection message box: Yes
Assign booked resource to lead: No (room booking, no follow-up needed)
Redirect to page on success: Stay on page
Event title: %resource_name%: %lead_company%
Event location: %resource_name%

Event description:

Booked by: %lead_name%
Company: %lead_company%
Phone: %lead_phone%
Participants: {{number-of-participants}}
Equipment needed: {{equipment-requests}}

Event color: Auto (each room has its own color)

Troubleshooting

Validation not working

If forms submit without validation:

Verify Apply field rejection rules is set to "Yes - validate values"
Check that fields are properly marked as required in the booking form configuration
Test with browser console open to see JavaScript errors
Ensure rejection message box is enabled to see validation feedback

Placeholders not appearing in events

If placeholders show as literal text instead of values:

Check placeholder syntax (correct: %lead_name%, incorrect: lead_name)
Verify the field exists and has data for test bookings
Use correct placeholder type (% for system fields, {{ }} for custom fields)
Test with a real booking submission, not just preview

Links not working in event description

If links don't work when clicked from calendar events:

Verify HTML syntax is correct (<a href="URL">Text</a>)
Ensure URLs are complete (include https://)
Test %lead_link_raw% by copying link from event and opening in browser
Check that web pages referenced in %page[slug,url]% exist and are active
Test links in the event description field by viewing a created event

Wrong resource assigned to lead

If the wrong person/resource gets assigned:

Verify Assign booked resource to lead is configured correctly
Check if there are automation rules overriding the assignment
Ensure resources are properly configured in the booking form
Test with different resource selections to verify behavior

Redirect not happening after submission

If users don't get redirected after booking:

Check that Redirect to page on success is not set to "Stay on page"
Verify the redirect URL or web page exists
Look for JavaScript errors in browser console
Test with a fresh browser session (clear cache)
Ensure Ajax submission is working properly

Summary

Booking form submission actions control validation, resource assignment, user flow, and calendar event creation. Access settings by clicking the On submission button when editing a booking form. Enable field validation with "Yes - validate values" and show rejection message box to ensure data quality and provide user feedback. Configure whether the booked resource (consultant, room, service) should be assigned to the lead for follow-up workflows. Choose to redirect users to a confirmation page or keep them on the current page after successful booking. Customize the resulting calendar event with dynamic event title, location, description, and color. Use placeholders like %lead_name%, %booking_service%, %resource_name%, and {{custom-field}} to populate event details dynamically. Include links in event descriptions using <a href="%page[slug,url]"> for upload pages and %lead_link_raw% for direct access to lead profiles. Follow best practices: always validate, keep event titles concise, include all relevant contact information in descriptions, use HTML formatting for readability, and test all links before going live. Configure differently based on use case: consultant bookings should assign resources and redirect to confirmation, service bookings should include address and upload links, facility bookings may not need resource assignment. Test submission actions thoroughly with real bookings to ensure validation, links, placeholders, and redirects work as expected.

? Common searches

booking submission • on submission • booking confirmation • calendar event • event description • validation • redirect after booking • booking actions

? Also known as

booking form actions • submission settings • form validation • booking event • calendar appointment • confirmation page • after booking

Creating and managing booking forms
How do I customize booking form fields?
How do I configure booking duration and time restrictions?
How do I configure booking form error and info messages?
Understanding placeholders and dynamic content