Skip to content
Approvals

Every draft waits for your yes.

Nothing goes out under your licence without you having read it. That is the easy half. The hard half is what happens when your yes is ambiguous, and the answer is that Lewis hands the ambiguity back instead of resolving it.

A queue, not a feed

Each draft arrives with the lead’s name and the note it was written from, so you are approving a sentence you can check rather than one you have to trust. Four things you can do with it, and the fourth is the one most products do not have:

  • Send it. One word.
  • Edit it. Say what to change. Lewis reads the thread before rewriting, which is why the revision is not the question you already asked.
  • Skip it. Reversible, so Lewis may resolve who you meant from context, and it names the person in its reply, so a wrong guess is visible immediately.
  • Write it yourself. The draft stays on screen and the next thing you type becomes the message, sent verbatim.

That last one exists because the alternative was worse. Before it, the only way to put your own words in front of a lead was to reject the draft, which meant the product could be told how to change a message but never handed one.

A bare yes belongs to the question that was asked last

If exactly one draft is pending, “yes” sends it. If two are, “yes” gets you a numbered list.

That is not caution for its own sake. It is the one place where a wrong guess is expensive and irreversible: a message under a licensed agent’s name, to a real person, that the agent did not intend. Every other ambiguity in the product resolves toward doing something. This one resolves toward asking.

The reverse is guarded too. A “no” with a sentence after it is not a no: “no, make it shorter”, “no I want to write something”, “no, ask about her timeline instead” all keep the draft and act on the instruction. A negative only lands as a rejection when nothing meaningful follows it.

Only the engine may say a message went out

There was a version of this that said “Sent. Next up is Chris Chase…” when nothing had been sent, because the phrase used to approve it was one the rail could not read. On the agent’s screen that is indistinguishable from success, which is the worst property a bug in this area can have.

So the claim itself is checked. If a turn says a message went out and no message went out, the turn is repaired into a re-ask. A phrase the rail could not read is not consent to infer.

Held is the normal verdict, not the failure

Any good draft to a lead whose note asks for a viewing names a day. Naming a day is a commitment. So hold is the state every draft is in by construction. It is what “waiting for your yes” means, and it is not a sign anything went wrong.

What is different is block. A blocked draft never reaches your queue at all. That distinction is the guardrails page.

Next to this

Your book is already full of people who meant it.

Point Lewis at the export and he works it over text, every draft still waiting on your yes.