Booking pages that feed your CRM
Every confirmed meeting becomes a contact and a calendar event in the same workspace.
Scheduling for people who remember people
Let people book time with you, capture the context before they arrive, and keep every meeting attached to the relationship it belongs to.
Every confirmed meeting becomes a contact and a calendar event in the same workspace.
Ask the right questions while people book, then carry their answers into follow-up.
| Capability | Connections | Standalone scheduler |
|---|---|---|
| Scheduling links | Yes | Yes |
| Reminder email before each booking | Yes | Yes |
| Clients pay when they book | Yes | Yes |
| Contact profile from every booking | Yes | Limited |
| Event and community history | Yes | No |
| Follow-up timeline | Yes | No |
| Public events, forms, and share cards | Yes | No |
Connections offers scheduling links like Calendly, but every confirmed booking also creates a contact profile, attaches your event and community history, and starts a follow-up timeline. A standalone scheduler stops at the booked time slot.
Yes. You can ask the right questions while people book, and their answers carry into your follow-up, so you arrive at the call with context instead of just a time slot.
Connections records who booked, where they came from, what they asked for, and what happened next, so meetings don't become disconnected calendar entries.
Yes. Every confirmed meeting becomes a contact and a calendar event in the same workspace, so your CRM builds itself as people book time with you.
Yes. Give a booking type a price and clients pay by card when they book. The money goes to your own Stripe account, which you connect once, and Connections takes three percent on top of Stripe's own fee. To take a deposit, set the price to the deposit.
Yes. Your booking page is free, and so is the account behind it. When clients pay as they book, Connections takes three percent on top of Stripe's own fee. Free sends up to 100 emails a week; paid plans raise that.