Loading tutorials…
Loading tutorials…
Charging for consultations, coaching, or expert sessions cuts no-show rate to under 5%. But the setup has subtle traps — tax handling, refunds, and the booking flow each have decisions that affect conversion. Here's the right setup.
Who this is forConsultants, coaches, and expert services who want to charge for time at booking. Also: SaaS teams that offer paid onboarding sessions or paid technical deep-dives. Not relevant for free demos.
What you'll need
Step 1
Paid bookings reframe the meeting from 'demo' to 'consultation.' Price it like the value you deliver, not the cost of your time.
Most paid Calendly bookings are in the $50-500 range. Below $50, transaction fees eat the value and the price doesn't deter no-shows. Above $500, the booking flow needs more reassurance (testimonials, scope clarity) than Calendly natively provides.
Sweet spot: $97-297 for an expert consultation. High enough to deter tire-kickers, low enough to convert without heavy sales motion.
Decide what's INCLUDED in the price: the call itself + recording + 1 follow-up email? Or just the call? Clarity here prevents refund disputes.
Decide what's EXCLUDED: ongoing support, written deliverables, calls beyond the booked duration. Spell it out on the booking page.
Step 2
In Calendly → Integrations → Stripe → Connect. Authorize with the Stripe account that will receive payouts. Test with Stripe test mode first.
In Calendly → Account → Integrations → Stripe → Connect.
Authorize with your Stripe account. You'll be redirected to Stripe to confirm — this creates a Stripe Connect link, meaning Calendly is authorized to charge cards on your behalf and route funds to your Stripe account.
If your Stripe account is not yet verified (business details, bank account, identity), complete that first in Stripe Dashboard → Settings → Business → Verification. Unverified Stripe accounts can take payments but can't pay out.
Use Stripe Test Mode for initial setup: in Stripe, switch to test mode, run test bookings with test card numbers (4242 4242 4242 4242). Verify everything works before flipping to live mode.
Step 3
Each event type can have a different price. Set in event type → Payments → Enable payment collection → enter amount + currency.
In Calendly → Event Types → [your event] → Payments.
Toggle "Enable payment collection" ON. Pick "Stripe" as the processor.
Enter the amount and currency. Stripe supports 135+ currencies but transactions outside your primary currency incur conversion fees (~1-2%).
Decide payment timing: "Charge at booking" (standard) or "Authorize at booking, capture later" (less common, requires Stripe Capture API). For 95% of paid bookings, charge at booking.
Save. The booking page now shows the price prominently before slot selection.
Step 4
If you're selling globally, tax compliance is real. Stripe Tax handles automated calculation for $0.50/transaction. For US-only, simpler options exist.
Decide your tax stance: (a) Tax-inclusive pricing (the $97 includes any taxes you owe), (b) Tax-exclusive (you charge the customer additional tax on top), (c) Tax-handled-externally (you manually reconcile and remit later).
For consultants in the US selling primarily to US clients: tax-inclusive at $97 is the simplest path. You handle quarterly estimated taxes via your accountant.
For international or EU sales: VAT/GST rules require collecting tax based on buyer location. Enable Stripe Tax ($0.50/transaction) for automated handling — it determines the right tax rate based on buyer's country.
For paid bookings >$500 or to corporate buyers: you may need to issue tax-compliant invoices. Stripe Invoicing handles this automatically.
Talk to an accountant before launching. Tax mistakes in your first year are expensive and embarrassing.
Step 5
No policy = chargeback risk. Common pattern: full refund for cancellations >24 hrs in advance, no refund for <24 hr cancellations or no-shows.
Decide: (a) When is a refund available? (b) Who initiates — auto-refund on cancel, or manual review? (c) Refund destination — back to original card, or store credit?
Standard policy for paid consultations: "Full refund for cancellations made at least 24 hours in advance. No refund for cancellations <24 hours or no-shows."
Some consultants offer reschedule-once free, refund-on-second-cancel. This is friendlier and rarely abused.
Display the policy prominently on the booking page (use Event Description) AND in the confirmation email. Don't hide it.
For chargebacks: Stripe will side with the customer if you don't have a documented policy displayed before payment. The Event Description is your first line of defense.
Step 6
Confirmation email is now a transactional + sales asset. Restate what they paid for, what they get, and how to reschedule. Drops refund disputes 50%.
In Calendly → Workflows, customize the confirmation email for paid event types.
Body should include: (1) Order receipt (amount paid, what for), (2) What's included (call + recording + follow-up email, etc.), (3) Refund policy summary with link to full terms, (4) Reschedule link, (5) Direct contact for issues, (6) Pre-call prep (what to bring, what to think about).
This email is now a contract. Clear, specific, and warm. Generic confirmation = refund risk.
Send a receipt PDF via Stripe automatically: in Stripe → Settings → Emails → Customer emails → enable "Email customers for successful payments."
Step 7
Book + pay using a Stripe test card. Verify Calendly Event creates, Stripe payment succeeds, confirmation email arrives, and refund flow works.
In Stripe → Developers → switch to Test Mode.
From an incognito browser, book your paid event. Use Stripe test card 4242 4242 4242 4242, any future expiry, any 3-digit CVC.
Verify: (1) Calendly Event created on your calendar, (2) Stripe Test Mode shows the test charge, (3) Confirmation email arrived with receipt, (4) Pre-event reminders fire as expected.
Test a refund: in Stripe Test Mode, refund the test charge. Verify it processes and the customer would get an email.
Test a cancellation: from the booking, click cancel. Verify Calendly cancels the event AND that you can decide whether to refund from Stripe.
Once all flows pass, switch Stripe to Live Mode and run ONE real $0.50 transaction with your own card to verify live mode works. Then refund it.
Step 8
Once live, measure: booking-page views → paid bookings → completed sessions → refunds. The bottleneck reveals where to focus.
Track: page views (from analytics), bookings (from Calendly), payments (from Stripe), completions (from Calendly), refunds (from Stripe).
Typical funnel: 100 page views → 8-15 paid bookings (8-15% conversion) → 95%+ show rate → 2-5% refund rate.
If page views → bookings is below 5%, your pricing is too high OR your value proposition on the booking page isn't clear. Test copy or a slight price decrease.
If show rate is below 90% on paid bookings, something is unusual — investigate (often it's a confused customer who thought they were booking a free intro).
If refund rate is above 10%, your scope is unclear and customers feel misled. Tighten what's included vs. excluded.
Common mistakes
Charging below $50
What goes wrong: Stripe takes ~$1.50 ($0.30 + 2.9%) on a $40 transaction. You net $38.50 from a transaction. Below this, paid bookings don't move the needle on no-show rate either (people don't value the booking enough).
How to avoid: Price at $97+ minimum. If you genuinely want $50 sessions, batch them as a package ($147 for 3 sessions).
No refund policy displayed
What goes wrong: Customer cancels 2 hours before, demands a refund. You refuse. They chargeback via their bank. Stripe sides with the customer because no policy was displayed. You lose the money + a $15 chargeback fee.
How to avoid: Display refund policy on the booking page Event Description AND in the confirmation email. Stripe sides with you when policy is clear.
Tax-inclusive pricing on international sales
What goes wrong: You charge $97 to a UK customer. They expect VAT included. You owe HMRC the 20% VAT. Your effective revenue is $77 — you priced for $97 but netted $77.
How to avoid: Enable Stripe Tax for international sales — it calculates and adds the tax for the buyer's region. Your $97 stays $97 to you; the customer pays $97 + VAT.
Refunding by canceling the Calendly event
What goes wrong: You cancel the Calendly event thinking it triggers a refund. Stripe charge remains. Customer has no meeting AND no refund. Angry customer + chargeback risk.
How to avoid: Refunds happen in Stripe Dashboard, not by canceling Calendly. Cancel Calendly first (releases the slot), then issue refund in Stripe.
Same event type for free intro AND paid consultation
What goes wrong: Some prospects expect the call to be free (free intro), some are charged (paid consultation). Confusion, refund requests, support burden.
How to avoid: Separate event types: "/intro-call" (free) and "/strategy-session" (paid). Different URLs, different expectations.
No pre-session prep email
What goes wrong: Customer pays $197 and shows up cold. They don't know what to bring or think about. Session is 30% as valuable as it could be. They feel they overpaid.
How to avoid: Add a 24-hr-before email via Workflows that asks 2-3 prep questions. Customer comes prepared. Session feels worth the price.
Launching without Test Mode
What goes wrong: You skip Stripe Test Mode and go straight to live. First customer hits a bug in your config — charged but Calendly didn't book. They demand refund + apology. You scramble.
How to avoid: Always test with Stripe Test Mode first. Run 5-10 test bookings + 2 test refunds. Switch to live only after all flows pass.
Recap
Done — what's next
How to set up Calendly Workflows (confirmations, reminders, follow-ups)
Read the next tutorial
Hand it off
Paid bookings drop no-show rate to under 5% — but the setup (especially policies + tax) needs real thought. EverestX demand-gen specialists set up paid booking flows + write the refund policy + connect Stripe + test end-to-end for $300-600 one-time, or as part of an ongoing $400-800/mo engagement.
See specialist rates
Dramatically. Free demo no-show rate is 20-30%. Paid booking no-show rate is typically 3-5%. The act of paying creates commitment — customers don't no-show on something they paid for. This is the single most reliable no-show fix, but it only works if you can credibly charge for the meeting.
$97-297 hits the sweet spot for most expert consultations. Below $50, fees eat the margin AND the price isn't high enough to deter no-shows. Above $500, the booking flow needs more reassurance than Calendly natively provides — better to use a sales call to close those manually.
Full price is simpler and more standard. Deposits add complexity (capture vs. authorize, partial refunds) without much benefit. The exception: if you're booking a multi-day workshop ($2K+), a 25-50% deposit reduces customer commitment risk while keeping cash flow.
When enabled, Stripe Tax calculates the correct tax rate based on the buyer's location at checkout and adds it on top of your base price. You see two line items on each transaction: base + tax. Stripe remits tax to relevant jurisdictions for you (in supported regions). Costs $0.50/transaction. For any team selling internationally, worth it.
Yes — Stripe Dashboard supports partial refunds. Set the partial amount in Stripe, then send the customer a manual email explaining. Calendly itself doesn't track partial refunds — you'll log them in your CRM if needed.
Calendly
A well-built Workflow sequence drops no-show rate by 10-15 percentage points and lifts demo-to-opportunity conversion by ~20%. Most teams build one confirmation email and call it done. Here's the full sequence specialists actually deploy.
Calendly
Calendly has four event types and most teams misuse three of them. This walks through what each one is actually for, the configuration that matters, and the routing logic that turns event types into a real demo-booking engine.
Calendly
Healthy no-show rate for B2B demos is 15-20%. If yours is 30%+, you're leaking 1 in 3 booked demos. This walks through the diagnostic sequence specialists use — most cases are fixable in under a week.
Calendly
DIY Calendly is fine when you're a solo founder. The moment you have multiple reps, routing logic, or a CRM that needs to stay clean, you're past the DIY ceiling. Here's the honest framework for when to make the call.