Keep support steady after an acquisition

After a company is bought, customers worry about prices, features and whether anyone will still answer. Support is where those worries show up first.

Last reviewed October 14, 2026

Tell customers before they guess

Publish a short note that says what is changing, what is not and who to contact. Silence is read as bad news.

Do not change the support address, chat or login without notice. Forward old addresses for as long as customers use them.

Draft replies for pricing, contracts, data handling and roadmap, and have the right people approve them.

Move the queues one at a time and keep the old inbox forwarding. A big-bang switch risks lost tickets.

Tag tickets that mention the change and review them weekly. A rise in cancellations needs a quick response.

Support hears about it from customers. Give agents the facts first, so they are not learning from the same messages.

What is changing, what is not and who to contact. Short and early beats long and late.

No. Move in stages, keep old addresses forwarding and check nothing is lost between systems.

Tag tickets about the change and review the tags every week for rising cancellations or confusion.

Written by Flatdesk, a help desk for small support teams at one flat price per agent. Try it free for 14 days, no card.