Peak Booking / Customer check-ins
The customer is happy.Keeping it that way takes conversations.
A check-in only works if it's easy to find and easy to move. With Peak Booking your customer gets their own booking page with the right length and one short question. They pick the time, get a confirmation with the agenda and can reschedule through their personal link.
Put the goal into words. Add perspectives and timing right below.
Plan a sample check-in. Nothing gets booked.
Check-in / length / preparation
What a good check-in needs.
- The topic
- What is it about this time?
- The guest
- Who speaks for the customer?
- The preparation
- What's on the table before the call?
Your small check-in
From three answers to a call with a purpose.
Fill in the example with a made-up customer. You see how topic, guest and preparation fit together. Everything stays in this preview.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three questions. A check-in worth having.
Draft · not yet put together
- The topic
- Still open
- The guest
- Still open
- The preparation
- Still open
From the invitation to the conversation
Short, regular, prepared.
The order keeps the check-in small: one page, one question, one note afterwards.
- 01Case
The page is set up.
The topicWhat is it about this time?
You create a booking page for known customers: fixed length, buffer before and after, lead time and one question about the topic. Peak Booking reads free times from your Google Calendar.
Flow type → known contact - 02Action
The customer books on their own.
The guestWho speaks for the customer?
They see times in their time zone, pick one and get a confirmation, calendar link and .ics. If it no longer fits, they move the same booking through their link.
Confirmation → agenda and reschedule link - 03Result
The conversation is on record.
The preparationWhat's on the table before the call?
The booking is an event on the contact in Peak One. After the call you record whether it took place. In the example you get a check-in note.
Sample artifact → check-in note
The next proof is the product
Create your first check-in page.
In Peak Booking you connect Google Calendar, set length and buffer and share the link with your customer. A known customer is matched to their existing contact, not created twice.
Start Peak BookingPeak Booking / Your next step
A customer you talk to regularly.
Try the example with the customer you haven't heard from the longest.
Open the check-in example
Talk briefly before things get tight.
What's on the table before the call?
Frequently asked questions
Can a customer move their check-in on their own?
Yes. Through the personal link in the confirmation they reschedule or cancel. The same booking moves, no new one is created.
Are there recurring series?
No, recurring series are not available today. The customer books each check-in separately through the same page.
Is the customer created twice as a contact?
No. A known guest is matched to their existing contact in Peak One.
Does Peak Booking send reminders before the call?
Automatic reminders are planned. Today the guest gets a confirmation with a calendar link and .ics.