A better conversation.
With every update.

Keep older work within reach

The workspace uses paginated lists so teams can move through records in manageable sections. Search helps narrow the result before opening a person, conversation, or content item.

• Browse past the first page of records.
• Search the supported lists without scanning every row.
• Load older message and activity history when needed.

Carry the question into reporting

Reports support filters and CSV export so teams can examine the relevant slice of activity. Choosing a useful date range and filters before exporting keeps the result focused on the question you are trying to answer.

Follow the record, not just the headline

An overview can point to a change in activity, while the underlying conversations explain the context. Use the lists and history together when reviewing follow-up work. These tools show recorded activity; they do not establish that a particular conversation caused a business outcome.

Give follow-up work a structure

Some questions need investigation, another teammate, or a later reply. Tickets make that work visible in the workspace with a status and ownership that can continue beyond the original exchange.

• Review support requests from a dedicated ticket list.
• Open a request to inspect its details and activity.
• Update ownership and progress as the team works through it.

Make the handoff easier to follow

A ticket provides a shared place to return to the issue. Teammates can review the request and its current state before continuing the work, reducing reliance on a separate personal reminder.

Build a routine around the queue

Use a consistent approach to triage and status updates so the list reflects work that still needs attention. Ticket tracking supports that routine without making promises about how quickly an issue will be resolved.

A message should leave a trace

Visitor-message notifications are stored so the team can find them after the initial interaction. The notification bell provides an entry point into unread activity and the conversation that needs attention.

• Review unread notifications in the workspace.
• Open the associated conversation from a notification.
• Use the configured sound and browser notification preferences.

Choose how to be alerted

In-app notifications and browser push serve different situations. The workspace can show incoming activity while open; browser delivery additionally needs permission and an active subscription on the receiving device.

Check the complete path

For browser alerts, enable permission on the intended browser and confirm that the push worker is running in the deployment. A saved preference alone does not guarantee external delivery. The persistent workspace record remains the place to review incoming activity and unread state.

Move from a queue to a next step

A shared conversation list gives teammates a place to review incoming questions and decide who should handle them. Assignment and status make the next action visible without moving the conversation into a separate tool.

• Organize ownership with team and teammate assignment.
• Track conversations as their status changes.
• Keep the visitor’s messages close to the work needed to answer them.

Keep the context with the conversation

Internal collaboration belongs alongside the original exchange. Teammates can review the conversation before replying, so a handoff does not have to begin with another request for the same information.

Set up the team first

Invite the people who will handle conversations, review their workspace access, and establish an assignment routine. The inbox supports the workflow; your team still decides coverage, response expectations, and when a conversation is complete.

Tune the conversation

Assistant settings bring together the agent’s identity, tone, suggested questions, and conversation behavior. These controls help teams explain how their assistant should respond and what information it should collect.

Shape the visitor experience

Messenger settings focus on presentation: appearance, launcher, branding, and the experience visitors open on your website. A preview helps you review the result while adjusting the settings.

• Set the assistant’s conversation style in one place.
• Adjust visitor-facing appearance from Messenger.
• Review the preview before using the widget on your site.

A more useful setup routine

Start with the assistant’s instructions and knowledge, then refine the messenger to match your website. Keeping these tasks distinct makes it easier to revisit a setting without searching through unrelated options. Test the final conversation in the playground before introducing it to visitors.

Turn repeated answers into a resource

A help center gives visitors a place to browse support content beyond an individual chat. Collections and articles help teams organize explanations into a structure readers can follow.

• Prepare and edit articles before publishing.
• Group related content into collections.
• Customize the help center’s appearance separately from the messenger.

Use an address that fits

Each website’s help center has a public route. Handle and custom-domain controls support a more recognizable address, with verification required before a custom domain is served.

Keep publishing deliberate

Review the article that readers will see and publish it when ready. Draft work stays separate from the public resource. Custom addresses additionally require the appropriate DNS and hosting certificate setup; saving an address in the workspace does not complete those external steps.

Choose the connection for the job

The integrations area brings supported providers into a catalog with configuration appropriate to each connection. Scheduling, commerce context, CRM handoff, and team notifications can be set up around the workflows your team uses.

• Review the available integration and its setup requirements.
• Connect the correct provider account for your workspace.
• Inspect connection and delivery information where supported.

Keep credentials out of the conversation

Provider credentials belong in the integration setup. They should not be pasted into assistant instructions or visitor-facing knowledge. The workspace separates connection management from the content used to answer visitors.

Confirm the real destination

After connecting a provider, test the full workflow with an authorized test record. A configured connection is a starting point; it is not proof that a booking, CRM update, or notification has reached an external service.

Give visitors a way in

The messenger can bring conversation entry points and useful content together inside the widget. Configure the home experience around the questions and next steps that matter to your website.

Reach visitors with more context

Proactive messaging supports audience rules and scheduling, so a message can be tailored to the circumstances in which it appears. Teams can review days, hours, and timezone settings alongside their coverage.

• Configure the messenger’s home and visible content.
• Define the audience for a proactive message.
• Set a schedule that fits the team’s operating hours.

Review the experience as a visitor

After saving, open the widget on an allowed website and follow the entry points yourself. Check the timing, language, and destination of each message. Availability rules and a thoughtful greeting work best when the next step leads somewhere useful.

See the full commitment

The plan comparison brings the monthly equivalent and the annual total into the same decision. Growth and Scale include yearly billing options, with the selected interval carried through signup and login to the billing workspace.

• Compare included usage and capabilities before choosing a plan.
• Review the annual amount alongside the monthly equivalent.
• Keep monthly usage resets when choosing a yearly subscription.

Continue from where you started

Choosing a plan on the public site carries that choice into the account flow. The billing screen gives you another opportunity to review it before checkout, while existing subscribers manage changes through the billing portal.

Built around consistent pricing

The public pages and workspace use the same pricing definitions. Checkout validates the configured provider price and billing interval. Live checkout still depends on the workspace’s Stripe configuration; this record does not confirm a payment or subscription change.

Ask for the next step in context

A visitor can share contact details with consent during the conversation. The resulting lead is stored with the workspace so the team can return to the enquiry after the chat.

• Capture details the visitor chooses to provide.
• Keep the enquiry available for team follow-up.
• Offer a scheduling step when a supported provider is configured.

Confirm before calling it a booking

Live scheduling depends on the connected calendar provider and its response. Without a configured provider, the product reports the missing connection. Demo scheduling uses simulated slots and should not be treated as a real calendar reservation.

Close the loop with your own process

Review the lead, confirm any meeting details, and check delivery to a connected CRM when that workflow is enabled. Capturing an enquiry is the beginning of follow-up, rather than a claim that a sale or meeting has already happened.