Configuring booking form submission actions

Modified on Wed, 6 May at 6:51 AM

Configuring booking form submission actions

Submission actions control what happens when a customer submits a booking form — validation, resource assignment, redirect behavior, and the calendar event that gets created.

TL;DR

Access: Edit booking form → On submission button. Configure: Field validation (always enable), Assign booked resource to lead (yes for follow-up workflows), Redirect on success (stay / URL / internal page). Resulting calendar event: set title, location, and description using placeholders — include lead contact info, %lead_link_raw% (direct lead profile link), and %page[page-slug,url]% (upload/confirmation page links) in the description.

4 things to configure

1

Field validation

Apply field rejection rules: Yes — validates required fields before submission (always recommended). Show rejection message box: Yes — shows specific error messages to users when validation fails. The form submits via Ajax, so no page reload occurs. Test by submitting incomplete forms to verify the validation messages appear correctly.

2

Resource assignment

Assign booked resource to lead: Enable when the booked consultant/technician/room should be linked to the lead for follow-up automations or manual workflows. This allows automations to reference %assigned_person_*% placeholders and filter/search leads by assigned resource. Disable for facility/room bookings where no follow-up is needed.

3

Redirect on success

Stay on page — for embedded forms where navigation would disrupt UX. Redirect to URL — for external confirmation page. Redirect to web page — for a Hubhus confirmation page with booking details, upload links, or next-step instructions. Use redirect when you want to show detailed post-booking info or track conversions.

4

Calendar event: title, location, description

Title: Keep concise — e.g. Consultation: %lead_name% or %event_service_names% - %lead_city%. Location: Auto or %lead_full_address% for on-site jobs. Description: include <a href="%lead_link_raw%">Go to customer</a>, upload page link, phone, comments. Color: Auto (resource-based) or fixed color per service type.

Read more

Complete event description example

Paste this directly into the Event description field. Replace page slug and custom field names as needed:

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

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

Service: %event_service_names%
Duration: %event_duration_minutes% min
Resource: %event_resource_name%

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

Placeholder reference — calendar event fields

Lead info

  • %lead_name% — Full name
  • %lead_firstname% / %lead_lastname%
  • %lead_phone% / %lead_email%
  • %lead_company%
  • %lead_address% / %lead_city% / %lead_full_address%
  • {{custom-field-slug}} — any custom field value

Event-specific (use %event_xxx% — NOT %booking_xxx% — in event config)

  • %event_service_names%
  • %event_duration_minutes%
  • %event_start_date% / %event_start_time% / %event_datetime%

Resource

  • %event_resource_name%
  • %event_resource_email% / %event_resource_phone%

Links

  • %lead_link_raw% — direct link to lead profile (for staff)
  • %page[page-slug,url]% — link to a specific Hubhus web page (upload page, confirmation, portal)

Common configuration scenarios

Consultant booking

  • Apply rejection rules: Yes | Show rejection message: Yes
  • Assign booked resource to lead: Yes (enables follow-up automations)
  • Redirect on success: → Hubhus web page (confirmation with booking details)
  • Event title: Consultation: %lead_name%
  • Event description: contact info + lead link + optional upload link

Service/installation booking

  • Assign booked resource to lead: Yes (link technician to lead)
  • Location: %lead_full_address%
  • Event title: %event_service_names% - %lead_company%
  • Description: contact + upload link + comments field

Facility/room booking

  • Assign booked resource to lead: No (no follow-up needed)
  • Redirect: Stay on page (show success message)
  • Event title: Room booking: %lead_name%
  • Location: static room name

Troubleshooting

  • Validation not working: Enable "Apply field rejection rules: Yes" AND "Show rejection message box: Yes"
  • Placeholders empty in event: Use %event_xxx% (not %booking_xxx%) in event title/description/location
  • %page[] link 404: Verify the page slug exists in Account → Web Resources → Web Pages
  • Wrong resource assigned to lead: Check booking form resource configuration — the assigned resource comes from what the customer selected in the booking step
  • Redirect not happening: Verify the redirect option is saved. If "Stay on page" is selected, the page won't navigate after submission.

Common searches

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

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article