# Starter sequence: multichannel B2B

Our recommended Email + LinkedIn sequence in Victoria AI, a blank request with a 10-day window, then two branches that reference each other.

This is a starting point, not a finished campaign. Replace the bracketed offer and the sign-off with your own, and keep only claims you can back up. It follows our recommended Email + LinkedIn shape: a profile view and a blank connection request, then message, email, message, email, message for people who accept within about 10 days, and four emails for people who don't. Every touch after the first ties back to the other channel.

It uses one AI Personalization field, `{recent_news}`, in the first email on the **No** path. Create it before activating (see "Create the AI Personalization field" below), or rewrite that line.

## The multichannel starter sequence

```json sequence
{
  "variation_a": [
    { "id": 1, "type": "view_profile", "delay": 1 },
    { "id": 2, "type": "linkedin_connection", "message": "", "delay": 10 },
    {
      "id": 3,
      "type": "conditional",
      "conditionalType": "linkedin_connected",
      "isConditional": true,
      "delay": 1,
      "branches": {
        "yes": [
          {
            "id": 4,
            "type": "linkedin_message",
            "message": "Hey {first_name}, I help [specific kind of company] [do one specific, niche thing] by [a few words on how].\n\nMind if I send over [the give: a short teardown / a sample] for {company}?",
            "delay": 2
          },
          {
            "id": 5,
            "type": "email",
            "subject": "from LinkedIn",
            "content": "Hi {first_name},\n\nI sent you a note on LinkedIn too, so I'll keep this short.\n\nI offered to send [the give]. It takes [a few minutes] to read, and it's yours whether or not we ever talk.\n\nWant it?\n\nJordan",
            "delay": 3
          },
          {
            "id": 6,
            "type": "linkedin_message",
            "message": "{first_name}, I sent you an email as well, so here's the short version.\n\nOne thing that's working for [teams like yours] right now: [one concrete idea, in a line].\n\nHappy to send [the give] if it's useful.",
            "delay": 5
          },
          {
            "id": 7,
            "type": "email",
            "subject": "an idea for {company}",
            "content": "Hi {first_name},\n\nA second idea to go with my LinkedIn message: [another idea or a resource, in two lines].\n\nIf it's useful, I can [make a quick intro / share how teams like yours set it up].\n\nJordan",
            "delay": 7
          },
          {
            "id": 8,
            "type": "linkedin_message",
            "message": "Last note from me, {first_name}, here and by email. If the timing's off, no problem at all. The offer of [the give] stands whenever it's useful.",
            "delay": 0
          }
        ],
        "no": [
          {
            "id": 9,
            "type": "email",
            "subject": "question about {company}",
            "content": "Hi {first_name},\n\nNoticed {recent_news}.\n\nIs [the thing your offer helps with] on your list this quarter?\n\nI sent you a connection request on LinkedIn too, in case that's easier.\n\nJordan",
            "delay": 2
          },
          {
            "id": 10,
            "type": "email",
            "subject": "[the give] for {company}",
            "content": "Hi {first_name},\n\nI'd still like to connect on LinkedIn, but email works too.\n\nI help [specific kind of company] [do one specific, niche thing] by [a few words on how]. Mind if I send over [the give]?\n\nJordan",
            "delay": 3
          },
          {
            "id": 11,
            "type": "email",
            "subject": "an idea for {company}",
            "content": "Hi {first_name},\n\nNo need to reply to this one. One thing that's working for [teams like yours]: [one concrete idea, in a line or two].\n\nIf LinkedIn is easier for you, my connection request is there.\n\nJordan",
            "delay": 5
          },
          {
            "id": 12,
            "type": "email",
            "subject": "last note",
            "content": "Hi {first_name},\n\nI'll leave it here so I'm not crowding your inbox or your LinkedIn.\n\nIf [the problem] comes up later, just reply. The offer of [the give] still stands.\n\nJordan",
            "delay": 0
          }
        ]
      }
    }
  ],
  "variation_b": []
}
```

Replace "Jordan" with the sender's name, and every bracketed phrase with your own words.

## Create the AI Personalization field

In the Sequence editor, open step 9 (the first email on the **No** path), select **Insert Variable → AI Personalization → +**, and create:

- **Field Name**: `recent_news`
- **AI Instructions**: "Name one specific recent launch, announcement or milestone from the company's website, as a short phrase that can follow 'Noticed' in a message. No generic praise."
- **Fallback value**: "the growth at your company" (or any phrase that reads well after "Noticed")
- **Data Sources**: **Website**

See [Personalization that works](https://docs.versionseven.ai/playbook/personalization-instructions).

## Why it works

- **Step 1, View Profile**: a light first touch. The prospect may see your name before the request arrives.
- **Step 2, blank Connection Request**: in our testing, requests with no note were accepted 10% to 30% more often, because a blank request carries no angle or ask. Acceptance is what unlocks LinkedIn messages.
- **The timing of the acceptance window**: Victoria checks the connection once, when the wait after the request ends, and the branch's own wait only spaces the check from the first step on either path. So the 10-day wait sits on step 2, and the branch waits 1 day. A lead has about 10 days to accept, and the first message or email goes out the day after the check. The built-in template instead waits 5 days on the request and 5 days on the branch: its first branch step lands at a similar time, but anyone who accepts after the check goes down **No**.
- **Step 4, first LinkedIn message**: the "I help X do Y by Z" opener with a give-first CTA. See [Openers that get replies](https://docs.versionseven.ai/playbook/openers).
- **Steps 5 to 8, Yes path**: message, email, message, email, message. Each one mentions the other channel ("I sent you a note on LinkedIn too", "I sent you an email as well"), so it reads as one conversation, not two strangers writing. Every touch gives something: the offer, an idea, a second idea, the offer left open.
- **Steps 9 to 12, No path**: four emails for people who didn't accept, so every lead is reached. The first uses the question opener with the AI field, and each one mentions the LinkedIn request so the two channels still tie together.
- **Delays**: Yes path 2, 3, 5 and 7 days; No path 2, 3 and 5 days. Start close together and back off steeply. The last step on each path waits 0 because nothing follows it.
- **Throughout**: no links, no unprovable claims, no slop, short first-person sentences and one small ask per message. When someone replies, the sequence stops and the Appointment Setter can take over: deliver the give, follow up and work the deal.

To test a second angle, turn on [A/B testing](https://docs.versionseven.ai/help/ab-testing) and change the opener and the give in Variation B, not just the wording.
