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

34 updates

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

Improvement

A conversation queue that tells you what needs attention

Assignment and status controls make the next action easier to identify.

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

Turn a list into a working queue

This sample update develops the shared inbox with clearer ownership and conversation states. The team can distinguish work that is underway from exchanges that are ready to close.

Assign a conversation to the teammate handling it.
Update its state as the enquiry progresses.
Review the queue for items that still need attention.

Make handoffs easier to follow

The fictional narrative focuses on shared understanding. A teammate opening the inbox should be able to see what they own and where help is needed. Consistent status updates make that picture more useful throughout the working day.

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

Improvement

More context when you open a person’s profile

Visitor profiles bring related conversations and activity into a clearer view.

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

Understand the person behind the thread

This illustrative update gives the team a more useful view of a visitor’s recorded activity. Related details help a teammate understand the enquiry before deciding how to respond.

Review the contact information available to the workspace.
Move from a profile into its related conversation.
Follow recorded activity without switching between disconnected lists.

Keep the review focused

The imagined improvement reduces the work needed to reconstruct context. A profile becomes a starting point for understanding an enquiry, while the original conversation remains available for the details that matter to the next response.

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

Fix

Keep work in progress out of published answers

A clearer separation between draft knowledge and published content protects the review workflow.

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

Give edits room to happen

This fictional fix addresses the boundary between preparing content and making it available to visitors. Updating a source creates work to review rather than silently changing the material used for answers.

Keep revised text in a draft state.
Review the saved version before approval.
Publish deliberately when the content is ready.

Make the status easier to trust

The sample narrative centers on a familiar editorial problem: an unfinished correction should not appear as a finished answer. Clear status and publication steps help the team understand which material is ready and which still needs attention.

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