How do I configure booking form error and info messages?
When a customer can't complete a booking, Hubhus shows a message. You control exactly what that message says — per form, per scenario. A good message turns "I can't book" into "I understand what to do next."
TL;DR
Go to Campaign → Booking forms → [your form] → Form messages. You get one text field per blocking scenario. Use %booking_postal_city% and %booking_location% to make messages specific. Always offer a fallback action (phone, email).
4 messages you can configure
Not supported postal code — shown when the postal code is outside your allowed area.
Example: "Booking is unfortunately not available in postal code %booking_postal_city%."
Address too far from base — shown when the address exceeds your Max. driving from base setting.
Example: "The address %booking_location% is too far away. Please contact us by phone or email."
No available times found — shown when the form can't find any bookable slots given current rules.
Example: "No available times were found in this period. Try another date or contact us for help."
Unknown address — shown when Hubhus can't calculate transit because the address is incomplete. If left blank, Hubhus allows booking anyway and skips transit checks.
Example (blocking): "We couldn't recognise this address. Please check the street name and postal code."
Read more⌄
How these messages interact with booking rules
Messages are shown after all core rules are evaluated. They don't configure the rules — just how the outcome is communicated. If customers frequently see "no times available", check the underlying settings:
- Booking form Times settings (duration, rolling dates, intervals)
- Resource available hours and special dates
- Transit limits under Location & transport
- Public holidays and closure dates
Available placeholders in messages
%booking_location%— the address the customer entered%booking_postal_city%— the postal code/city used in routing
To see all available placeholders: open any message field → press Ctrl/Cmd+K → search for "booking".
Best practices
- Keep messages short: one line explaining what went wrong, one line on what to do next
- Avoid technical terms — use "service area", "driving distance" instead
- Always offer a fallback: phone number, email, or contact form
- Test each scenario on the public URL before going live
- Messages are per form — adapt wording for different services or regions
Common searches
booking error message • no available times message • postal code blocked message • form messages • %booking_location% • address too far message
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article