Review bookings

Before a call, review why the person booked it and what your team already knows. Open Bookings to inspect the company, source, qualification, call details and stage, then record the outcome after the conversation.

Review a call

1. Find the company and check the source and qualification details. Open its website if you need to confirm what the business does.
2. Read the call information and current stage. A scheduled call and a completed call are different states; confirm what happened before changing the stage.
3. Use the stage control to record the supported next state. Reload the page to confirm the update persisted.
4. Open the related contact or opportunity to record who will follow up and when.

The summary shows qualified inquiries, bookings, calls held and attributed won revenue. Use those figures to inspect the booking workflow; a scheduled meeting alone does not establish a sale.

Produce a debate

If your workspace uses the Bookings module for debates, open Debate productions from Bookings. Create a production from an existing contact, then link a proposed counterpart and target date. The production keeps topic interest, counterpart agreement, proposition, perspective, format, date, invitation, production terms, announcement, recording and publication as separate commitments. The first missing commitment appears as the next step in the production and in Today.

For each commitment, record what was actually agreed and cite the Gmail message or Drive transcript. A founder can also confirm a fact directly. Review the quoted source before approving an AI proposal. A proposed counterpart or question remains proposed until someone confirms it; interest alone does not confirm a booking.

When both participants have agreed, choose their two inbound acceptance messages, review the exact event details, and submit the invitation for approval. Approval sends one Google Calendar event to the two saved contact addresses. The result records the provider event and recipient responses. Verify calendar reads that exact event again. A canceled event, changed time or attendee, missing requested Meet link, or participant who has not accepted keeps the booking incomplete. If the provider confirms a cancellation, use Reopen canceled invitation before preparing a replacement. The scheduled work engine also rechecks linked invitations daily when it is configured and running.

The booking remains in its own workspace. You need connected Gmail and Google Calendar, current synced participant threads, saved contact addresses and a working scheduled work engine for the complete automated loop. If a source or provider receipt is missing, inspect the production and connection status before another send. A pending approval is not an invitation, and an invitation is not a completed recording or publication.

When a booking is missing or wrong

Check the company and contact first before creating another record; a different email address or an unlinked inquiry usually explains why the relationship you expected isn't showing up.

For an expected calendar update that hasn't appeared, check the connection in Setup: a saved connection tells you it was configured once, not that the most recent sync succeeded. Calendly stays optional throughout this guide, so nothing here requires enabling it.

After correcting a stage or connection, reload the booking list and confirm the specific row. If the save did not persist, retain the error and use Troubleshooting.

Booking mode and attribution

The workspace booking setting has three modes: embedded scheduling, a manual link, or disabled. An embedded calendar can accept appointments without providing verified event attribution to the workspace. Setup reports those capabilities separately.

A ready attribution check requires a recent signed booking or cancellation receipt. If a previously working receipt is stale or failed, Setup shows the degraded state and its recovery action. Confirm a fresh controlled event before treating the connection as ready again. A manual link does not imply API access, and disabling booking does not enable Calendly.