The right message.
At the right point in a booking.
Keep customers informed from booking acknowledgement and deposit requests through pre-session reminders and follow-up, in the language of their booking.
Customer communication continues after a reservation arrives. Messages distinguish an accepted request from a confirmed session and follow changes in payment status. With a supported delivery connection, the system records delivery separately from provider acceptance. Studio notifications use your own configured email account.
01
Connect your sender
Configure email delivery, the sender address and studio notification recipient.
02
Follow the booking lifecycle
Messages follow acknowledgement, payment, the day before a session and completion.
03
Review delivery
Review booking history and handle bounces or cases that need staff attention.
01
Explain what happens next.
Match each message to the booking state and the next action needed.
Notify the studio of contact enquiries while retaining the enquiry record even if sending fails.
QUESTIONS, ANSWERED.
A few things
to know before you start.
Do account emails and studio booking emails share a sender?
Tsumira Foto sends platform verification emails. Customer booking emails require the studio’s own sending account and sender settings, which onboarding support can help configure.
What happens if the payment email bounces?
With Brevo delivery tracking configured, a bounce is recorded against the booking. Provider acceptance is not treated as confirmed delivery, so staff can review failed or uncertain cases.
Is every email guaranteed to arrive?
Recipient settings and provider decisions can prevent delivery. Use sending and delivery history to identify issues and contact the customer another way when necessary. Provider costs are separate.
