Build a multichannel sequence worth answering
Email, a connection request and a call, spaced so it reads as persistence rather than noise.
The conversation
Sample accounts and numbers, for illustrationYouBuild a four-step email, LinkedIn and call sequence for Northwind Labs. Use their support operations hiring as the angle, and keep every touch focused on the same problem.
Unify3 preparation steps · Exa web research and connected mailbox
- Read the support operations job postings for the team’s stated responsibilities.
- Checked existing correspondence for tone and prior conversations.
- Kept the proposed angle separate from claims the account has not confirmed.
The thread is how Northwind will support a growing team. The open roles are evidence of hiring, not proof that their current tooling is failing.
| Step | Timing | Channel | Purpose |
|---|---|---|---|
| 1 | Day 1 | Ask about the support operations buildout | |
| 2 | Day 3 | LinkedIn request | Introduce yourself without repeating the pitch |
| 3 | Day 6, if no reply | Offer a useful rollout checklist | |
| 4 | After a positive reply | Call task | Discuss the priorities they actually named |
Any reply stops the scheduled follow-ups. The call is conditional on engagement.
YouShow me the messages, with no “just following up” and no meeting ask in every step, and show me the checks before anyone enters the sequence.
UnifyEach touch adds something. The first starts a conversation, the second makes the connection, and the third is one question. The sequence is ready for review, with the first batch held before enrollment.
- Day 1Email
Support ops at Northwind
Dana, I noticed Northwind is hiring across support operations. Is the priority getting more capacity from the current setup, or deciding what the next setup should look like?
- Day 3LinkedIn connection request
Dana, I work with support operations teams as they grow. Saw you’re building the function at Northwind and thought it would be useful to connect.
- Day 6Email
Dana, would a short checklist for mapping support requests before a team expansion be useful?
- After a replyCall preparation
Start from Dana’s answer. Confirm the current priority, who owns the decision, and whether a rollout is planned. Skip questions already answered by email.
Set up
- Enrollment checks Exclude customers, open opportunities, unsubscribed contacts, and anyone in an active sequence. Confirm the account owner and contact address.
- Sending rules Use the recipient’s business hours. Stop on reply or opt-out, and create the call task only after a positive response. Review the first batch before it runs.
The sequence is the deliverable; the checks and rules are what Unify set up around it.
Building the sequence, with and without Unify
Four steps that read as one conversation, rather than four people asking for time.
| Without Unify | With Unify |
|---|---|
| Each step is written on its own, so four steps carry four different angles | One thesis per account, carried across all four steps |
| The call goes first, before anything has come back, and lands cold | Email, then social, then a call once something comes back |
| The spacing is whatever the template came with | Two days, then three: one conversation rather than a nuisance |
| The first batch enrolls the moment somebody clicks save | The first batch waits for approval, then caps and exclusions keep it inside the lines |
Start from this prompt
Make it your own in Unify, then review the results.
Build a 4-step sequence for my target accounts that mixes email, a LinkedIn connection request and a call, personalized with a signal for each account.
How it changes by who you sell to
- Software
- Email and LinkedIn carry most of the weight, and the call step is a courtesy. Ask for two email steps, one LinkedIn step and a call only for accounts with a direct number.
- Manufacturing
- Phone still outperforms email at plant level, and plant contacts rarely live on LinkedIn. Ask for the call step first, email second, and drop LinkedIn for anyone whose title is at a site.
- Healthcare
- Clinical leaders are hard to reach by phone, so email leads and the call comes late. Ask for three email steps and a call only after a reply, and keep every mention of patients out of the copy.
- Financial services
- Compliance shapes what can be said on each channel. Ask for formal email steps with no performance claims, no LinkedIn for regulated roles, and a call step that references the email rather than pitching.
Next in outreach and meetings
+2Call follow-upCreate call tasks for repeat email openersFind people who repeatedly opened without replying, then review who warrants a call.
+4Meeting prepGet ready for a first meetingTen tabs of research, or one prompt and a brief with sources against each claim.- CallingStart a calling session with your best leadsTwenty leads with a verified number, in the order to call them, each with one line to open on. Start dialing instead of building the list.
Connect what this workflow uses
Each guide covers the connection, what Unify reads and writes, and what to check before the first run.
Questions about this workflow
Which channels can a sequence use?
Email through Gmail or Outlook, LinkedIn connection requests, and calls. The starting prompt mixes all three across four steps.
How is each step personalized?
Unify opens each account on a signal it found, such as a hire from PredictLeads or a new tool, and writes the step around it rather than around a template.
Does it send automatically?
Sequences are drafted for your review. Nothing goes out until you approve the steps and start the sequence.
What if a contact has no direct number?
Ask for the call step only where Findymail returns a verified number; the sequence drops the call for everyone else.