How do I send a unique door access code by SMS or email after a sauna booking is paid?
Unique door access codes after payment are a partner lock plus messaging job, not a native Zettlor smart-lock product.
After Stripe marks the sauna or cold plunge booking paid, a unique door code should reach the guest by SMS or email so an unmanned entry can open only for that reservation. Zettlor does not ship a native smart-lock door-code product that mints {access_code} tags into SMS after pay—Use partner lock hardware plus messaging or Platform / API automation after the paid booking exists.
What Zettlor does today
Door access codes after pay are not native in Zettlor. What is live: Stripe checkout on the operator’s own account, automated guest SMS and email for booking confirmations and reminders (operator-customizable content and timing), QR-oriented check-in patterns on the desk side, and an operator API / Platform custom-integration path for connecting other systems. What is not in product: a Store menu for smart-lock connectors, heater control, or RFID gates. Unmanned PIN delivery is a partner lock + post-Stripe message job, not a built-in Zettlor door SMS feature.
Guest booking, cancel, and credit self-serve steps stay on Help. This page is for operators.
Desk path
No native Door codes or Smart lock settings path in Zettlor. Use: paid booking confirmation (SMS/email templates for confirmations and reminders); Stripe as the payment source of truth; operator API credentials in the dashboard (contact [email protected] for docs) or Platform custom integration when a named lock partner must mint and send a code after payment_succeeded. Partner lock admin (Igloo-class, building SMS/email templates with {access_code} / time tags) lives in the lock vendor, not in Zettlor Store.
Do not invent a settings path beyond what is listed here. If the product does not include a control, the desk workaround is the path.
Failure mode
Operators paste a static building code into every confirmation template. One cancelled guest still opens the door all week. Others assume Zettlor “has door SMS like Gibbs” and stall launch hunting for a lock connector that is not shipped. The failure is treating confirmation SMS as a unique, time-bound credential when no partner lock is minting per-booking codes after Stripe.
Operator example
A Bad Sauna-style riverside barrel runs evenings without a front desk. Guests book sauna and cold plunge on Zettlor and pay on Stripe. On payment success, a Platform or partner automation asks the lock vendor to mint a one-booking PIN, then the lock vendor (or the automation) SMS/emails that PIN with the booked start window. Zettlor remains the booking and payment system of record; the lock partner remains the code authority. Staff still see the paid roster on the shift view for exceptions.
A sauna and cold plunge operator can copy the shape of this example without copying another brand's private pricing or customer lists.
How to do this
- Confirm you need unique, time-bound codes—not a shared static PIN in the confirmation email.
- Keep booking and Stripe payment in Zettlor; do not move checkout into the lock vendor unless you accept a split system of record.
- Choose a lock partner that can mint per-booking codes and send SMS/email (or accept codes from your automation).
- Wire payment-success → mint code using Platform custom integration or the operator API; do not assume a one-click Zettlor lock connector exists.
- Put only non-secret arrival instructions in Zettlor’s native confirmation/reminder templates until the partner message carries the real code.
- Test: pay a booking, receive a unique code, cancel or expire the booking, and confirm the code no longer opens.
- Train desk staff on the exception path (walk-in, failed SMS, lost phone) without publishing a master override code on social posts.
Related questions
Can I put the door code in Zettlor’s native confirmation SMS?
You can put text in confirmation and reminder templates, but Zettlor does not mint unique lock PINs. A static code in every confirmation is not a per-booking credential. Unique codes belong to the partner lock or the automation that listens after Stripe.
Is this the same as hiding a private event behind an access code?
No. A booking-page access code that hides a private event SKU is a discovery control. A door PIN that opens hardware after pay is an entry control. Different jobs.
Does QR check-in replace a door code?
QR or roster check-in helps a staffed door. Unmanned hardware still needs a lock partner or on-site staff.
Follow-up guides
- How do I set early-entry and late-exit buffer on a door code around the booked sauna time?
- How do I add a turnaround buffer between private sauna or cold plunge sessions?
- How do private hire and shared drop-in share the same sauna slot without double-booking?
- Can operators customize the notifications Zettlor sends to guests?
- Does Zettlor have an API?
Book a demo or get started.
- How do I set early-entry and late-exit buffer on a door code around the booked sauna time?
- How do I add a turnaround buffer between private sauna or cold plunge sessions?
- How do private hire and shared drop-in share the same sauna slot without double-booking?
- Can operators customize the notifications Zettlor sends to guests?
- Does Zettlor have an API?
Zettlor is booking and operations software for commercial sauna, cold plunge, and wellness facilities. See how it works.