Collection · 6 articles
Drafting and voice.
A draft sounds like you or it doesn't, and the difference is usually a handful of habits: how you open, how much you explain before the ask, whether you sign off at all. These pages cover what a draft has to get right to clear that bar, the three ways a habit gets into Point in the first place, and how to read the learned rules back later and delete the one that started every reply with Hi there. They also cover the harder cases: a blank compose window with no thread underneath it, and a client who wrote to you in a language you don't read, where the first question is whether to answer in theirs. And they cover the pause before a message goes out, what it's for, and why an undo window isn't the same thing.
-
Getting AI replies that sound like you wrote them
Your voice is a small set of habits rather than a personality. What a draft has to get right, how to tell whether it did, and what to correct.
-
How Point learns your email habits, one sentence at a time
Point keeps what you tell it as plain rules you can read back. What it can learn, the three ways a habit gets in, and what it never reaches.
-
Seeing what an AI learned about you, and changing it
A learned rule is an instruction, not a description. How to read the list, which of three failures you actually have, and what deleting a line takes back.
-
Composing an email from scratch, with no thread underneath
A blank compose window hands a drafting tool nothing. What your instruction has to carry, where the missing context comes from, and what to check.
-
Why a drafted email waits for you, and what the pause is for
The gap between a written draft and a sent message is a setting. What it is for, why an undo window is not a substitute, and how it goes stale.
-
Answering a client who wrote to you in another language
Whether to reply in their language, what you can still check in a draft you cannot read, and when a message should go out in both.