Client-side API gets PiperX parity: same calls, now voice-ready 🎙️

The Qualified client-side API is how your web team gets Qualified to talk to the rest of your site: opening the messenger on your own triggers, reacting to conversation events, passing visitor data in, and now, prefilling a visitor's first message. If you've wired any of this into your site, here's what just changed.

If you've built anything on top of it, the good news is you don't need to touch it. The calls you already use now carry straight across to PiperX:

• open and setChatIsVisible both follow whichever messenger owns the active experience. So if a visitor lands in a PiperX conversation instead of the legacy messenger, your existing show and hide logic keeps working exactly as it did before.
• handleMessengerEvents picks up a set of PiperX-only events on top of the ones you already track: call requested, call started, call ended, mic muted, mic unmuted, and meeting offered or booked inside the PiperX conversation itself. If you're piping messenger activity into analytics, these give you visibility into voice engagement that wasn't there before.
• The Customizable Agent Launcher lets you open a conversation with your AI SDR agent and populate the first message yourself, by invoking the startChat call with a message argument. That means you can take something a visitor already typed, like a site search query, and hand it off as their opening message instead of making them repeat themselves.

All of this is live now for any org using PiperX.

📚 Full how-to: Client-side API

Let us know in the comments:

What would you want to hand off to your AI SDR agent this way, a search query, a form field, something else? And if you're tracking voice engagement, what are you hoping to learn from it?