KoltrixReply suggestions or full drafts: choosing the right level of help
Should an AI give you a few short reply options or a full draft? How to choose the right level of help by message type, risk and how much you trust your review.
On this page(9 sections)
Two kinds of AI help look similar from a distance and behave very differently in a busy inbox. One gives you a few short reply options to pick from. The other writes a whole draft that you edit and send. Teams often switch one on, feel that something is off, and blame "the AI" when the real issue is that they picked the wrong level of help for the message in front of them.
This guide helps you choose on purpose. It is not a product comparison. It is a way to decide, message by message and then team by team, how much writing you want a machine to do.
The two levels, defined
Suggestions are short. A line or two, sometimes just a direction: "Thanks, that works for me", "Can you send the invoice number?", "I'll look into it and reply tomorrow." You scan, tap or choose one, and maybe tweak a word. The person is still the author. The tool saves keystrokes.
Full drafts are complete replies with a greeting, the substance, and a sign-off. They can pull facts from the thread, follow a style guide and quote earlier messages. You read the whole thing, check each claim and edit. The tool saves composition time, but it moves your job from writing to reviewing.
Neither is better. They are different trades. Suggestions give you speed with very little new risk. Drafts give you more time back on hard messages, and they ask more of your attention before you send.
What changes when the AI writes more
Every extra sentence the tool writes is a sentence you did not choose. That has three consequences.
More surface for mistakes. A two-line suggestion can be wrong, but you will notice. A 200-word draft can contain one wrong date or an invented policy in the fourth paragraph, and a tired reader skims past it. The more text, the more careful the check has to be.
More drift in voice. Short replies hide the difference between your voice and a generic one. Long drafts expose it. If you want drafts that sound like you, read our post on AI reply drafts in your own voice and set a style guide for AI-drafted email.
More temptation to skip the read. The longer and more fluent a draft is, the easier it is to trust it. That habit is the real risk, and it is why the principle in AI drafts, human sends matters more as drafts get longer.
A quick way to decide: four questions
Ask these about the message you are answering. You will answer them in a few seconds once you have done it a dozen times.
- Is the reply mostly a decision? "Yes", "no", "Tuesday works", "please send it". If the content is a choice you make, suggestions fit. You are the source of the answer, and the words are routine.
- Does the reply need facts from elsewhere? Order status, a contract date, what was agreed three weeks ago. Facts are where drafts earn their keep, because the tool can gather them from the thread. They are also where drafts go wrong, so this is "draft, then verify".
- What happens if a sentence is wrong? A slightly clumsy "see you then" costs nothing. A wrong refund promise, a wrong legal statement or a wrong price costs real money. The higher the cost, the more you want to write the critical sentence yourself, whatever tool produced the rest.
- Is the relationship delicate? Apologies, complaints, a cancelled contract, a first message to someone important. Here the tone is the message. A draft can help you get started, but it should not be the last word. For a worked example, see apology emails that rebuild trust.
Matching help to message type
Here is a practical map. Adjust it to your own work.
Acknowledgments and confirmations. Suggestions. "Got it, thanks" does not need a draft, and a draft would only add padding.
Scheduling. Suggestions for simple replies, drafts when several people and time zones are involved. The risk is in the details, so check dates and zones yourself. Our post on meeting and scheduling requests in a shared inbox covers the common traps.
Routine support questions. Drafts, with a human reviewer, work well when your answers are consistent. Keep a short checklist, like the one in reviewing AI-drafted replies. If the same question arrives ten times a week, a saved reply may serve you better than any AI; see reusable reply snippets.
Replies with facts and commitments. Drafts, plus a deliberate check of every number, date and promise. Treat the draft as a research assistant's first pass.
Complaints and bad news. Write the opening and the key sentences yourself. If you use a draft, use it for structure, then rewrite.
Legal, financial, medical or contractual matters. Do not rely on either level without a qualified person's review. This guide is general practice advice, not professional advice.
Think about the team, not just yourself
On a shared inbox, the level of help is also a policy question.
- New teammates often do better with suggestions. They learn the house voice by choosing and editing short lines, and they are less likely to send a long reply they did not fully understand.
- Experienced teammates may prefer drafts, since they can spot a wrong claim fast.
- A reviewer for high-risk replies is cheaper than a ban. Agree on which message types need a second pair of eyes, whatever level of help produced them. The post on ownership of AI-drafted replies in a shared inbox explains why one named person should own each reply.
If you are introducing AI help for the first time, start small. Piloting AI drafting with a small group lays out how to begin without surprising customers or colleagues.
Using an assistant with Koltrix
If you connect an assistant such as Claude through Koltrix, drafts land in your Drafts folder for you to review, and sending stays under your control: it is off unless an admin allows it, and even then the assistant must show you the message and get your yes first. That setup fits the "full draft, human decides" level well. For short replies you may find it quicker to write them yourself or give the assistant a very tight instruction. You can see how to brief an assistant in draft replies with Claude and Koltrix Drafts, and what the connection can and cannot do on the MCP page.
Briefing for the level you want
Tell the tool what you want, because it cannot guess.
- For suggestions: "Give me three one-line replies. One that agrees, one that asks a question, one that declines politely. No greeting, no sign-off."
- For a full draft: "Read the whole thread first. Write a reply in my voice, under 150 words, answering only what they asked. List any fact you are unsure of at the end, outside the reply."
That last instruction is worth keeping. A draft that flags its own uncertain facts turns your review into a short list instead of a hunt.
Signs you picked the wrong level
- You edit every draft heavily. The message needed your own writing, or your style guide is too thin. Move to suggestions, or improve the briefing.
- You accept suggestions without reading. They are short enough to trust blindly, which is a risk of its own. Slow down on anything with a commitment in it.
- Customers say replies feel generic. Drafts are doing work that should be personal. Write the opening and closing lines yourself.
- Replies sit unsent. You may be asking for drafts on messages that need only a quick answer. Switch to suggestions and clear the queue.
- A mistake slipped through. Do not just apologize and move on. Ask which message type it was and raise the level of review for that type. Our golden set guide shows how to measure draft quality over time instead of relying on a feeling.
A simple starting rule
If you want one rule to begin with: suggestions for decisions, drafts for explanations, your own words for anything that could hurt. Review it after a month. Look at which replies you edited most, which ones customers answered with confusion, and which ones you never needed help with. Then move the lines.
The right level of help is not a setting you choose once. It follows the message, the stakes and your own attention that day. When you are rested and the question is routine, let the tool do more. When you are rushed and the reply matters, do more of it yourself. In both cases the same rule holds: the person who clicks send owns what it says.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
