Book the conversation. Keep its context with it.

A discovery conversation and a project review usually need different preparation. Create a booking page that explains what the meeting is for, who should attend, and what information will make the conversation useful. Custom questions can collect relevant context before the appointment instead of leaving the host to discover the topic at the start of the call.

Keep the request proportionate. A short review should not require a full new-business questionnaire, while a consultation may need more detail to be worthwhile. The page's promise should match the meeting itself. Avoid offering an apparently confirmed solution when the actual appointment is only a chance to establish fit or understand a problem.

Weekly availability rules describe the recurring pattern: the days and times when bookings are normally appropriate. Date-specific overrides handle exceptions such as travel, a workshop, a holiday, or a day reserved for concentrated delivery. Both matter because a schedule that was correct last month can be wrong for a particular week.

Connect Google Calendar so booking availability can use free/busy checks from your calendar. Choose the account and test a booking before sharing the page. Other calendar providers and automatic video-meeting creation are not currently included.

Imagine a consulting team offering an initial operations review. The booking page asks for the company, the process under discussion, and the most useful outcome for the meeting. The host makes Tuesday and Thursday afternoons available, then blocks a specific Thursday for an existing client workshop. The requester selects an available time and receives the booking confirmation.

If plans change, cancel the booking to keep the record current and share the booking page again if a new time is needed. Prepare from the submitted context, then capture a qualified opportunity in the CRM when the conversation is ready to move forward.

Scheduling errors are especially visible because they affect two people's calendars at once. A realistic end-to-end check is worth more than reviewing the settings screen alone.

1. Define the meeting

   Write a concise description and choose questions that help the host prepare. Make clear whether the appointment is discovery, delivery review, or a paid-service conversation.

2. Set the normal schedule

   Configure weekly availability and review the timing assumptions. Confirm that the host can consistently honor those windows.

3. Add exceptions and connections

   Apply date overrides and inspect any Google Calendar connection. Check a busy period as well as an apparently free one.

4. Complete a test booking

   Follow the public path, inspect the confirmation, and test the change or cancellation process. Only then use the link in normal client communication.

Meeting availability and production capacity are separate. A founder can have an open hour for discovery while the design team is fully allocated for the next two weeks. Use resource planning before promising a delivery start date. The booking page should help begin the conversation, not silently sell capacity that the agency does not have.

Scheduling also does not replace a broader meeting process. The host still needs preparation, a clear agenda, and a place for decisions after the call. Use documents for the brief or meeting outcome and the CRM or project for the next action. Keep the record useful even when the meeting does not lead to new work.