first-touch-message-after-acceptlisted

# The first message after accept states intent, and never repeats the note The first message after an accepted invite says clearly why you are writing. Which of two families it belongs to depends on one fact: did the person actually see an invite note? - **Note not seen** (free accounts, stripped notes, invites sent without one): this message is the first touch. Fact, what you do, a clear next step. - **Note seen** (the note was delivered): refer to it briefly ("following up on my note about X") and end with a question. Do not retell it. If they stay quiet, the second message is short and adds something that was not in the first: a customer number, a case, an artifact you can send today. ## Why Repeating the same thought in the same words reads like a mass send. Retelling from scratch to someone who already read your note reads like a machine that does not remember its own messages. Both mistakes spend the only first attempt. What was written and what the person read are two different things. In one of our own queues seven people were due for a first message on the same day, and three of the seven had never seen the note, because the sender had stripped it while the note text stayed in the record. In a wider check, 44 people had received two separate first touches built on the same fact, 17 of them within six hours. ## How to apply 1. Look up the invite record and read the delivery flag (note sent: yes or no). Ignore the note text field; it can be filled even when noth