Prepare your sending identity and meeting handoff

Confirm how Kite introduces your business, connect only what the mission needs and decide whether the handoff includes a booked meeting.

Before you begin#

Access to your Kite workspace. Keep your objective in plain language.

Follow the steps#

1. Confirm your sending identity when setup asks. Check the business name, sender name and resulting identity before creating a Kite email. The current screen explains that the created Kite email address is fixed; review it carefully.
2. Choose Kite email or your connected sender. You do not need to build email infrastructure when using Kite email. A confirmed Kite email can still be preparing when the mission starts, but actual sending waits until it is ready.
3. Use Settings → Domains and email for your own inbox. Choose the provider shown and follow the current connection instructions. Enter account credentials only into the trusted product/provider flow. A connected sign-in account is not automatically a sending account.
4. Confirm the channel selection. Email, LinkedIn and SMS each depend on their own connection, permissions and channel rules. Extra channels are optional; paying does not bypass provider restrictions or SMS usage charges.
5. Decide how to receive the Introduction. For a booked meeting, connect the calendar under Settings → Calendar and check the host, availability, timezone and meeting details. If booking is off, choose an agreed direct handoff instead.
6. Verify status before relying on the connection. A selected sender, queued preparation or expired calendar sign-in is not proof that sending or booking can proceed. Read the status and resolve the named issue.

Enlarge image

Prepare your sending identity

Open full-size image Open full-size image

Enlarge image

Set up meeting booking

Open full-size image Open full-size image

What you should see#

You should know which identity and channels the mission will use and where the handoff goes. A separate CRM is optional, and signing in with Google does not connect Gmail, Calendar, Drive or contacts.

If something is missing#

If Kite email is preparing, read the status; do not create another account or buy domains by default. If a sender cannot carry the configured load, review the actual shortfall and sending setup. If a calendar read is unavailable, retry the read and keep its state unknown. Use the supported sign-in recovery only when the current error identifies a lost grant or ended sign-in. Recover provider connections helps choose the appropriate next step; Set up and check booking covers the calendar, host, zone and actual meeting outcome. Review an agreed direct handoff when it fits the next conversation. Never assume that enabling an integration authorizes every action.

Work with your agent#

Use the task below to prepare a useful next step. Give your agent current University guidance and only the business information it needs. Ask it to separate facts, assumptions and decisions that need your answer. If its tools cannot read something, the answer is unknown.

Prepare a connection checklist for my first mission. Ask whether I want Kite email or my own sender, which channels I intend to use, and whether I want booking or a direct handoff. Explain required versus optional connections and what status I should verify. Do not ask for passwords, codes, app passwords or tokens; I will enter those only in the trusted connection flow.

Prepare guidance only. Do not change settings, create or start work, connect accounts, send messages, enroll contacts or spend money. Use current tool discovery; never invent capabilities or record IDs. Show missing evidence and the next step for me to review in Kite.

Check your next step#

The business and sender identity are correct. Complete the readiness notes below, then use your Kite workspace to confirm what is actually saved. Checking a box here does not change your account.