Twilio
Twilio fills out EU data residency, RBAC, and unified messaging APIs
A side-by-side editorial comparison of Kayako and Thread — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Kayako | Thread |
|---|---|---|
| Sector | Support | Support |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | customer-support, legacy-product, stalled-changelog, communication-silence | voice-ai, msp, helpdesk, triage-agent |
| Last editorial update | 1mo ago | 2d ago |
| Website | Visit → | — |
Kayako's public changelog has been silent since mid-2022 — the radar is showing a stalled product.
Kayako has not posted a public changelog entry since June 2022. The most recent communication was a CEO apology over a performance incident and a series of link-only release-notes posts pointing to a Help Center article. The visible operational picture is an established customer-support product no longer broadcasting product motion.
Thread is turning its MSP helpdesk into a full Voice AI platform, now reaching outbound calls.
Thread is an AI helpdesk for MSPs built around a Triage Agent and Voice AI that answers and routes inbound calls into PSA tickets. Recent work pushes on three fronts: voice (transcription, custom farewells, speech controls), the Triage Agent (structured testable rules), and visibility (a six-dashboard analytics suite). The product sits tightly against partners' PSAs.
Kayako has not posted a public changelog entry since June 2022. The most recent communication was a CEO apology over a performance incident and a series of link-only release-notes posts pointing to a Help Center article. The visible operational picture is an established customer-support product no longer broadcasting product motion.
Direction is hard to read from public changelog activity alone, but the trajectory implied by the silence is unmistakable: either the product moved its release communication elsewhere, or development pace slowed enough to stop justifying a regular changelog. Either way, prospects watching only the public surface see no momentum.
Without renewed public activity, Kayako will continue to be perceived as legacy in a category where Zendesk, Intercom, and HelpScout are publishing prominently. A customer-facing changelog refresh would be the lowest-effort signal to send, and is the most likely next move if the product is in fact still under active development.
Thread is an AI helpdesk for MSPs built around a Triage Agent and Voice AI that answers and routes inbound calls into PSA tickets. Recent work pushes on three fronts: voice (transcription, custom farewells, speech controls), the Triage Agent (structured testable rules), and visibility (a six-dashboard analytics suite). The product sits tightly against partners' PSAs.
Voice is becoming Thread's center of gravity. After building out inbound handling, custom agents, and transcript-to-PSA delivery, the latest releases add outbound calling and finer call controls - the product is becoming a full telephony layer for MSP service desks, not just an inbound attendant.
Expect deeper outbound workflows next - agent-initiated callbacks, dialer-style queues, and analytics that tie outbound call volume to the ROI dashboards Thread just shipped.
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 Kayako or Thread.
Twilio fills out EU data residency, RBAC, and unified messaging APIs
Spiceworks remains an IT-news desk, not a product — its feed is editorial
Supportbench's feed is a daily helpdesk-migration blog, not a changelog
Front is rebuilding the shared inbox around AI agents and omnichannel reach.
Service Fusion's feed is field-service marketing and partner content, not release notes.
Respond.io is pushing AI agents deeper into every stage of the customer conversation.
See all Kayako alternatives → · See all Thread alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Thread is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Thread is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Kayako alternatives in Support are ranked by recent ship velocity. Browse the "Kayako alternatives" section above for the current picks, or visit /alternatives/kayako for the full list with editorial commentary on each.
Top Thread alternatives in Support are ranked by recent ship velocity. Browse the "Thread alternatives" section above for the current picks, or visit /alternatives/thread for the full list with editorial commentary on each.