Follow-up isn’t left to memory. It’s written into the system.
Follow-up written for each account, one step at a time. When a reply comes in, the conversation moves to your sales team.
- Your sales team
- Day 1 · first message
- Day 3 · reply received
- Day 8
- Day 15
A sequence, day by day.
Four steps on four days, each written for that account. The sequence below is an example.
| Day | Step | When | From the message |
|---|---|---|---|
| Day 1 | First message, written for the account | Once the list and the decision maker are ready | Hello, we make containers and lids from 250 ml to 5 kg for [dairy] plants like yours in [Balıkesir].The sales team at [Packaging maker] |
| Day 4 | Short follow-up | Three days after the first message | Hello, a few days ago we mentioned our container and lid options for your [dairy] production. Shall we send you the sample list?The sales team at [Packaging maker] |
| Day 8 | A note from another angle | Four days after the second step | Hello, a different angle this time: we also make leak-proof lidded containers for [dairy] producers. We can share the size chart.The sales team at [Packaging maker] |
| Day 15 | Closing note | The last step; the sequence ends here | Hello, we won’t take up more of your time on this. If packaging comes up later, just reply to this message.The sales team at [Packaging maker] |
The parts in brackets change with each account.Example
Move the day, follow the sequence.
- Step 1 · Day 1sent
- Step 2 · Day 4waiting
- Step 3 · Day 8waiting
- Step 4 · Day 15waiting
Example
Personalisation isn’t filling in a field.
The first line of the message starts from what the company makes, how big it is and what the reader decides on. Personalisation isn’t a name or a company name dropped in at the end; it’s the sentence itself.
| Template | Written for the account |
|---|---|
| Dropping a name and a company into a template. | Building the first line around sector, size and role. |
| The same text, the same day, for everyone. | Each account gets its own text on its own day. |
| Nobody knows who will read it. | The decision maker’s role is known, and the message is written to it. |
The rules of a sequence.
- One decision maker per account.
- Every message is written for its account; the same text never goes out to the list in bulk.
- A sequence ends with a closing note; it doesn’t run forever.
- An account that replies is handed to your sales team with the context of the conversation.
Your rep never starts from scratch.
When a reply comes in, your rep gets a handover record: who was written to, what was said and what the other side wants, all in one place.
- Account
- Dairy producer · Balıkesir · 320 staff
- Decision maker
- Supply chain manager
- Request
- a call on Tuesday or Wednesday, 1 kg and 5 kg samples
- Context
- first message (day 1), reply (day 3)
- Next step
- the rep proposes a time
Questions about follow-up.
How do you set up automated follow-up for a sales team?
The target definition and the list come first, with a decision maker found at each account. Then the steps of the sequence and the gaps between them are set, and each step’s message is written for the account. It isn’t a one-off auto-reply to an incoming message; it’s a sequence that moves step by step. The SilverOps team sets it up and runs it, and your sales team takes over once someone replies.
When does a follow-up sequence end?
Every sequence has an end: the last step is a short closing note, and the sequence stops there. Accounts that reply are handed to your sales team and show on the panel with their stage.