Set a standard for your first Introduction

Define the required conditions for a relevant conversation, and keep useful preferences separate. Unconfirmed required facts stay visible for the call; a fact recorded as not met rules the person out.

Before you begin#

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

Follow the steps#

1. Open Qualify in the mission builder. Start with the objective and the people you chose. Your criteria should explain what makes a conversation worth taking forward.
2. Require willingness to talk. A matching profile, a polite acknowledgment or a calendar booking alone is not enough. Look for relevant expressed interest and agreement to be connected.
3. State each required condition clearly. Use conditions that can be established from relevant evidence or conversation. For example, a software mission might require responsibility for the workflow, a current relevant problem and willingness to discuss it.
4. Move preferences out of the required list. A useful timing detail or company-size preference can add context without being essential. If it is required, Kite must not treat it as optional just to create a result.
5. Avoid duplicate or vague conditions. Keep up to eight conditions. Use concise wording and follow any validation shown in your workspace. When the full builder asks for your own standard, keep at least one Required condition. If your setup uses willingness to talk as its baseline, additional conditions are optional. Willingness and an actual handoff still matter. Combine duplicates and replace “a good lead” with a concrete test.
6. Check the handoff you want. Decide whether the next step is a booked phone/video meeting or an agreed direct handoff. A meeting is optional; the qualification and conversation context remain necessary in either route.

Enlarge image

Set your Introduction criteria

Open full-size image Open full-size image

What you should see#

You should be able to assess each required condition as supported, not met or unknown. An unknown fact stays unknown and is confirmed on the call; it is not a failed criterion. A required condition recorded as not met rules the person out. What makes an Introduction qualified? includes the existing interactive assessment; use it to practice without changing your mission.

If something is missing#

If a condition cannot be established, clarify what would count as evidence or ask your business for the missing decision. If the product asks you to remove duplicate or excess conditions, revise them on Qualify and review again. Do not label an ambiguous reply qualified or remove a real requirement simply to obtain a booking.

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.

Help me write the required Introduction criteria for this objective. Separate must-have conditions from preferences. For each required condition, describe acceptable evidence and what would remain unknown. Require willingness to talk and an agreed next step. Do not relax criteria to produce a result.

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#

Every required condition is concrete. 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.