NoShowSaver
FAQ

Answers from someone who's held a card before.

The buyer's questions before connecting, and the client's questions after a charge. Both matter.

Money & holds

Is the customer charged at booking?
No. We place a refundable authorization on the card. The customer sees a temporary pending hold on their statement that drops off if they show up or cancel inside policy. They are charged only on a confirmed no-show, up to your stated fee.
Where does the money go?
Direct to your Stripe account via Stripe Connect Standard. NoShowSaver never holds your funds — Stripe pays you out on your normal schedule.
How long is the hold valid for?
Stripe authorizations are valid for 7 days. That means bookings must occur within 7 days of the appointment in v1; longer leads need a re-authorization step (planned for v1.1).
Can the customer dispute a no-show charge?
Yes — and we make it easy for them to. Every no-show charge includes a "I was there" link. If a dispute is filed, we auto-bundle the client message and Calendly attendance log into a Stripe dispute response.

Setup

Do I need to migrate off Calendly?
No. NoShowSaver lives next to Calendly. You keep your existing share-links, event types, and calendar integrations. We listen for the Calendly webhook events and act on them.
How is this different from Calendly's 'Connect a payment processor' option?
Calendly's payment-processor option charges the client's card at booking — full price collected upfront via Stripe. It's a prepaid-session flow, not a no-show fee. There's no card-on-file mechanism, no post-event capture, and Calendly explicitly says enforcement of cancellation policies isn't managed on their side. NoShowSaver doesn't charge at booking. We place a refundable hold on the card and only capture if the Calendly no-show event fires — the client sees nothing on their statement if they show up.
Do I need a separate Stripe account?
If you already use Stripe (most service businesses do), connect it via OAuth in two clicks. If you don't, you'll create one through the connect flow — Stripe handles the KYC.
How long does setup actually take?
Five minutes for the OAuth steps, plus a few minutes per event type to confirm the policy fee, cancellation window, and SMS copy.
Does my client need an account?
No login. Reschedule and dispute pages are signed-link, no-account experiences. The only thing the client interacts with is the booking page they already use.

Cancellations

What about a client who cancels the day before?
You set the grace period per event type — default is T-24h. Cancellations inside the grace window void the hold automatically. Cancellations after the grace window can capture the fee, your call.
What if a client reschedules at the last minute?
If they use the reschedule link before T-2h, the hold voids and the new booking gets a fresh hold. If they don't, the original hold flows through to the no-show capture.

Reminders

How are clients reminded about their appointment?
Every booking gets a branded confirmation email with a calendar invite attached. The invite carries native reminder alarms at T-24h and T-2h — the client's own Apple/Google Calendar fires the push, in every country, with no carrier involved. On top of that, SMS reminders fire in UK, Germany, France, Netherlands, Sweden, Japan, and Australia today, with US, Canada, and Singapore on the near-term roadmap.
What if my client is in a country where SMS isn't supported yet?
They receive the branded confirmation email and the calendar invite with built-in alarms at T-24h and T-2h, just like every other booking. The reminder still fires on their phone via their native calendar app — it just comes from Apple/Google Calendar instead of a text message. We're expanding carrier coverage and will turn on SMS for additional regions as registration completes.
Are SMS reminders included in the price?
Solo opts in per-message; Pro and Agency include an SMS pool. You can disable any of the four touchpoints per event type, or rewrite the copy entirely. Email + calendar reminders are included on every plan, in every country, with no cap.

Compliance

Is NoShowSaver HIPAA-compliant?
No. We do not sign BAAs and we're not a HIPAA-covered service. Therapy practices handling protected health information should not use NoShowSaver until we offer a covered tier.
Where is data stored?
Postgres in the US. We store booking metadata and the Stripe PaymentIntent ID. We do not store full card numbers — Stripe holds the card.

Pricing

Is there a transaction fee on captured no-show charges?
Not on Solo, Pro, or Agency. A 2% transaction-tier option is available for high-volume operators who'd rather pay per capture than a flat monthly.
What happens if I exceed my plan's booking cap?
We'll notify you and ask you to upgrade. We don't auto-upgrade you to a higher tier without consent — you get a soft banner and a button.

Still have a question?

Email support@noshowsaver.app and a human will reply within a business day. Or just connect Calendly and click around the dashboard for a few minutes.