Limited offer

Build with our iMessage API/MCP. Get our sandbox for free.

Writing messages people answer instead of ignore

Messages get answered when they read like one person typing to another, which means one thought, no boilerplate, and a question that can be answered with a thumb. The first message has exactly one job: start a thread. Nobody buys off a first text, so optimising it for anything except a reply is wasted work.

What is the first message actually for?

The first message exists to open a thread. It does not qualify, pitch, or explain pricing. It earns one reply, where the conversation actually begins.

A first message written to sell reads like a brochure, and the reader clocks it in a second. The thread is dead before it started.

Say less than feels comfortable. Short reads as a person who is busy; long reads as a company selling.

What makes a message read like a person?

An iMessage reads like a person when it could not have been sent to anyone else. Inserting a first name into a paragraph that fits ten thousand people is a mail merge with a name, and everyone can tell.

Reference the specific thing: the page they converted on, the offer they asked about, the location they opened, the role they posted. One concrete detail beats four merge fields.

  • One thought per message. If it needs a paragraph break, it needs to be two messages.
  • No opt-out boilerplate stuffed into the text. Handle opt-outs properly, not decoratively.
  • No links in the first message. A link is a request; earn the reply first.
  • Ask something answerable with a thumb: yes, Thursday, or a number.
  • Write the way you would text a colleague, including the lower-case start if that is how you text.
  • Send a voice note where a paragraph would lose. Fifteen seconds, one point.

What should the follow-up sequence do?

The sequence should be dense in the first hour and thin fast after. All the value sits in the first touch; the rest catch people in a meeting.

Each follow-up needs a new reason to exist. A new angle, relevant example, useful information, or easy exit works. Repetition does not.

Give them the exit explicitly once: if this is not a priority, say so and I will leave it. Half of people who hear that tell you when to come back.

What does a thread look like when it works?

A working iMessage thread looks unremarkable. Short outbound, short reply, one question, a time. No sales language. The whole exchange fits on one phone screen.

Teams from green-bubble campaigns find this the hardest adjustment. Every instinct for one-shot broadcasts is wrong for conversations. You are not writing a campaign; you are texting somebody.

Message templates by industry and moment live here, free and without signup.

What to take from lesson 5

  • The first message has one job, which is a reply. Anything else in it lowers the odds.
  • One concrete detail beats four merge fields; a mail merge with a first name still reads as one.
  • Follow-ups need a new reason to exist, and an explicit easy exit gets answered more than it should.