Set up and check booking · Kite University

Check the calendar, host, time zone and rules, then distinguish a proposed time from a confirmed meeting.

Set up where an agreed meeting should go, check the time and host, and keep an offered time separate from a confirmed booking.

Start with the meeting you want#

Decide whether the next conversation should be a phone call or a video meeting. Keep the business reason and your required Introduction criteria clear. A booking alone does not establish an Introduction: the person must be willing to talk, have nothing on record ruling them out and be handed over with context and a next step.

You can use Kite without a separate CRM. If the person asks your team to contact them directly, review that agreed handoff rather than forcing a calendar booking. Use Review your first Introduction for the qualification and handoff check.

Open Calendar in the right workspace#

Open Settings → Calendar and confirm your workspace before changing anything. Check the connection, the calendars Kite can book into, the host and the time zone. Signing in to Kite with Google does not itself connect Google Calendar.

If the page could not be read, reload it. Keep the connection, booking permission and saved settings unknown until their reads succeed. An unavailable read is not evidence that you have no calendar or that a sign-in has ended.

If a calendar you recognise is unexpectedly missing or shown as disconnected, compare the provider account and current error before replacing credentials or disconnecting it. That display alone does not establish why the account is missing.

Use CRM and integrations for the relevant provider's connection flow. Enter credentials only in the trusted product or provider page. Opening a sign-in page does not finish the connection; return to Kite and check the recorded account and current status.

Choose the calendar and host#

A connected account and a calendar selected for bookings are separate choices. Read the explanation for a skipped or unavailable calendar before changing it.

For Google calendars, check whether the intended calendar is in use and where it sits in the order. Reordering changes which calendar Kite tries first; it does not move existing meetings. For another supported calendar or booking-page provider, check the workspace's selected primary provider and its current readiness rather than assuming Google's per-calendar ordering applies.

Check who receives the invitation. A shared calendar without a named host can be skipped. Use the appropriate host control only when you intend that address to appear on invitations. Changing the host affects later bookings; it does not rewrite invitations already sent.

After saving a choice, read it back. A calendar can be connected yet still lack the host, booking selection or permissions needed for the intended work.

**Read the calendars selected for booking**
Calendar settings show selected Google calendars, a reported ended sign-in and a shared calendar without a named host.

**Check who receives the invitation**
The shared-calendar host editor is open with no address entered; its confirmation remains disabled.

Check the effective time zone#

Read the workspace time zone and any calendar-specific override. A calendar with its own zone keeps that choice when the workspace zone changes. A calendar following the workspace uses its current zone; an unset zone needs resolving before interpreting a proposed time.

Read a time together with its date and named zone. Do not substitute your browser's local zone or infer the prospect's zone from their company address. If a reply says “Thursday at eleven” without enough context, clarify it before booking.

Changes to a saved zone apply to later interpretation and offers. They do not move an already booked call or change a time already put to someone.

**Read the effective calendar zone**
The zone editor shows a Pacific override and explains that existing calls keep their booked zone.

Read the booking rules#

Review the days and hours, default meeting length, minimum notice and space between meetings. The available controls let you save supported changes; use the current values your account actually returns.

Check a change's tradeoff. More notice can remove near-term choices. More space between meetings reduces the times Kite offers. Spacing offers does not reserve those slots or prevent someone from arranging another meeting in the calendar.

Save one setting at a time, then read the current value back. Meeting length also affects how Kite describes a call in a reply. If one part of that change could not be saved, keep the warning and reconcile the saved length and reply guidance before making another change.

**Read hours, length, notice and gap**
Booking rules show weekday hours, thirty-minute calls, four-hour notice and a fifteen-minute gap.

Decide who authorises booking#

Read the current authority to book without asking. Permission to act and a ready calendar are different facts. Turning on booking authority does not connect a calendar, qualify a person, send an invitation or start a mission by itself.

Changing booking authority can involve both booking rules and reply permissions. If Kite reports that one part changed and another did not, inspect both current settings. Do not assume the switch's appearance establishes the whole result, or repeat a different choice before resolving the partial change.

Use the current in-app approval controls for work that needs your decision. A public University guide and a copied agent task do not approve a booking or broaden an agent's permissions.

Check the meeting type and link#

Read What a call it books looks like and the video-link settings. A saved meeting type can adapt when the person asks for another kind of conversation. Check the actual invitation details and any missing phone, address or link information.

A connected calendar does not guarantee a usable video link. Depending on the selected provider and settings, a meeting can use the calendar's native link, your connected Zoom account or a saved standing link. Check that the intended people can use that link.

Some choices save as soon as you select them. Review the current value before changing a meeting type or video preference. Do not select an option merely to inspect it if you intend to leave the setting alone.

Test Zoom creates, moves and deletes a provider meeting. Use it only when you intend that real test and have the required account authority. It is not a read-only connection check.

Offer a time deliberately#

When a conversation needs a proposed time, use its Offer a time control where available. Check the selected calendar, meeting length, date and explicit zone. Read the choices before confirming.

The offered-time grid uses configured hours. Its suggestions do not establish that the provider's calendar is free, and an offered slot is not a reservation. Check the current provider diary when availability is uncertain.

Confirming an offer can fill the reply and change the conversation's stage. It does not by itself book the meeting or send the message. Check the resulting draft before any separate approval or send.

The proposed-time display is held in the current tab. Its appearance does not establish that a provider booking or a durable proposed-time record will be available after reloading.

Cancelling the open time picker abandons that staged choice. Removing a proposed time does not cancel a booked meeting. Preparing another offer does not move an existing booking.

**Read a proposed time before confirming**
The offered-time picker explains that no calendar was checked and that confirmation creates neither an event nor a sent reply.

Read the booking outcome#

Keep these states separate when reading the conversation, approval or recorded booking:

What you have	What to check next
A proposed time	Whether the person agreed and the current availability supports it
A booking approval waiting	The person, time, zone, calendar, conditions and action you are being asked to approve
A host-confirmation request	Whether the host actually accepted it; a request is not a confirmed meeting
A scheduled booking	The recorded event, person, calendar, date, zone and next step
A change or cancellation	The current recorded event and the actual provider result
An unconfirmed result	Current state and the retained warning before another attempt

A successful approval decision alone does not prove that the provider event exists. Read the returned outcome and the current record. A scheduled time that has passed does not establish attendance, a completed conversation or a commercial result.

If a booking card or field is absent from the surface you are using, keep its state unknown. Use the relevant supported record read or current calendar rather than inventing a booking from an offered time or a reply.

Recover a calendar or an uncertain action#

A sign-in that has ended and an account that did not answer need different next steps. Use Recover provider connections to distinguish them. A successful calendar check establishes the returned read or health result; it does not prove permission to create or change events.

The Calendar event view can be partial. An empty-looking period or a returned list is not a complete free/busy check. Inspect the provider's own diary before treating a time as available.

For a partial or unconfirmed save, booking or move, preserve the exact message, intended action and time. Read the current settings and event before another attempt. Another person may have changed the meeting in the meantime. Do not create a duplicate booking, disconnect a healthy account or clear browser state to make the warning disappear.

Where a supported change approval is shown, check what event and calendar it will move and whether the proposed time is still valid. A new offered time is not that change approval. If Kite cannot establish the current result, use Get help with useful context.

Watch the booking controls#

Use the walkthrough to locate Calendar readiness, the host and time zone, booking rules and the proposed-time picker. Review the meeting type and link with the written steps. In your own workspace, inspect what is actually saved or booked there.

40 sec · Captioned, no audio

Check booking readiness and a proposed time

Work with your agent#

Ask your agent to prepare a booking-readiness review from current authorised context. Have it separate saved settings, permission to book, an offered time, host confirmation, the provider event and Introduction qualification.

Keep missing or partial reads explicit. Let the agent return a proposal and the exact in-app review steps. You decide whether to make a setting change, approve a booking, contact the person or run a provider test.

Work with your agent

A clear task to copy

Prepare a read-only booking-readiness review. Discover the currently available authorised Kite tools and their exact argument schemas before reading account state. Use only supported reads in the correct workspace. Keep missing fields, failed reads and partial results unknown. Cite the current University guide, stable section and version. Public University tools supply guidance and do not reveal private account state or grant permission to act. Read the saved calendar selection, host, effective zone, hours, duration, notice, gap, booking authority and meeting-link state where supported. Separate a reported connection from grant loss or unreadable state; a read check from event-write permission; a proposed time from host confirmation or a provider event; and a booking from Introduction qualification. A Calendar list can be partial and a tab-held proposed-time display is not a durable booking receipt. Preserve an unconfirmed result and propose reconciliation before any retry. Prepare only. Do not save settings, change permissions or credentials, connect or disconnect accounts, run provider tests, book or move or cancel meetings, approve requests, enroll people, import or re-read sources, pause or remove sources, replay deliveries, send messages, activate work or spend money. Return the exact in-app review location and a readback checklist for me.

This prepares guidance. Use the controls in your Kite workspace for account changes and starting work.

Before you move on#

Check the calendar, host, effective zone, rules, authority and meeting link you intend to use. Resolve uncertain state before another booking action. The readiness notes below record your own checks; they do not change settings, approve a request or create an event.

Your readiness check

0 of 6 checked

I checked the correct workspace, calendar and hostI read the effective zone and clarified the agreed date and timeI reviewed hours, length, notice, gap and booking authorityI checked the actual meeting type and usable link or phone detailsI kept an offered time separate from a confirmed eventI reconciled any partial or unconfirmed outcome before another actionThese checks stay in this browser. These are your notes; Kite’s actual account state and start checks decide readiness.