Appearance

Customer support

Great answers start with context.

The conversation and the customer’s live page in one window. See where they need help and reply with visit history and previous tickets at hand.

Explore the product in a demo tailored to your business.

Meetlead inbox with a conversation, a working live preview of the customer’s page and visit history. Example data.
Chat, the customer’s live page and visit history — in one view.
Capabilities

Less searching. More helping.

Customers see one company. Your team should see the whole issue: where the message came from, what happened before and who owns the next step.

Shared inbox

Every question has a place to go.

Bring website conversations and connected social channels into one view. Each conversation has a status and owner, and the team can see what needs attention.

Team and personal views
Switch scope, filter unread conversations and pin the ones you need to revisit.
Channels with clear requirements
Messenger and Instagram require separate connections. Instagram is available to eligible workspaces.
Inbox with conversations, messages and context. Demonstration data.
Inbox with conversations, messages and context. Demonstration data.
Live page preview

Help with what the customer sees right now.

A question like “where should I click?” is easier to answer when the customer’s page sits beside the messages. Combine live preview with the session’s visited URLs.

Current context
Check the offer, form or signup step behind the question.
Visibility follows configuration
An active session, consent and masking determine the preview. You do not take control of the device.
Actual live page preview beside the conversation and visit history.
Actual live page preview beside the conversation and visit history.
Team ownership

Hand over the issue with its history.

Customers should not have to repeat a conversation every time the owner changes. Departments, assignment and notes clarify who is handling the issue and what remains to resolve it.

Assignment that fits the team
Distribute conversations in rotation or by workload, considering department and availability.
A lasting ticket
A reference, priority and event history preserve decisions. Internal notes stay with the team.
The context panel shows ownership, the live page and the visit path.
The context panel shows ownership, the live page and the visit path.
Help on the website

The answer can be closer than a chat button.

Put clear instructions where questions arise. The widget lets customers search an article and contact your team if the explanation is not enough.

Content in the customer’s language
Articles support categories, drafts and published PL, EN and DE versions.
A next step when questions remain
Connect help to chat, callbacks or voice according to the Apps you enable.
Example help articles and contact options in the widget.
Example help articles and contact options in the widget.
Working with product teams

Good support informs the next improvement.

When an issue needs a product change, the chat reply is only the beginning. Link a Projects task to the ticket, keep the reason and agree on the next step.

The source beside the task
Designers and developers return to the ticket without copying the conversation into another tool.
A specific scope
Description, owner, priority and comments organize the work toward a solution.
Explore Projects
A task in the Projects App with a linked customer issue.
A task in the Projects App with a linked customer issue.

For your team

See how the product fits everyday work.

A startup serving its first customers

A founder answers a plan question, sees the customer’s pricing page and records a recurring difficulty as a task. One conversation informs both customer support and product work.

A team sharing ownership

One teammate gathers information and a specialist takes over the ticket. Ownership, an internal note and past decisions reduce repeated questions to the customer.

A business taking bookings

A customer asks about an offer before choosing a time. The team explains requirements in chat and the customer moves to bookings in the same widget.

Customer support

Capabilities

One shared inbox

Reply to website chat, Facebook Messenger and Instagram Direct. Filter conversations, pin important issues and hand them to the right person.

Every issue has a thread

Tickets keep a reference number, priority, owner and timeline. Internal notes help your team collaborate without bringing customers into internal discussions.

The right kind of help

Send files and quick replies, or share help articles. Enable browser voice calls or let customers request a callback.

Clear ownership

Departments and automatic routing distribute conversations in turn or by workload. History, tags and statuses make it easy to pick up where a colleague left off.

The live page beside the conversation

A live preview and visited URLs help locate the step where a customer needs help. Visibility depends on an active session and your website’s collection settings.

Help without starting a conversation

Publish widget articles with categories and language versions. Customers can search for instructions and start a conversation when they need more help.

How it works

From the first question to a resolution.

  1. See the need

    A customer starts a conversation in the widget or a connected channel. Their message arrives in the shared inbox.

  2. Reply with context

    Check the history, visited page and previous agreements. Help directly or bring in the right teammate.

  3. Decide who owns the issue

    Assign the conversation or ticket, add an internal note and set priority. The next person sees the history instead of a separate summary in another messenger.

  4. Follow through

    Set a priority, add a note and resolve the ticket. Review support quality in your reports.

Availability

Chat and the inbox are part of the platform. Additional channels, voice and advanced capabilities depend on your plan and active Apps. Instagram Direct requires individual access for your workspace.

See pricing
FAQ

Good to know

Which channels does the inbox support?

Website chat and connected Facebook Messenger and Instagram Direct accounts. Meta channels require the corresponding App, configuration and permissions.

How is a callback different from a voice call?

A callback collects a contact request and a preferred time. A voice call connects the customer and operator over the internet in their browsers. They are separate contact options.

Can customers return to an earlier issue?

Yes. The widget shows their issues, messages and statuses. The team retains the ticket context, assignment and event timeline.

Can I see the customer’s page live?

Yes, for an active visit with live preview available. The inbox shows the page beside messages and the visited URLs. Visibility follows website collection, masking and consent settings; this is not remote control of the customer’s computer.

What happens outside business hours?

Configure team hours and the offline view. Customers can leave a message and, when configured, request a callback. The offline experience should reflect your team’s actual availability.

Is all history retained forever?

No. Messages, recordings and other modules have their own retention rules. Review your plan and retention settings before treating the system as a permanent archive.

Start with a better conversation.

Tell us about your team. We will show you the product and help you choose capabilities for the way you work.

Explore the product in a demo tailored to your business.