Product journal / Chatrevia

A better conversation.
With every update.

A closer look at what’s new, what’s improved, and the details that make Chatrevia work better for your team.

The details, in one place

From the first visitor question to the next step your team takes. Explore the features behind the conversation.

Explore product updates

History entries: 34
New features: 20
Improvements: 11
Fixes: 03

September 2026

12 updates

Clear filters

New feature

Start every answer with knowledge you control

Website sources, document text, and written FAQs give the assistant a reviewed foundation for visitor questions.

Bring your source material together

The knowledge workflow accepts permitted website pages, text extracted from PDF documents, and manual FAQs. Teams can prepare useful source material without placing every answer inside the assistant’s instructions.

Add a source for the website the assistant serves.
Review and edit the extracted or written content.
Approve the saved version, then publish it for answers.

Keep drafts separate from answers

Editing or recrawling a source returns the new work to the review workflow. Publication is a deliberate step, so preparing a correction does not mean it is already approved for visitor answers.

Test the questions customers actually ask

Use the playground to ask about the products, policies, and next steps described by your sources. Review the response and improve the underlying material where it is unclear. Knowledge quality and provider availability still affect what the assistant can answer.

Open this update

New feature

Keep a human within reach of the conversation

Live conversations let the team review visitor messages and take over when the exchange needs a person.

Start with the conversation history

Visitor messages are stored so teammates can review what has already been asked and answered. The team can use that context when the visitor needs a more specific response or a human decision.

Open the conversation from the workspace.
Read the earlier messages before replying.
Take over the exchange when human support is needed.

Make the transition understandable

Human takeover changes who handles the conversation. It gives the team a way to continue the visitor’s existing exchange instead of asking them to restart in a separate support channel.

Plan for team availability

A handoff still depends on someone being available to respond. Establish coverage and review the visitor-facing language so expectations match the team’s operating hours. Test both the assistant and human paths on your website before relying on them for live enquiries.

Open this update