Skip to content
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

The latest, in detail

20 updates

Clear filters

New feature

Your messenger, with a more useful home

A configurable home screen gives visitors more ways to begin.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Put the right starting points in view

This sample release expands the messenger beyond a single empty thread. A home experience can introduce the assistant, surface useful content, and give visitors a choice of relevant next steps.

  • Configure the opening experience for your website.
  • Bring helpful content closer to the conversation.
  • Keep the route into chat easy to find.

Make discovery feel deliberate

The fictional milestone explores a more guided visitor experience. Someone arriving with a common question can find an answer or begin a conversation from the same place, while the business can prioritize the content most relevant to its audience.

Open this update
New feature

Carry the enquiry into your CRM

Connected lead workflows make contact information useful beyond the inbox.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Give follow-up a destination

This fictional update adds a CRM handoff to the sample product timeline. Contact information and enquiry context can move into the system the sales team uses for ongoing work.

  • Configure the supported CRM connection.
  • Choose the workflow that should receive the enquiry.
  • Review the destination after testing the connection.

Keep the conversation’s meaning

A name and email are more useful when the team can understand the original request. The imagined milestone focuses on preserving enough context for a teammate to follow up with a relevant response instead of asking the visitor to explain everything again.

Open this update
New feature

Move from a question to a meeting

Scheduling connections bring the booking step closer to the conversation.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Offer the next step while the context is fresh

This illustrative release introduces a scheduling workflow for visitors who want to continue with the business. A connected calendar provider supplies the availability used in the booking flow.

  • Configure the scheduling account for the workspace.
  • Present the available meeting options.
  • Confirm the visitor’s selection through the provider.

Keep the outcome clear

The sample story emphasizes distinguishing a proposed time from a confirmed reservation. The conversation can explain the next step and show the result of the provider response, helping both the visitor and the team understand what happened.

Open this update
New feature

Make room for the whole support team

Invitations and workspace roles help teammates work in the same environment.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Bring the right people into the workspace

This fictional milestone introduces a team setup flow with invitations and role-based access. Administrators can build the group that will manage knowledge, review conversations, and support visitors.

  • Invite teammates to the correct workspace.
  • Choose access that matches each person’s responsibilities.
  • Review membership as the team changes.

Give ownership a place to start

A shared product needs a clear understanding of who can do what. The sample release frames team setup as part of the everyday workflow, allowing people to collaborate while keeping administrative actions with the appropriate members.

Open this update
New feature

Capture the enquiry behind the conversation

Consented contact capture helps the team turn useful chats into follow-up work.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Give interested visitors a next step

This sample release brings contact capture into the conversation. A visitor can choose to share their details when follow-up would be useful, with the enquiry retained in the workspace.

  • Ask for relevant contact information in context.
  • Keep the visitor’s choice clear.
  • Connect the details with the conversation the team will review.

Pick up the thread later

The fictional milestone is about making follow-up practical. A teammate should be able to understand what prompted the enquiry before reaching out. That context helps the team continue a useful exchange rather than starting with a generic introduction.

Open this update
New feature

Let a teammate take the conversation further

Human takeover gives complex questions a natural route to a person.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Continue the same conversation

Some questions need judgment, account context, or an explanation from a teammate. This fictional entry introduces a handoff path that keeps the earlier messages available when a person joins the exchange.

  • Review what the visitor has already asked.
  • Take over the thread from the workspace.
  • Continue with the context of the existing conversation.

Make the transition feel connected

The imagined release focuses on continuity. Visitors should be able to move from the assistant to the team without rebuilding the entire enquiry. Clear ownership helps teammates understand when they are responsible for the next response.

Open this update
New feature

A shared place for incoming conversations

The team inbox gives visitor messages a home beyond the chat window.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

See the exchange from the team’s side

This illustrative release introduces an inbox for reviewing visitor conversations. Teammates can open a thread, read the history, and understand the question before deciding what should happen next.

  • Browse incoming conversations in one workspace.
  • Read earlier messages without asking the visitor to repeat them.
  • Return to an exchange that needs follow-up.

Keep useful context together

The sample milestone moves the product from an isolated assistant experience toward a shared team workflow. The conversation becomes a record that people can review and continue, giving the business a clearer view of the enquiries arriving through its website.

Open this update
New feature

Bring documents and FAQs into the conversation

Written answers and document text extend the knowledge library beyond website pages.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Add the answers that are not on your website

This sample milestone introduces manual FAQs and document-based source material. Teams can prepare explanations for recurring questions without publishing a new website page for every answer.

  • Write a direct answer to a recurring question.
  • Extract useful text from a supporting document.
  • Review the material alongside existing website sources.

Keep each source focused

Short, specific explanations make a knowledge library easier to maintain. The imagined update encourages teams to separate unrelated policies, use descriptive titles, and check that each source answers a clear question. The result is a more organized foundation for the assistant’s responses.

Open this update
New feature

Turn your website into an answer library

A source workflow brings website information into the assistant’s knowledge workspace.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Begin with the information you already have

This illustrative milestone introduces website sources as a foundation for answers. Teams can bring relevant pages into a knowledge workspace and review what the assistant will use.

  • Add pages that explain products, services, and policies.
  • Inspect the extracted text before making it available.
  • Keep unrelated material out of the answer library.

Improve the source, improve the conversation

A useful answer begins with clear source material. The sample release narrative emphasizes reviewing headings, removing duplicated text, and making policies easy to understand. It establishes a repeatable way to maintain the information behind a conversation.

Open this update
New feature

A first home for website conversations

A lightweight website messenger brings visitor questions into a focused conversation experience.

Illustrative history · This entry’s date and release narrative are fictional, created to demonstrate a full year of product updates.

Start with a simple hello

The first chapter of this sample timeline introduces a messenger that visitors can open without leaving the page. A welcome message explains what the assistant can help with and invites a useful first question.

  • Open and close the conversation from a compact launcher.
  • Keep the exchange in the context of the website.
  • Give visitors a clear starting point with suggested questions.

Build around the first interaction

This fictional milestone focuses on the basics: a readable message thread, an obvious place to type, and an experience that works on desktop and mobile. The goal is to help a visitor ask a question at the moment it comes up.

Open this update