Review and edit reply drafts

Start with the actual conversation#

Open Inbox, select the person and check the channel, recipient, subject and recent exchange. Read what was sent from your side and what the person actually asked. Needs you helps you find conversations where Kite stopped for your decision or kept a reply for review.

A response can be a question, interest, a rejection or an opt-out. A reply alone is not an Introduction. Keep the person's willingness to talk and every required criterion separate from the fact that a message arrived.

If the conversation cannot be read, retry the supported read and keep its warning. A partial thread does not establish the person's complete history. Do not write a confident answer from missing context.

Enlarge image

Start with the actual conversation

Open full-size image Open full-size image

Read the draft and its reasoning#

A ready draft appears under KiteGTM wrote a reply. Read the entire body, then open Why it wrote that when the reasoning is available. Check the facts it relied on and Not sure about. An uncertainty is a question to resolve, not a fact you can promise.

For example, a person asks whether a particular equipment-finance application needs a co-signer. Your saved information covers credit criteria but does not answer that requirement. Keep it open, get the actual business decision and avoid promising eligibility, a rate or a turnaround you cannot support.

Read any reason the draft is being held. Writing means the draft is still being prepared. A failed attempt has not produced a ready reply. A block or opt-out is not a drafting problem to work around by writing on another channel.

Enlarge image

Read the reasoning and uncertainty

Open full-size image Open full-size image

Ask for a useful change#

When the draft is ready, open Ask for it differently. Tell Kite what to change in this reply, such as “Answer the question first, keep the requirement open and leave the price out.” The shortcuts add words to the instruction box; they do not run a rewrite. Write it again submits the instruction.

Compare the returned words with the conversation. Earlier takes remain available when the control shows them. A one-off rewrite does not become a permanent business rule. If Remember this for [person] is offered, saving it is a separate action that belongs on that person's notes; check the confirmed result before assuming it was kept.

If there is no draft, Draft reply asks Kite to write one from the conversation and your optional instruction. Generation may use applicable credits. A queued or writing result is not a finished draft. During a rewrite, Check current draft rereads its state; it does not cancel a reply already being written. Read the current state before retrying.

Enlarge image

Prepare a rewrite instruction

Open full-size image Open full-size image

Put it in the box and check it again#

Choose Put it in the box to bring a ready draft into the composer. This does not send the message. Check the recipient, channel, email subject and any Cc entries, then edit the wording as needed. A previous take can also be put in the box for further editing.

If you already had words in the composer, use its offered restore control when you want them back. Switching to another person is a new conversation; make sure your text and instruction still belong to the person on screen.

Typing words into a reply box does not attach a file. Do not say “attached” unless the intended attachment is actually present and supported by the sending route. Likewise, proposing a time does not create a booking. Use the actual booking controls and current availability when you need to arrange a meeting.

Understand Send and its outcome#

Send is the separate action that submits your reply. The composer states its 30-second undo window; a picked future time is a scheduled reply. Use the current Undo or take-back control while it is available. A schedule or countdown is not proof of delivery, and stopping later cannot retract a message already sent.

Check the resulting message and any warning. A refused, held, failed or unconfirmed result must stay that way until a supported read confirms more. Even provider acceptance does not establish that the recipient read the message, agreed to talk or met your required criteria.

If the send result is uncertain, read the conversation and its pending work before submitting the same words again. Keep the exact error and time for support. Follow Get help with useful context without copying private prospect details into public feedback.

When Kite needs your business decision#

KiteGTM stopped and asked for you explains the decision it needs. Read the reason and anything it was going to say before deciding. I have this acknowledges the thread while keeping Kite paused there. Let it carry on hands it back and can allow permitted automated work to continue.

Answer the actual missing business fact first. Handing it back does not make a false claim true, lift an opt-out or broaden saved permissions. If you want to take over the person's automated work across channels and campaigns, follow Take over and hand back a person; the thread acknowledgement is a different control.

Watch the reply controls#

Follow the conversation, inspect the draft's reasoning and find Ask for it differently and Put it in the box. The walkthrough does not generate or send a reply. Use the written checks against your own current conversation and composer before choosing an action.

Work with your agent#

Your agent can help read authorised context, identify missing facts and propose words for you to review. It should discover the connection's actual tools and use returned conversation IDs. Public University tools supply guidance; they do not read your private Inbox.

When your authenticated connection exposes reply_to_conversation, it saves a draft with the supplied text. That is a workspace write. It does not send, attach a file or book a meeting. Use it only when you have authorised saving that exact draft to the correct conversation, then check the returned outcome and open its review link in Kite. An unconfirmed save is not proof that the draft was kept; reread the correct conversation before retrying. Sending remains with you in Kite.

Prepare a reply-review checklist from authorised context. Discover the connected Kite tools and exact arguments. Where available, use list_conversations and get_conversation with a returned conv_key; use supported paging and keep an incomplete thread explicit. Read the actual question, messages from your side, draft and any current hold or uncertainty. Separate willingness to talk and required criteria from the existence of a reply. Propose wording that leaves unverified pricing, qualification, attachments, permissions and calendar times open. Cite the current University guide, stable section and version.

Prepare only. Do not call reply_to_conversation, generate, save, rewrite, send or schedule a reply; book a meeting; save a person instruction; acknowledge, take over or release a hold; change permissions; or spend money. Saving an exact draft through reply_to_conversation requires separate explicit authorisation and a confirmed result. Public University tools do not supply private account facts.

Before you move on#

Explain what the person asked, which facts are known and what still needs a decision. You are ready when you can review the actual draft and distinguish editing, saving, scheduling, sending, delivery and qualification.