From booking to capture, in four moving parts.
On the Calendly no-show event, we capture the hold up to your policy amount. On attendance or in-policy cancellation, we void it. The customer's card is never charged twice.
Hold the card. Capture only on no-show.
When your client books, we create a Stripe PaymentIntent with capture_method set to manual and the amount you've configured per event type. Stripe places a refundable authorization on the card — the customer sees a temporary pending hold on their statement.
If the client shows up or cancels inside your grace window, the authorization voids automatically. Nothing is captured, and the hold drops off the customer's statement within a few business days.
If the Calendly no-show event fires, we capture up to your policy amount. The funds settle directly into your Stripe balance via Stripe Connect Standard — NoShowSaver never holds the money.
Four touchpoints. Every one is editable.
Booking confirmation goes out the moment the hold lands, with your cancellation policy text and the dollar amount in plain English.
T-24h reminder includes a one-tap reschedule link that's valid until T-2h. T-2h is the gentle 'you're up next' nudge.
T+15min after a no-show capture, the client gets a clear notice that the fee was charged, with a link to the dispute page if they believe it's a mistake.
Every template is per-event-type configurable. Toggle off any touchpoint, rewrite the copy, or override the policy amount — your event type, your call.
- T-0Booking confirmationHi Maya — confirming Tue 3pm. Cancellation policy: $200 charge inside 24h.
- T-24hReminder + rescheduleTomorrow 3pm. Reschedule any time before 1pm: ns.app/r/abc
- T-2hYou're up nextToday at 3pm. Looking forward to it.
- T+15minNo-show captureWe missed you today. A $200 hold has been captured per the policy.
The client always has an out.
The reschedule link is signed and no-login, valid until T-2h. Clicking it deep-links into Calendly's native reschedule flow, which we already trust to handle availability and time-zones.
Once the new booking lands, the original authorization voids and a fresh hold is placed for the new appointment. The customer's card is never authorized twice for the same booking.
If the link is unused and the client doesn't make it, the original hold flows through to the no-show capture — no manual cleanup, no orphaned holds.
- Deep-links into Calendly's native reschedule page
- Voids the original hold the moment a new slot is picked
- Fresh hold attaches to the new booking automatically
Defensible if challenged. Quietly.
Every no-show charge ships with a signed "I was there" link. The customer can submit their version of events with one form.
If they file a Stripe dispute instead, we automatically bundle their submission, the Calendly attendance log, the SMS history, and a timestamped policy snapshot into a Stripe dispute response.
You don't have to remember to log into Stripe and respond. The bundle is uploaded inside the response window and we'll notify you of the outcome.
- EVIDENCEClient's "I was there" submission
- LOGCalendly attendance log
- HISTORYFour-touch SMS delivery log
- POLICYTimestamped cancellation policy snapshot
Five-minute setup. No migration.
Connect Calendly, connect Stripe, set your fee. The next booking on every connected event type is held automatically.