Booking

Booking puts “grab time with me” on every member card and gives the org one place to run scheduling.

Watch: The meeting books itself (0:52)

Setup

Per card: availability rules (weekly hours, exceptions, buffers), bookable services (duration, location/virtual, description), and email templates for confirmations and reminders.

The booking flow

Visitors pick a service and a slot on the card’s booking page. Depending on configuration, bookings confirm instantly or land as requests for a manager to approve. The requests queue lives on Organization → Booking → Requests, with a pending-count badge.

Attendance & no-shows

Appointments track attendance; marking a no-show can trigger an automation rule (e.g. a “sorry we missed you” follow-up, see Automation).

Proposing times

Instead of waiting for someone to pick a slot, offer two or three and let them choose. Reps can propose from a lead’s detail panel, and from their own Dashboard → Bookings for anyone outside the pipeline.

Times are chosen from the card’s real availability, so a slot that is already taken (or blocked by a connected calendar) is never offered. Each offered time is held until the recipient answers; the one they pick is confirmed and the rest are released. Recipients can counter with a different time, which the proposer accepts or declines.

Offers expire after seven days and can be withdrawn at any point.

What the booking form asks for

Per card, under Settings → What you ask for. Name is always required. Email is required by default: it carries the confirmation, the reminders, the calendar invite and the reschedule link. Phone is optional by default.

Either can be made optional, but never both. A booking with no way to reach the customer has nowhere to send any of the above.

Note to attendee

Owner-written, customer-delivered: it appears in the confirmation, in every reminder, and in the calendar invite. Set a default per card, override it per service (an intro call’s video link, a site visit’s address), or write a one-off on a single booking. The most specific one wins.

Distinct from a booking’s private note, which is internal and is never sent. Custom email templates can place it themselves with {{booking.note}}; if they do, it is not also appended.

Connected calendars

Google or Microsoft, per user, under Settings → Connected calendars. Times already busy on a connected calendar stop being bookable. Preview busy times shows which windows are being blocked over the next week. Start and end only, never titles or attendees.

Coverage differs by provider: Microsoft reads every calendar on the account, including secondary and subscribed ones; Google reads the primary calendar only.

If a connection’s access is revoked, the owner is emailed and notified in their inbox. A calendar that cannot be read is indistinguishable from a free one, so it is never treated as silent success. The busy check can also be turned off per card.

AI meeting briefs

For a confirmed booking linked to a lead, Lynqu writes a meeting brief the day before: who they are and where the deal stands, what they engaged with, open tasks, and talking points for the conversation. The assigned rep (or the card owner) gets an inbox notification when it is ready, and it opens with the booking. You can also generate or regenerate it there at any time.

If the AI service is unavailable, the brief is written from the lead record without talking points, and Lynqu keeps trying for the AI version through the day before the meeting. Use Add talking points on the booking to ask for them yourself.

Briefs need an AI plan (Business + AI or Enterprise). Connected AI assistants can read them through MCP with get-meeting-brief.

Reminders

Customers get confirmation and reminder emails automatically, using your templates and branding.