Notifications
ReservKit sends standard customer messages for the booking workflow. Your business identity controls what customers recognize, while ReservKit manages the delivery plumbing by default.
Business identity comes first
Set your business name, business email, phone number, and Google Review Link in Settings. Customer-facing messages use your business name, and customer replies to booking emails use your business email when available.
Customers should not need to know whether a message was delivered by ReservKit, Resend, Twilio, Supabase, or another internal service. They should see a clear booking message from the business they booked with.
Messages ReservKit can send
Booking confirmations
Sent after payment succeeds or an operator-confirmed booking is created, when confirmation emails are enabled.
Booking reminders
Sent before the activity when reminders are enabled. Reminder emails and SMS can include waiver hub links when waivers are required.
Cancellation and modification emails
Sent when a booking is cancelled or changed, so customers have the updated booking context.
Google review requests
Sent after a completed booking only when review requests are enabled and a Google Review Link is configured.
Abandoned booking recovery
Sent only for recoverable unpaid pending bookings when the recovery job finds an eligible hold.
Booking-link recovery
Sent only after a customer asks for help finding a booking. The browser response stays generic so customer records are not exposed.
Email delivery
Standard booking emails can use ReservKit-managed email delivery. You do not need a Resend account to start sending booking confirmations, reminders, cancellation emails, or customer booking-link recovery messages.
If you want customer emails sent from your own verified domain, Settings includes optional Custom Email setup for Resend. That is an advanced sender-domain option, not a launch requirement.
Custom Resend setup requires both a Resend API key and a verified From Email. Leave both fields blank when you want to keep using ReservKit-managed email delivery.
SMS reminders and broadcasts
Automated SMS reminders and broadcast SMS can use ReservKit-managed delivery when platform SMS is configured. Operators can also connect their own Twilio account if they want messages from their own number or stronger SMS control.
Broadcast SMS depends on verified SMS readiness before sending. If SMS is important to your launch, test it during onboarding before relying on it for customer operations.
Custom Twilio setup requires Account SID, Auth Token, and From Number together. Leave all three fields blank when you want to keep using ReservKit-managed SMS reminders and broadcasts.
What is not editable yet
ReservKit does not currently include a full operator-facing email or SMS template editor. The current controls cover notification toggles, business identity, Google review links, and optional custom provider credentials.
Settings also includes a read-only delivery log for recent notification events. It shows safe delivery facts like message type, channel, trigger, status, provider label, failure code when present, and timestamp without exposing customer email addresses, phone numbers, message bodies, recovery links, OTPs, or provider secrets.
Test emails from Settings go only to the signed-in operator. The SMS reminder test sends only to the saved business phone. Review-request tests require a saved Google Review Link, and SMS reminder tests require a saved business phone before the test-send controls become available. Test messages do not message customers, run reminder jobs, or accept arbitrary recipients.