Black Friday
Skip to documentation content

Hotel Setup

Configure the hotel’s contact form

Free includes a contact-enquiry workflow with stored messages and hotel notifications. It operates without Pro, WooCommerce or a paid theme. An enquiry is not a room reservation or a payment, and a received message does not prove email delivery.

Free includes a contact-enquiry workflow with stored messages and hotel notifications. It operates without Pro, WooCommerce or a paid theme. An enquiry is not a room reservation or a payment, and a received message does not prove email delivery.

Save the intake configuration

  1. Open Hotel Booking → Newsletter & Contact with communication-settings permission.
  2. Enter one valid Notification recipient, the customer-facing Privacy notice, and a valid Privacy Policy URL for the hotel.
  3. Enable Accept contact messages and save. Review the Contact readiness status.
  4. Check the configured Contact Page, its publication/access state and its actual permalink. The native form shortcode is [kimorapro_hb_contact].

Both communication intakes start disabled. The suggested WordPress administrator address and Privacy Policy URL are suggestions, not automatically saved settings. Contact remains unavailable when its feature/schema, saved configuration or intake state is not ready. Its shortcode can therefore produce no form until those conditions are satisfied.

Assigning a Page does not overwrite arbitrary content or publish a private Page. An untouched installer-created Contact draft has a separate guarded initial-publication workflow; user-edited/adopted Pages remain under the owner’s control. See managed Pages.

Test the guest experience

Use a synthetic address and mail sink first. Open the public form and check its name, email, optional subject, message and privacy information. A blank subject becomes General enquiry. Current limits are 120 characters for name, 200 for subject and 5,000 for message; do not enter payment-card or sensitive personal data.

Submit once and check both the public result and the stored Contact message. A receipt acknowledges intake, not a delivered notification or a promised response time. The same valid submission replay must not create another identical message; reusing its submission identity with different data is a conflict and requires a fresh form.

Handle failures and retention

Review validation, expired-form, throttled and unavailable states before resubmitting. Do not automatically retry an uncertain network response or disable abuse controls. Open a fresh form when its security context expired.

Authorized staff can manage Contact messages and use supported notification actions; this does not grant communication-settings or newsletter-export privileges. Check actual transport independently before claiming inbox delivery. Configure Contact retention separately from booking data, and remember that deleting a local message cannot recall a notification already handed to an external mail system.

See communication data and retention.

Was this article helpful?

Your feedback helps us improve the documentation.