LoginSign Up
← Back to all sparks
C

Chatwoot

COMMS
Velocity6.3

Chatwoot is turning its June voice launch into a channel a team can actually run.

customer-supportvoiceai-agentsreportinghelp-centeromnichannel
◆Current state
Voice, introduced in June, now has a dedicated Calls area with filtering by inbox and assignee, per-call status and recordings playable in place, instead of calls buried inside conversation threads. Captain, the AI agent, mines already-resolved conversations for suggested FAQs and refreshes its own documents. Reporting charts became clickable, leading from a metric straight to the conversations that produced it.
◆Where it's heading
The pattern is consolidation rather than expansion. Each recent release takes something Chatwoot already shipped and adds the surface a daily operator needs: a home for calls, a payoff view for Captain, a path from a report number to the underlying threads. The AI work is aimed at reducing manual upkeep of the knowledge base rather than at answer quality.
◆Prediction
Voice is the obvious place for the next round of automation parity with text, since this release gave it a dashboard but not workflow triggers or Captain participation.

◆Recent moves

  1. 6d ago

    Voice calling grows up: a dedicated calls dashboard and smarter call handling

    Voice gets the operational surface June's launch lacked: one Calls list filterable by inbox and assignee, per-call status at a glance, and recordings played back in place. It closes the gap between having the channel and being able to run it.

  2. 6d ago

    Reporting Insights, Right Down to the Conversation

    Report charts became clickable, so a metric that stands out leads directly to the conversations and messages behind it, alongside inbox housekeeping such as a per-contact attachment view and a reorderable sidebar. It targets the distance between seeing a number and acting on it.

  3. 8d ago

    Help Center: safer edits, easier organizing, and faster search

    Bulk category changes, an editor that matches published typography, and faster search are all aimed at teams maintaining large help centers rather than small FAQ pages. The bulk move is transactional — nothing moves if anything fails — which matters when reorganising dozens of articles. This is the maintenance layer under the Documentation layout shipped in May, and under Captain, which reads this content.

  4. 12d ago

    Meet the Improved Captain: Smarter Suggestions and a Better Assistant Overview

    ⚡ SPARK

    Captain now reads the conversations a team has already resolved, spots repeated questions, and returns a ranked list of suggested FAQs with the source conversations attached for review. This inverts the knowledge-base problem the previous Captain releases danced around: instead of asking teams to feed the AI, the AI derives its own source material from work humans already did. It is the missing piece of the loop that Custom Tools and document refresh were building toward.

  5. 1mo ago

    Introducing voice calls in Chatwoot

    ⚡ SPARK

    Voice calls arrive in beta after years of text-only channels, and the framing is explicit: the foundation across chat, email, WhatsApp, social and help center had to be solid first. It removes the last structural reason a team running Chatwoot would keep a second vendor for phone support. Against the trajectory, it completes channel coverage and shifts the remaining competitive weight onto Captain.

  6. 2mo ago

    Captain Documents Now Stay Up to Date

    Captain documents gain a Refresh action that re-fetches a source page, compares it, and regenerates answers only when the content actually changed. Nothing about how Captain answers changes — this is upkeep of the material it answers from, and it is the release where knowledge-base staleness gets treated as Captain's problem rather than the admin's. A direct precursor to July's FAQ suggestions.