SoundHound closed on LivePerson — check your exit path

The conversational AI vendor running your support inbox may have changed owners this week. SoundHound AI closed its acquisition of LivePerson on September 4, took LivePerson off Nasdaq, and started folding a two-decade-old enterprise messaging platform into a voice-agent company's stack. If you are a customer of either, your roadmap is now someone else's integration project.

What actually happened

Per SoundHound's announcement, the deal closed September 4, 2026. LivePerson common stock stopped trading on Nasdaq. The combined company claims 25 of the Fortune 100 as customers and a portfolio of over 750 patents. John Collins — previously LivePerson's CFO, COO, and interim CEO — becomes CFO of the combined company.

The product plan is the part to read closely. LivePerson's digital messaging infrastructure gets integrated into OASYS, SoundHound's orchestrated agent system, to run one platform across voice, web, mobile, SMS, and social. SoundHound retired LivePerson's outstanding debt at close and says the combined balance sheet is debt-free. It also states a target of over $500 million in future revenue from the existing customer base alone — a company projection, not a booking. Product rollouts are described as coming "in the coming quarters," which is the standard way to say not yet.

Why vendor consolidation matters for your business

"Integrated into OASYS" is a migration with a friendly name. Somebody is going to rewrite the routing rules, re-map the intents, and re-point the webhooks — and historically, the vendor's timeline for that is not your timeline. Meanwhile the acquiring company has every incentive to steer customers toward the platform it actually owns the roadmap for.

You do not need to panic-migrate. You need to know what leaving would cost, before you find out under pressure. Three things to do this month, whether or not you touch either vendor:

Export your conversation transcripts to storage you control, on a schedule, in a format you can read without the vendor's console. Those transcripts are your training data, your QA sample, and your evidence in a dispute. Second, write down your intents and flows as plain artifacts in your repo — a YAML file, a decision table, anything version-controlled — so the logic survives a platform change even when the runtime does not. Third, check your contract for the change-of-control and price-protection clauses, and note your renewal date. Consolidation is when quiet repricing happens.

The pattern repeats across every category: point solutions get bought, get absorbed, and get repriced. The teams that shrug it off are the ones whose business logic lives in their own repo and whose data lands in their own bucket.

Sources: SoundHound AI press release, MarTech Series.