All features
Shared inbox

Bring your support conversations into one workspace

Follow website, Telegram, WhatsApp and Bale conversations from a shared inbox. Keep the message history, customer context and next action together while your team replies.

A clear conversation queueOwnership your team can seeContext beside the reply
Shared inboxPRODUCT SCREENSHOT
Actual shared inbox interface in a sample workspace
Actual product interface with sample workspace data
IN YOUR WORKSPACE

What your team can do

A clear conversation queue

Switch between open, resolved, assigned and unassigned conversations. Search the queue to find the customer you need.

Ownership your team can see

Assign a conversation to an operator or team and set its priority from the customer sidebar.

Context beside the reply

Read customer details, labels and internal notes without leaving the conversation. Reply with text, attachments or saved responses.

Connected messaging channelsPRODUCT SCREENSHOT
Actual connected messaging channels interface in a sample workspace
Actual product interface with sample workspace data
FROM SETUP TO DAILY USE

See the conversation and its connected channels

  1. Create an inbox and connect the channels your team uses.

  2. Choose a conversation, review its history and assign the right owner.

  3. Reply, add an internal note when needed and mark the conversation resolved.

BEFORE YOU START

A closer look at how it works

Are internal notes visible to customers?

No. Internal notes are for the support team; the reply composer provides a separate reply mode for customer messages.

Can I see the interface before choosing a plan?

Enlarge the product screenshots on this page or explore the interactive workspace demo. The demo uses local sample data; plan availability is listed on the pricing page.

Explore the workspace demo

Choose the workspace that fits your team

Compare the available plans and decide which capacities your support team needs.

Compare plans

Product screenshots use sample data; form examples are not necessarily enabled.