iTop
iTop's 3.3 beta stretches the CMDB to containers and finally ships non-English sample data
A side-by-side editorial comparison of Live Helper Chat and Plain — release velocity, themes, recent moves, and the top alternatives to consider.
Live Helper Chat is instrumenting itself — dashboards, caching and cached archive lookups now lead every release
Six releases from March to July, each bundling security, performance and widget work. The most substantive additions are department and operator performance dashboard widgets with configurable columns and update intervals, backed by cron aggregation, plus caching improvements across online-operator retrieval, department prefill and chat archive range checks. Security appears repeatedly: MIME validation across download endpoints, tightened chat permission checks, and CSP parser work.
Sidekick went from in-thread helper to an operator with skills and any MCP server it needs
Plain spent the last month converting Sidekick from an assistant that answers inside a thread into something that runs work on its own. It got a dedicated page as the first sidebar item, where sessions are started and the tools it can reach are managed. It can take actions across connected tools and inside Plain. Workflows now trigger it automatically when a thread matches conditions, and can run on a schedule with no thread at all. The two newest releases make it extensible: reusable skills authored once and shared workspace-wide, and connections to any MCP server rather than only Plain's built-in integrations.
Six releases from March to July, each bundling security, performance and widget work. The most substantive additions are department and operator performance dashboard widgets with configurable columns and update intervals, backed by cron aggregation, plus caching improvements across online-operator retrieval, department prefill and chat archive range checks. Security appears repeatedly: MIME validation across download endpoints, tightened chat permission checks, and CSP parser work.
The product is turning operational data about itself into a supervisor-facing feature — response times, wait times, online and offline time — while the caching work exists to make those aggregates cheap on installations with large chat archives. Alongside it, the bot and REST surface gained streaming and chunked response handling, which is what conversational integrations require.
Expect the performance statistics surface to keep expanding with more aggregated metrics, and the archive caching work to continue as the datasets those widgets query keep growing.
Plain spent the last month converting Sidekick from an assistant that answers inside a thread into something that runs work on its own. It got a dedicated page as the first sidebar item, where sessions are started and the tools it can reach are managed. It can take actions across connected tools and inside Plain. Workflows now trigger it automatically when a thread matches conditions, and can run on a schedule with no thread at all. The two newest releases make it extensible: reusable skills authored once and shared workspace-wide, and connections to any MCP server rather than only Plain's built-in integrations.
The sequence is deliberate: give the agent capability, then autonomy, then extensibility. With arbitrary MCP servers and workspace skills, the ceiling on what Sidekick can do stops being set by Plain's integration roadmap and starts being set by what each customer wires up and writes down. The support product around it is being reshaped to match — workflows are becoming the trigger layer for agent work rather than routing rules for humans, and shareable workflow links suggest those definitions are meant to circulate between teams.
Expect skills and MCP connections to converge into something packaged — shared or templated skill sets that ship with the tools they assume — and for the agent's autonomy to need governance next, since an agent that acts across arbitrary MCP servers on a schedule raises approval and audit questions the current releases do not address.
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 Live Helper Chat or Plain.
iTop's 3.3 beta stretches the CMDB to containers and finally ships non-English sample data
Zoho's own LLM is being wired into ITSM one data center and one assist at a time.
Knowmax's feed is a thought-leadership blog arguing AI fails without knowledge — no releases in it.
The tracked ProProfs Help Desk feed is an SEO blog — no product releases are visible in it.
Hatz AI chases the model catalog weekly, but the MSP control plane is the real build.
Thread is making the ticket, not the channel, the place an MSP conversation actually lives.
See all Live Helper Chat alternatives → · See all Plain alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Plain is currently shipping more aggressively (velocity 7.5 vs 2.5), with 2 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. Plain is currently shipping more aggressively (velocity 7.5 vs 2.5), with 2 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 Live Helper Chat alternatives in Support are ranked by recent ship velocity. Browse the "Live Helper Chat alternatives" section above for the current picks, or visit /alternatives/livehelperchat for the full list with editorial commentary on each.
Top Plain alternatives in Support are ranked by recent ship velocity. Browse the "Plain alternatives" section above for the current picks, or visit /alternatives/plain for the full list with editorial commentary on each.