Notifications & SMTP (Booking)

Tiger Booking keeps customers and staff informed with branded email notifications across the whole booking lifecycle, and lets you send them reliably over your own SMTP server.

Where: WP Admin → Tiger Booking → Settings → Notifications.

Lifecycle emails

Notifications are grouped per active module, split into customer emails and admin alerts. For appointments the customer set includes Booking Confirmation, Booking Reminders, Cancellation Confirmation, Payment Receipt, Post-Booking Follow-up and Review Request; admins can be alerted on New Booking, Cancellation, Payment Received and New Review. The Hotels module adds its own equivalents (reservation confirmation, check-in reminder, check-out confirmation, room change/upgrade, plus daily check-in/check-out digests for admins).

Switch each email on or off independently, so you send only what your business needs.

Editing a template

Open any notification to edit its content. Each template offers three tabs:

• Plain Text — a simple text version.
• HTML — the full branded HTML body, with merge tags such as {{clientName}}.
• Preview — a live render so you can check it before saving.

You can also set the subject line and, for admin alerts, choose whether they go to the Default Admin Email or a Custom Email address.

Mail delivery (SMTP)

The Email Delivery card controls how every notification is actually sent. Pick a provider:

• System Default — your server’s built-in PHP mail. Fine for testing, but often lands in spam.
• SMTP — send through a real mailbox or a service such as Gmail, SendGrid, Mailgun or SES for reliable delivery.

For both, set the From Name and From Email (use an address on your own domain for the best deliverability). Choosing SMTP reveals the connection fields:

1. SMTP Host — e.g. smtp.gmail.com.
2. Port — usually 587 for TLS or 465 for SSL.
3. Encryption — TLS, SSL or None.
4. Username — usually your full email address.
5. Password — for Gmail or Outlook use an app password. It is stored server-side and never sent to the browser.

Send a test

Use Send test to email yourself and confirm the connection works. Save your changes first so the server uses the latest settings; if delivery fails, the test reports the exact host/port/encryption or credential error to fix. A send log and stats let you monitor real deliveries afterward.

Troubleshooting

Emails aren’t arriving.

Switch delivery to SMTP rather than System Default, use a From Email on your own domain, and run Send test — the error message points straight at the misconfigured field.

Reminders and follow-ups don’t fire.

Time-based emails depend on WordPress cron. On low-traffic sites, set up a real system cron so scheduled sends go out on time.