# What to do with LinkedIn sales when your product goes down
> How to handle active LinkedIn conversations and scheduled demos when your software goes down, so you keep the prospect's trust and the deal alive.
- HTML: https://getkinlead.com/managing-linkedin-sales-during-product-outages
- Markdown: https://getkinlead.com/managing-linkedin-sales-during-product-outages.md

**Short answer:** Pause any automated outreach that sends people to a broken product, then message everyone with a demo booked or an active trial before they find the outage themselves. Say what broke, what it stops them doing, and when you will next update them. Offer a new time or a manual workaround rather than hoping the fix lands first.

## Pause everything that sends people to the product

The engineering team sees a broken service. You see a list of people who were about to decide whether to buy from you. Those are different problems running on different clocks, and only one of them is yours to fix.

A prospect who hits a dead dashboard on the morning they planned to test the integration doesn't think 'outage'. They think the product is unfinished, or that the company is small enough to break. Your status page doesn't reach them, because they aren't checking it. The message you send is the only thing standing between an outage and an opinion.

The stakes depend on where the prospect sits. Someone evaluating you has nothing invested and can walk. Someone already paying has a team asking why the tool is down. Both need a message, but not the same one.

So before you write a single apology, stop the machine. Every scheduled message, connection request and follow-up that points at the product is now pointing at a dead link.

1. **Turn off scheduled outbound.** Pause every campaign and sequence. A new lead who lands on a broken page doesn't come back later to check whether you fixed it.
2. **Read the next 24 hours of your calendar.** Write down every demo, discovery call and onboarding session. These people get a personal message, not a broadcast.
3. **List anyone in a trial or onboarding.** Pull the accounts that were active in the last few days. They are the ones most likely to be staring at the error right now.
4. **Switch automatic replies to hand-off.** If your outreach tool writes replies on its own, set it so a person reads each one. An AI cheerfully asking about their goals while the product is down reads badly, and they will remember it.

> Ten minutes of pausing buys you the room to do the rest properly.

## Who to message first, and in what order

You can't message everyone at once and you shouldn't try. Work down this list and stop when the product is back.

Write the list before you write the messages. Deciding who matters while you're typing is how the demo at 3pm gets missed.

- Demos in the next 24 hours. They have a slot in their calendar and a reason to show up. A warning now saves them the trip and saves you the call.
- Anyone in a trial who was active this week. They're inside the product and will hit the error before you finish writing.
- Prospects who asked a question in the last day and haven't had an answer. Silence plus an outage reads as a company in trouble.
- Everyone else in an active conversation. One short note is enough. They don't need a status report.
- Cold leads and new connections. Leave them alone until the product works. Nothing you could say to them is worth the first impression of a broken link.

| | Timing | What they need |
| --- | --- | --- |
| Demo in the next 24 hours | A message within minutes, two new times, and a fresh invite |
| Trial active this week | Confirmation their account is fine and the problem is platform-wide |
| Open question from yesterday | An answer or a straight 'I'll come back to this at 4pm' |
| Cold lead or new connection | Nothing until the product works again |

## How to word the message

Vague language makes an outage bigger than it is. 'Technical difficulties' invites the reader to imagine the worst version: a company running out of money, a rewrite, a product that never worked.

Say what broke, what it stops the reader from doing, and when they will hear from you next. If you don't have a fix time, give an update time. That is the part people actually need, because it tells them whether to wait or get on with their day.

If you don't know the cause yet, say that too. 'The dashboard is down, we don't know why yet, I'll have an answer by 4pm' is a complete message. Guessing at a cause and being wrong costs more than admitting you don't know.

Apologize once, then give information. Three apologies in a row reads like panic.

**Vague and reassuring**

- We are experiencing some technical difficulties and will be back soon.
- Sorry for any inconvenience caused.
- Our team is working hard to resolve the issue.

**Specific and useful**

- Our API is down, so the dashboard won't load. Nothing you did caused it.
- The team is rolling back a database migration. I'll message you at 2pm whether or not it's fixed.
- You were going to test the Salesforce sync today. That's the part that's blocked.

## What to do about a demo in the next few hours

Don't gamble on the fix landing before the call. If it lands, warning them cost you nothing. If it doesn't, you spend the call narrating a broken screen and apologizing for their time.

Message as soon as you know. Offer two specific times instead of asking what suits them, and send the new invite before the old slot passes so it doesn't sit in their calendar as a reminder of the day you cancelled.

- **you:** Hi Sarah, we've got an outage that affects the demo environment. I'd rather move our call than show you a broken screen.
- **them:** Thanks for the heads up. I was about to log in.
- **you:** Can we do tomorrow at the same time, or later this afternoon if the fix lands early? I'll send the invite as soon as you pick one.

> Rescheduling costs you an hour. A demo where nothing loads costs you the reason they were going to buy.

## Prospects already in a trial or mid-conversation

These are the people most likely to be inside the product right now, and the most likely to conclude it's broken for them specifically. A prospect who thinks their account is corrupted starts looking at alternatives. One who knows it's a platform issue waits.

Reach out before they reach out. A short message that names the problem and confirms their account is fine removes the doubt that makes people churn.

If someone was close to signing, tell them plainly whether the outage affects anything they were about to rely on. A delay you explain is a delay. A delay they discover is a doubt.

| | What to do | Why it works |
| --- | --- | --- |
| They report a bug | Tell them it's platform-wide and their account is fine | Stops them hunting for a setting they think they broke |
| They ask for a status | Give the next update time, even with no fix time | A promise you can keep beats a guess you can't |
| They question stability | Name the cause in one sentence and what changes after the fix | A specific cause reads as engineering. A vague one reads as chaos |
| They go quiet | Send one short note when the product is back, with a link | Silence after an outage reads as a company that's struggling |

## After the fix, the follow-up that keeps the deal

The outage ends. The memory of it doesn't. The follow-up is where you either close the loop or leave the prospect with a story about the day your product broke.

Send it within a day of the fix and reference the specific thing they were trying to do. 'We're back online' is a status update. 'The Salesforce sync you were testing on Tuesday works now, here's the screen you were looking for' is a reason to come back.

> Tell them what changed. A prospect who hears 'we added a check that would have caught this' has a reason to trust the next release. One who hears nothing assumes it can happen again.

```
Hi {first name}, we're back. The {specific feature} you were testing on {day} works now, and the fix for {cause in plain words} is live.

Here's the {link or screenshot} so you can pick up where you left off. If you'd rather I walk you through it, I have {two times} open.

Sorry again for the interruption. {one line on what changed so it doesn't happen twice}
```

## Doing this with Kinlead

Any campaign can be paused, so nothing new goes out while the product is down. Switch the running campaigns to hand-off mode so a person answers every reply instead of the AI, and the first reply from each prospect lands in one [unified inbox](/features/unified-inbox), sorted with interested replies at the top.

When the product is back, resume the campaigns and work through the replies you handled by hand. Everything a prospect sent during the outage is still in that inbox, so nothing gets lost in the gap.

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Handling a prospect who asks for a discount](https://getkinlead.com/handle-prospect-asking-for-discount.md)

## Common questions

**Should I apologize in every message about the outage?**

Apologize once, clearly, then give information. Repeating it makes the situation sound worse than it is and puts the focus on you instead of on what the prospect needs.

**When should I tell a prospect the product is down?**

As soon as you know it affects something they were going to do. Being the one who tells them is worth far more than hoping they don't notice.

**What if the outage lasts more than a day?**

Send one update at the same time each day, even when there's nothing new. A predictable update schedule is what keeps a long outage from turning into a trust problem.

**Should I offer a discount after an outage?**

Not as a first move. Offer the working product and a clear explanation first, and only talk about money if they raise it.

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