# LinkedIn scripts for cross-selling new features
> Scripts and message examples for telling existing customers about a new feature on LinkedIn, matched to how each account actually uses the product.
- HTML: https://getkinlead.com/linkedin-scripts-for-cross-selling-features
- Markdown: https://getkinlead.com/linkedin-scripts-for-cross-selling-features.md

**Short answer:** Don't broadcast a feature to every customer at once. Send a direct message that starts from something the customer said or did, then put the feature in the second sentence as the answer to that problem. The goal is a reply, not an announcement.

## Why the announcement message fails

Most founders announce a feature the way they'd write a changelog entry. Same wording, same link, sent to everyone they've ever closed. The customer reads it, thinks it sounds fine, and goes back to whatever they were doing. Nothing in the message connects the feature to their actual week.

A message works when it starts from something the customer already said or did. If they mentioned during onboarding that reporting eats their Friday afternoon, that's your opening line. The feature shows up in the second sentence, as the answer to that problem.

There's a second cost to the broadcast. It looks exactly like cold outreach. Your customer has no reason to believe you wrote it for them, because you didn't. Once they've received three of those, they stop opening your messages altogether, which makes the next real conversation harder.

**The broadcast**

- We're excited to announce our new Analytics Dashboard, with real-time tracking and custom reports. Check it out here: [link]
- Big news! We just launched a Slack integration to help you stay productive. Let me know if you want to try it.

**The direct message**

- You mentioned reporting takes about four hours a week. We built something that removes most of that. Want to see it on your own data?
- You're onboarding three people this month. We added bulk invites, which should cut that setup down to a few minutes. Should I show you where it lives?

## Segment customers before you write a word

The same script sent to a daily user and to someone who hasn't logged in since March will land badly with both. Before you open LinkedIn, split your customer list by how they actually use the product.

For a small base, a spreadsheet is enough. Sort by last login, by which features they touch, and by how much they pay. For anything larger, pull the data from your product database rather than guessing from memory.

Leave out anyone who's midway through a support issue or a renewal negotiation. A feature message during either of those reads as tone deaf, and it can complicate a conversation someone else on your team is already having.

1. **Export the list.** Pull names, company, and email from your database or CRM. Include last login date and the features each account uses.
2. **Sort into three or four groups.** Daily users of one feature, accounts that went quiet, accounts that just upgraded, and accounts with an open support thread. Keep the groups small enough that you can write a different first line for each.
3. **Match to LinkedIn profiles.** Find each person's profile URL. If you're not connected, send a plain connection request with no pitch, wait for the accept, then send the message a few days later.
4. **Write the first line per group.** One sentence that references their usage or their stated goal. The feature goes in the second sentence, never the first.

## Scripts for three kinds of customer

The wording changes with the group. A heavy user wants to know what gets faster. A quiet account needs a reason to come back. An account that pays you the most wants to feel like they're getting something before everyone else.

Swap the bracketed parts for the specific outcome, not the feature name. 'Bulk invites' means nothing on its own. 'Onboarding three people in one go' means something the customer can picture.

For the quiet account, don't lead with the silence. 'I noticed you haven't logged in' sounds like a teacher marking attendance. Lead with the problem the update solves and let them decide whether it's relevant now.

| | Customer type | What they want | Message |
| --- | --- | --- | --- |
| Power user | Less manual work | You're using [feature A] most days. We added [feature B], which does [the step they currently do by hand]. Want a quick look? |
| Quiet account | A reason to return | We rebuilt [feature A] so it handles [the problem they mentioned]. Is that still on your list for this quarter? |
| High-value account | Early access | We're giving a few accounts [feature C] before it goes out. Given your focus on [goal], you'd probably find the first version useful. Want me to switch it on? |

## Making the message sound like a person wrote it

Two things give a template away: the opening line and the length. If the first sentence could be sent to anyone, the customer stops reading. If the message runs past four lines, it starts to feel like work.

Keep the ask small. 'Want to see it?' is easier to answer than 'Would you be open to a 30-minute call to walk through the new reporting module and how it fits your workflow?' The smaller the ask, the more likely you get a reply you can work with.

Read it out loud before you send. If you wouldn't say the sentence to someone sitting across from you, rewrite it. That test catches most of the stiffness that templates introduce.

```
Hi {first name},

{One sentence about something specific they said or did.}

We added {feature} that {outcome, in their words}. {One line on what changes for them.}

Want me to send a short video, or would a 10-minute call be easier?
```

## What to do when they reply

The reply is the moment most founders lose the thread. They send a help center link and a paragraph of instructions. The customer opens it later, gets distracted, and never comes back.

Give them one small next step. A short screen recording beats a call for most people because they can watch it while they're already in the product. Offer the call as a second option.

If they say 'not right now', take it at face value and ask what would need to change. That answer tells you whether to follow up in a month or drop it. Either way, you've learned something about the account.

- **them:** Yeah, that could be useful. How does it work?
- **you:** It pulls your existing reports into one view, so you stop rebuilding them each week. I can send a two-minute video or we can do a quick call. Which is easier?
- **them:** Video is fine.
- **you:** Here it is. I recorded it on an account set up like yours, so the numbers should look familiar. Does that cover the Friday problem, or is there a piece missing?

## Following up once, then stopping

One follow-up is reasonable. A second is pushing it. If a customer doesn't reply to two messages about a feature, they either don't need it or they're too busy to care right now. Both are fine.

Make the follow-up carry something new. A tip, a screenshot of how another customer set it up, or a note that the feature is now included in their plan. Repeating the first message just adds noise.

Keep a simple record of who you've messaged and when. A spreadsheet column is enough. Without it you'll either double-message the same person or forget the account that said to ask again next quarter.

> If a customer doesn't reply to two messages about a feature, stop. Send the next one when there's something new to say, not because a calendar told you to.

## Doing this with Kinlead

If your customer list is long enough that manual tracking gets messy, you can run this in Kinlead. Import the LinkedIn profile URLs of your customers from a CSV into a [lead group](/features/lead-groups-and-scoring), then point a campaign at that group.

Put your cross-sell scripts into the campaign's sales playbook so the AI writes from your wording rather than a generic pitch. Set the campaign to hand the conversation to you at the first reply, so the opening message goes out on its own and you take over when the customer answers.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**Should I post the update on my feed or send a direct message?**

Both, for different reasons. A post tells your whole network the feature exists. A direct message is what gets a specific customer to try it.

**How often can I message existing customers about new features?**

LinkedIn doesn't publish a number for this, and the real limit is patience. Message when the feature solves something they already told you about. Skip the small updates.

**What if the customer doesn't respond to the first message?**

Send one follow-up with something new in it, like a tip or a short video. If that gets no reply, leave it and pick it up when you have a reason.

**Is email better than LinkedIn for this?**

Email works for release notes that go to everyone. LinkedIn works when you want a reply from one specific person, because it lands where they already spend time.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
