1 min read
MyBookaro sends transactional emails for every booking event. Templates are configurable, and individual templates can be disabled.
Templates shipped (Lite) #
new_booking— sent on booking submission.approved— sent on provider approval.rejected— sent on provider rejection.cancelled— sent on cancellation (customer or provider).rescheduled— sent on reschedule.reminder_24h— queued at approve time, fires 24 h before booking start.reminder_1h— queued at approve time, fires 1 h before.review_invite— queued at completion.
Templates added by Pro #
chat_message— new chat message notification.profile_reminder— incomplete custom profile form reminder.
Configure #
WP Admin → MyBookaro → Settings → Notifications. Per-template:
- Enable / disable.
- Recipient (customer / provider / both / custom address).
- Subject line.
- Body (HTML, with placeholders).
Placeholders #
{customer_name}, {provider_name}, {service_name}, {booking_date}, {booking_time}, {booking_url}, {site_name}.
Reminder behavior #
Reminders are queued only when a booking moves to Approved. Already-past reminder times don’t send. Cancelling a booking flushes pending reminders.
Notification log #
Every send attempt is logged in {prefix}bookaro_notification_logs. View under MyBookaro → Logs → Notification Log. Failed sends include the error message.
Email deliverability #
Use a transactional email plugin (WP Mail SMTP, Post SMTP, etc.) on production. WordPress’s default wp_mail() works for testing but is unreliable for transactional volume.
