The CEO calls an all-hands. "We've been acquired by [BigCo]. The deal closes in 90 days. Until it's publicly announced, nobody can discuss this with customers, partners, or the press."

Two days later, a customer emails support: "Heard a rumor you're getting acquired by [BigCo]. What happens to our contract? Are you going to change the product? Should we be looking for alternatives?"

Your agent stares at the screen. They know about the acquisition. They can't confirm it. They can't deny it (that's a lie, which creates legal liability). They can't say "I can't discuss that" (which is confirmation). And they can't ignore the email (the customer will escalate).

Welcome to acquisition support.

The Communication Blackout

During an acquisition, the acquiring company's legal team controls all external communication. The rules are strict and the consequences for violating them are real (deal breakage, SEC violations for public companies, contractual penalties).

For support teams, this creates an impossible situation. Customers have questions that you have answers to but aren't allowed to share. The standard support values (transparency, honesty, helpfulness) collide with legal constraints.

The blackout typically lasts from the moment the deal is signed until the public announcement (which might be same-day or might be 30 to 90 days later). During this period, your support team needs a playbook.

The Playbook

Before the announcement, coordinate with legal and communications to create approved responses for the most likely customer questions:

"I heard you're getting acquired." Response: "We don't comment on rumors about corporate matters. What I can tell you is that we're fully committed to supporting you and our product. Is there something specific I can help you with today?"

This response doesn't confirm, doesn't deny, and redirects to the customer's actual needs. It's not satisfying. But it's the best you can do within the constraints.

"Should I be worried about my contract?" Response: "Your current agreement with us is fully active and will continue to be honored. If anything changes that affects your account, we'll reach out proactively."

This is true during the blackout (the deal hasn't closed, contracts are unchanged) and sets the expectation of proactive communication (which you should deliver after the announcement).

"Are you going to raise prices?" Response: "We have no pricing changes to announce. Your current pricing is in effect." Again, true during the blackout. If pricing will change post-acquisition, you'll communicate it then.

The Announcement Day

On announcement day, your support volume will spike. The spike depends on how your customer base learns about the acquisition:

If you announce via email to customers first (before press): moderate spike, mostly positive or curious. Customers feel respected because they heard from you directly.

If customers learn from a press article or social media: large spike, mostly anxious. "Why didn't you tell us?" is the dominant sentiment.

Always announce to customers first, even if the gap is only 2 hours before the press release. That 2-hour head start signals respect.

The announcement email should answer the questions customers will ask: What changes? (Nothing right now.) Will the product continue? (Yes.) Will pricing change? (Not immediately; if it will eventually, say so.) Who can they contact with questions? (Support, with expected response times.)

Have your full support team online on announcement day. Pre-write responses for the top 10 expected questions. Use AI to auto-respond to the common ones (Supp can classify "acquisition question" intents and provide the approved response) and route complex ones to senior agents.

The 90 Days After

The announcement spike subsides within a week. Then comes the slow burn of integration questions that trickle in over the next 90 days.

"Will you integrate with [BigCo's] product?" Usually yes, eventually. Be honest about timelines if you have them. "We're exploring integration, but I don't have a timeline yet" is fine.

"Is [person] still at the company?" Be careful here. If the CEO left, saying "we can't comment on personnel changes" while their LinkedIn says "Former CEO" looks evasive. If they left, it's public information. Acknowledge it.

"I chose you because you were independent. Are you still the same product?" This is the emotional question. The customer isn't asking about features. They're asking about identity. "The team that built [product] is still here, working on the same product, with the same values. The acquisition gives us more resources to do that faster." If that's true, say it. If it's not (if the team was gutted post-acquisition), don't lie.

The Long Game

How you handle support during an acquisition determines whether your existing customers stay through the transition or leave for a competitor. The competitor is actively targeting them. They're running ads that say "Worried about [product's] acquisition? Switch to [us]."

Every support interaction during this period is a retention conversation. The customer who contacts support with a question about the acquisition is a customer who's evaluating whether to stay. A fast, honest, specific response keeps them. A slow, evasive, corporate response pushes them toward the competitor's ad.

AI helps by handling the volume. Supp classifies acquisition-related questions and provides approved responses instantly. The customer gets an answer in seconds instead of waiting in a queue that's 5x longer than normal. The human agents focus on the complex, emotional, account-specific questions that need personal attention.

The acquisition is stressful for everyone: the founders, the team, and the customers. Support is the stabilizing force. When everything else is uncertain, fast and honest support says "we're still here, we still care, and we're going to take care of you."

That message is worth more than any integration roadmap or press release.