← Back to home
Comparison · Support

Request Tracker vs Live Helper Chat

A side-by-side editorial comparison of Request Tracker and Live Helper Chat — release velocity, themes, recent moves, and the top alternatives to consider.

Request Tracker vs Live Helper Chat: at a glance

FeatureRequest TrackerLive Helper Chat
SectorSupportSupport
Velocity score0.06.3
Sparks · 30d01
Top themesticketing, security-releases, multi-branch, cvecustomer-support, live-chat, mcp, ai-native
Last editorial update20d ago2h ago
WebsiteVisit →Visit →

What is Request Tracker?

Request Tracker maintains three branches in lockstep, and security is what sets the release calendar.

Best Practical ships RT across three concurrent branches, 4.4, 5.0 and 6.0, and coordinates security releases across all of them on the same day. The most recent pair, 5.0.10 and 6.0.3, both landed on 2026-05-20 carrying the same fixes: a privilege escalation and credential disclosure through the REST 2.0 user collection endpoint (CVE-2026-44231), SQL injection via the entry_aggregator parameter in JSON search (CVE-2026-41075), and an LDAP authentication bypass. Feature work rides along on the 6.0 branch, while 5.0 and 4.4 receive security fixes and little else.

Read the full Request Tracker trajectory →

What is Live Helper Chat?

Live Helper Chat ships MCP support, making self-hosted customer chat an AI-queryable endpoint

Live Helper Chat added native Model Context Protocol support in its latest release, adding an MCP endpoint at `aimcp/mcp` that exposes the chat installation to external AI clients—ChatGPT custom connectors, Claude, and other MCP hosts. The endpoint uses Streamable HTTP via the official PHP MCP SDK, with token-based authentication, CORS controls, and a new admin screen showing the tool catalog. Recent releases have also added reCAPTCHA v3 and Cloudflare Turnstile support, and configurable operator offline reasons.

Read the full Live Helper Chat trajectory →

Request Tracker vs Live Helper Chat: editorial side-by-side

R0.0

Request Tracker maintains three branches in lockstep, and security is what sets the release calendar.

◆ Current state

Best Practical ships RT across three concurrent branches, 4.4, 5.0 and 6.0, and coordinates security releases across all of them on the same day. The most recent pair, 5.0.10 and 6.0.3, both landed on 2026-05-20 carrying the same fixes: a privilege escalation and credential disclosure through the REST 2.0 user collection endpoint (CVE-2026-44231), SQL injection via the entry_aggregator parameter in JSON search (CVE-2026-41075), and an LDAP authentication bypass. Feature work rides along on the 6.0 branch, while 5.0 and 4.4 receive security fixes and little else.

◆ Where it's heading

The branch structure is consolidating. RT 4.4 reached its last planned release at 4.4.9 in October 2025, with users pointed at 5 or 6, and 6.0 is where features now land: dashboard saved searches gained pagination and sorting, statuses take colors from lifecycle configuration, custom fields display multi-column by default, and keyboard menu navigation improved. The 5.0 line still gets real work but of a narrower kind, such as the inline CSS handling in ticket history that shipped with 5.0.10. Expect the same-day multi-branch security release to remain the pattern for as long as two branches are supported.

◆ Prediction

The next release is most likely another coordinated security pair on 5.0 and 6.0, with feature work continuing to accumulate only on 6.0.

L6.3

Live Helper Chat ships MCP support, making self-hosted customer chat an AI-queryable endpoint

◆ Current state

Live Helper Chat added native Model Context Protocol support in its latest release, adding an MCP endpoint at `aimcp/mcp` that exposes the chat installation to external AI clients—ChatGPT custom connectors, Claude, and other MCP hosts. The endpoint uses Streamable HTTP via the official PHP MCP SDK, with token-based authentication, CORS controls, and a new admin screen showing the tool catalog. Recent releases have also added reCAPTCHA v3 and Cloudflare Turnstile support, and configurable operator offline reasons.

◆ Where it's heading

The MCP addition converts LHC from a standalone support tool into infrastructure that participates in agentic workflows. This is the most significant architectural change the project has shipped in several releases—and it opens the door to AI agents querying chat history, routing conversations, or creating tickets without custom API wrappers. The next moves will likely expand the MCP tool catalog and deepen the AI client integration.

◆ Prediction

Expect the MCP tool surface to grow in the next 2-3 releases: richer read/write access to conversation history, customer profiles, and ticket creation are the natural asks from AI client integrators who've discovered the endpoint.

Alternatives to Request Tracker and Live Helper Chat

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 Request Tracker or Live Helper Chat.

See all Request Tracker alternatives → · See all Live Helper Chat alternatives →

Recent activity from Request Tracker and Live Helper Chat

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5h agoLive Helper ChatMCP Support
  2. 9d agoLive Helper ChatRestricted replaceable variables
  3. 28d agoLive Helper Chat4.90v Track you set user online manually
  4. 28d agoLive Helper Chat4.89v Enhancements
  5. 1mo agoLive Helper Chat4.88v Offline reasons
  6. 2mo agoLive Helper Chat4.87v Forms flow improvements for Quality Assessment extension
  7. 3mo agoRequest TrackerSecurity release fixes REST 2.0 credential disclosure and SQL injection
  8. 3mo agoRequest TrackerSame security fixes as 5.0.10, plus dashboard and accessibility work
  9. 10mo agoRequest TrackerCalendar view for saved searches and memory management work
  10. 10mo agoRequest TrackerCSV injection fix in TSV export, with assorted updates
  11. 10mo agoRequest TrackerFinal RT 4.4 release closes the branch with one security fix
  12. 1y agoRequest TrackerRelease exists mainly to support RTIR 6.0.1

Frequently asked questions

What is the difference between Request Tracker and Live Helper Chat?

They serve adjacent needs but don't currently overlap on shipped themes. Live Helper Chat 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.

Is Request Tracker better than Live Helper Chat?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Live Helper Chat 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.

What are the best alternatives to Request Tracker?

Top Request Tracker alternatives in Support are ranked by recent ship velocity. Browse the "Request Tracker alternatives" section above for the current picks, or visit /alternatives/request-tracker for the full list with editorial commentary on each.

What are the best alternatives to Live Helper Chat?

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.