Take over and hand back a person

Start with the right person#

Check your workspace, the person's company and the actual conversation before changing who handles it. In Introductions, open the opportunity and use Handoff & ownership to read Who is handling this. In Inbox, check the recipient and channel as well as the latest exchange.

An opportunity, a conversation and an Introduction describe different facts. Taking over does not confirm willingness to talk or complete an open required criterion. Follow Review your first Introduction when you need to check qualification.

If no linked conversation is returned, retry the supported read and keep that warning. A visible opportunity does not supply the missing exchange. Establish the correct conversation before acting.

Read the scope of Take over#

Where Kite is handling the opportunity, Take over holds Kite's automated work with that person on every channel and campaign in this workspace until you hand them back. This is a person-wide decision, so check for other conversations with them before choosing it.

The takeover also withdraws Kite's own drafts and scheduled replies. A reply you or a teammate scheduled remains queued. Review that pending reply separately if it should no longer go out. A takeover cannot retract a message already sent.

Taking over does not change your sending permissions, lift Do not contact or make a disconnected account ready. Keep those restrictions in place. If you need to review one, follow Manage exclusions and Do not contact.

Enlarge image

Read the person-wide takeover scope

Open full-size image Open full-size image

Check what the takeover confirmed#

After Take over, read the result instead of treating your press as confirmation. Check whether the person hold was established, which conversations were held and whether Kite's drafts and pending work were reconciled.

An incomplete, failed or unconfirmed result needs a current read. Some work may have changed before a later step failed. Keep the warning and do not assume that every thread stopped, or that nothing changed. Do not continue from a count that says the result is incomplete.

Understand I have this#

When Kite stops for a business decision, Needs you in Inbox helps you find the thread. KiteGTM stopped and asked for you shows why it paused and, when available, what it was going to say. Read both before answering.

I have this acknowledges that thread while keeping Kite paused there. It is a different action from Take over, which holds the person's automated work across this workspace's channels and campaigns. Acknowledging one thread does not establish a person-wide takeover.

If a held draft says “attached”, check whether the sending route actually supports the intended attachment. Copying that text into the composer does not attach anything. A draft also cannot establish permission to share a rate card or other business information. Resolve the actual business decision first.

Enlarge image

Read why this thread needs you

Open full-size image Open full-size image

Prepare before handing them back#

Confirm the fact or decision Kite needed and review any words you intend to send. Keep unanswered qualification, pricing, permission and timing questions open. Use Review and edit reply drafts to distinguish draft preparation from sending.

Check the latest thread and its current reason for being held. A newer reply or another decision can change what needs attention. If the control asks you to reload before handing it back, read the current conversation first.

Use Let it carry on and read the result#

Let it carry on in the held conversation hands it back and can allow Kite's permitted automated work to continue. For a person you took over, the hand-back also attempts to release the other conversations that takeover held. It does not clear an unrelated reason another thread needs you.

Wait for confirmation. If the result names conversations that remain held, check those reasons separately. If the hand-back is incomplete or unconfirmed, reread the current hold before deciding whether another attempt is appropriate. A changed reason needs a fresh review.

Returning handling to Kite does not bypass saved permissions, opt-outs, connection readiness, funding or work limits. A successful hand-back does not prove that a reply was sent, a meeting was booked or an Introduction was delivered.

Recover from an uncertain result#

If the request fails or times out, check the person and related conversations before repeating it. An error after an action started can leave a partial result. Keep the exact warning, time, workspace and action for support, and describe what you can currently confirm.

Do not work around a hold by changing channels, starting another campaign or treating a missing record as permission. Follow Get help with useful context and keep private conversation details out of public feedback.

Watch the handling controls#

Read the Handoff & ownership disclosure, then inspect an Inbox decision banner. These views show the scope and choices; the walkthrough does not take over, acknowledge or release anyone. Apply the checks to the same person in your own workspace before choosing an action.

Work with your agent#

Your agent can help inspect authorised conversation and opportunity context, identify the current hold and prepare a decision checklist. It should discover the connection's actual read tools and use returned IDs. Public University tools provide the guidance and its version; they do not read your private workspace.

Keep this task read-only. Your agent should report what is known, what remains held and which missing facts need your decision. Reading this guide does not authorise takeover, acknowledgement, hand-back, sending or changing permissions.

Prepare a read-only handling checklist for the person in the correct workspace. Discover the connection’s actual tools and arguments. Where available, use list_opportunities and list_conversations with their supported paging; use a returned conv_key with get_conversation. Do not invent an ID or infer a complete person history from a partial result. Report the current handling/hold only if the authorised reads actually return it; otherwise give the steps to inspect Handoff & ownership and Inbox in Kite. Distinguish person-wide takeover, a thread acknowledgement, an unrelated held reason and a human-scheduled reply. Keep willingness to talk and required criteria separate. Cite the current University guide, stable section and version.

Prepare only. Do not take over, acknowledge or resolve an escalation, hand a person back, generate/save/send/schedule a reply, cancel pending work, book a meeting, change permissions or suppression, or spend money. A public guide does not authorise a workspace action. If an outcome is incomplete or unconfirmed, retain the warning and require a current read before proposing a retry.

Before you move on#

You are ready when you can identify the person, distinguish a thread acknowledgement from a person-wide takeover, account for a human-scheduled reply and read the actual hand-back result without treating it as delivery or qualification.