Respond.io
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
A side-by-side editorial comparison of LiveAgent and Plivo — release velocity, themes, recent moves, and the top alternatives to consider.
Two maintained branches, a build-stamp version scheme, and a steady diet of defect fixes.
LiveAgent ships from two branches at once, 5.67 and 5.66, and tags each build with a timestamped version string rather than a release name. The window is almost entirely defect work: chat lifecycle bugs, a shared-mailbox OAuth timeout on large tenants, Gmail quote parsing, and several database write loops. The most recent pair are same-day builds on both branches carrying an overlapping fix set.
Plivo's CPaaS hygiene work — but the feed is now over a year stale.
The most recent entry is from January 2025, and the rest land between August 2024 and November 2024. The visible work covers CPaaS table-stakes: dynamic usage-based pricing, automated India-number activation, self-service security/profile management, expanded CNAM coverage, voice-invoice transparency, and Verify API parameter additions for branded auth flows.
LiveAgent ships from two branches at once, 5.67 and 5.66, and tags each build with a timestamped version string rather than a release name. The window is almost entirely defect work: chat lifecycle bugs, a shared-mailbox OAuth timeout on large tenants, Gmail quote parsing, and several database write loops. The most recent pair are same-day builds on both branches carrying an overlapping fix set.
The recent fixes have shifted from user-visible bugs toward the cost of running the system: a chats overview that re-ran a full grid query every ten seconds per open screen, a language synchroniser writing on every read, and uncached language metadata. That is a performance pass on hot paths rather than feature work. The dual-branch pattern is stable, with the older 5.66 line receiving a subset of each fix set as backports.
Expect the branch pair to continue, with 5.66 receiving narrower backports of whatever 5.67 fixes, and further work on query and write amplification now that three such issues have been addressed in one build.
The most recent entry is from January 2025, and the rest land between August 2024 and November 2024. The visible work covers CPaaS table-stakes: dynamic usage-based pricing, automated India-number activation, self-service security/profile management, expanded CNAM coverage, voice-invoice transparency, and Verify API parameter additions for branded auth flows.
What's in the feed is a steady but unglamorous platform-broadening cadence — geo expansion (India), regulatory plumbing (CNAM, toll-free verification), and pricing flexibility — with no AI, no agentic-voice, no LLM-meets-telephony moves. The bigger signal is the silence: a 16-month gap between the last entry and now, which either means the changelog has moved or the public-facing release stream has gone quiet.
If Plivo is still shipping, the next directional move would almost certainly involve AI voice agents or LLM-powered messaging — every CPaaS peer (Twilio, Vonage, Telnyx) has made that pivot. The absence of any such signal in this batch is consistent with a feed that's no longer the primary changelog surface; the next confirmation will be either a new release stream appearing or a long-overdue entry breaking the silence.
Other Support products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either LiveAgent or Plivo.
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
Live Helper Chat keeps adding the oversight surfaces a supervised support floor needs.
Post-rebuild Sleekplan is adding the objects a feedback board never had: docs and components.
Plain built an autonomous support agent, and has now built the controls to trust it.
Comm100 publishes steadily about AI support — none of it is Comm100 shipping anything.
Hatz sells through MSPs, and its roadmap has started to serve the partner more than the end user
See all LiveAgent alternatives → · See all Plivo alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. LiveAgent is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. LiveAgent is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Support products to evaluate alongside.
Top LiveAgent alternatives in Support are ranked by recent ship velocity. Browse the "LiveAgent alternatives" section above for the current picks, or visit /alternatives/liveagent for the full list with editorial commentary on each.
Top Plivo alternatives in Support are ranked by recent ship velocity. Browse the "Plivo alternatives" section above for the current picks, or visit /alternatives/plivo for the full list with editorial commentary on each.