One inbox. Every conversation.
Website chat, WhatsApp, Instagram, Messenger, email and SMS in a single queue — assigned, tagged, prioritised and answered by one team, in one place, without tab-hopping.
- Every channel in one queue
- Assign, tag and resolve
- Free plan available
Connects to the channels and tools your customers already use
WhatsAppInstagramMessenger
Telegram
LINE
Discord
Shopify
Salesforce
HubSpot
Pipedrive
Zoho CRM
SlackWhatsAppInstagramMessengerTelegramLINEDiscordShopifySalesforceHubSpotPipedriveZoho CRMSlackSix places customers write to you. One place you answer.
Every channel keeps its own quirks — templates on WhatsApp, story replies on Instagram — but your team works in one interface with one set of rules.
Website chat
The widget on your site, with the visitor's journey and details attached to every thread.
Answer WhatsApp Business messages in the same queue, with templates for follow-ups.
DMs and story replies become tracked conversations instead of lost notifications.
Messenger
Facebook page messages, answered by your team without opening Facebook.
Forward a support address and email threads arrive with status, assignment and history.
SMS
Two-way text for order updates and for the customers who still prefer a message.
Every conversation has an owner within seconds of arriving.
Unowned conversations are how things get missed. Route by team, language, tag, plan or availability — and fall back to the shared queue when nobody is on.
- Teams and round robin so the load spreads instead of landing on one person.
- Availability aware — offline agents don't get handed new work.
- Transfer with context — the transcript, notes and customer record move too.
- Roles and permissions to decide who can see, reply, close or export.
Sarah Chen
Ask a colleague without leaving the thread.
Most support answers need a second opinion from someone who isn't in support. Internal notes and mentions keep that conversation attached to the customer's, where it belongs.
Internal notes
Private to your team, kept in the thread forever, never visible to the customer.
@mentions
Pull in the one person who knows the answer. They get notified, not added.
Collision detection
See who has the thread open and who is typing, before you send a duplicate answer.
The answer you type ten times a day, in one keystroke.
Type a slash, pick the reply, edit the details. Shared replies keep the team consistent on refunds, policies and pricing — personal ones keep your own voice.
- Variables like name, order number and date fill themselves in.
- Shared or personal — one library for the team, one for each agent.
- Usage counts show which replies work and which need rewriting.
- Attachments included, so the size guide or invoice goes out with the text.
Variables available in every reply: {{first_name}}, {{order_id}}, {{agent_name}}, {{date}}.
Sarah Chen · WhatsApp
First response due
Alex Rivera · Instagram
First response due
David Okafor · Website
Waiting on customer
Jane Whitfield · Email
Resolution due
Know what's about to break before it breaks.
Set first response and resolution targets per priority and per channel. The queue orders itself around what is closest to breaching, and alerts fire before it does — not after.
- Targets that respect working hours, so a Friday night clock doesn't run all weekend.
- Pre-breach alerts to the assignee, the team, or a Slack channel.
- Escalation rules that reassign or raise priority automatically.
- Honest reporting on met and missed targets, by team and by channel.
Find any conversation in a couple of seconds.
Search across every channel, open or closed, then save the search you keep repeating as a pinned view.
Refund policy for annual plans
Sarah Chen · WhatsApp · closed by Marco
Refund not received after 7 days
Alex Rivera · Instagram · unassigned
RefundPartial refund on a bundle order
David Okafor · Website · assigned to you
Refund request — duplicate charge
Jane Whitfield · Email · assigned to you
Refund policy question, closed no reply
Anonymous visitor · Website chat
Saved views sit in the sidebar for the whole team — or just for you.
Everything a shared inbox needs to stay calm.
The features that decide whether a busy queue feels manageable or chaotic on a Monday morning.
Conversation status
Open, pending, snoozed or closed — with a reason on close, so reports mean something.
Tags and topics
Tag manually or automatically, then filter, route and report by the tags that matter.
Priorities
Set priority by rule or by hand, and let it drive both queue order and SLA targets.
Unread and snooze
Snooze a thread until the customer replies or a date passes, then have it come back.
Saved views
Turn any filter into a pinned view — "Unassigned", "Breaching in 1h", "VIP customers".
Search everything
Keyword, customer, agent, tag, channel or date, across open and closed conversations.
Notes and mentions
Private notes in the thread, @mentions that notify without adding a participant.
Canned replies
Shared or personal shortcuts with variables, so speed doesn't cost accuracy.
Collision detection
See who has the thread open and who is typing before you send a second answer.
SLA rules
First response and resolution targets per priority, per channel, with alerts before breach.
Questions about working as a team.
Website chat, WhatsApp Business, Instagram DMs, Facebook Messenger, Telegram, email and SMS. Each one becomes a thread in the same queue, and the customer keeps a single profile no matter where they wrote from. Adding a channel takes a few minutes in settings and does not change how your team works.
Manually, round-robin across a team, or by rule — channel, language, tag, plan, customer value or working hours. Anything unassigned sits in a shared queue that anyone can claim. If an agent goes offline mid-shift, their open conversations can fall back to the team automatically.
Collision detection. You can see when a teammate has the conversation open and when they are typing, before you press send. If two people start replying anyway, the second one gets a warning in the composer. It removes most duplicated and contradictory answers on its own.
Yes. Internal notes live in the same thread but are visible only to your team, and @mentioning a colleague notifies them without adding them as a participant. Notes stay attached after the conversation is closed, so the context survives for whoever picks it up next time.
You can search by keyword, customer, agent, tag, channel, status or date range, including closed conversations. Any search can be saved as a view and pinned to the sidebar. Most teams end up with a few standing views like "Unassigned", "Breaching in 1h" and "Waiting on customer".
No. Email conversations arrive in the same inbox with statuses, assignment, SLA timers and full history, so a chat can turn into a tracked ticket without switching tools. If you need formal ticket numbers, queues and forms, Ticketing is built on top of this same inbox.
Close the tabs. Open one inbox.
Bring every channel into Chatdrill and let your team answer from one place.
No credit card required.