One inbox, every channel
Customers reach you wherever they are. Your team replies from a single shared inbox with full context, no tab-switching.
Omnichannel customer support without channel sprawl
Modern customers do not pick a channel and stick to it. They start a conversation in WhatsApp, finish it over email, then come back via the live chat widget on your site. Most help desks treat each of those as a separate ticket, so context is lost between every handoff. Deskwoot pulls the 8 channels below into one shared inbox: email, live chat, WhatsApp Business, Telegram, X (formerly Twitter), LINE, SMS, and a REST API. Customer history, order context, AI agent replies, automation rules, and reporting all run on a single source of truth. Merge a customer's contacts from different channels and their whole history sits in one place.
Why a unified inbox beats stacked tools
Stitching together a separate WhatsApp app, an email helpdesk, a Twitter monitor, and a live chat widget looks cheaper on day one. By month three you have a context-loss problem: agents alt-tab between four UIs, customers repeat themselves at every channel switch, and reporting fragments into four dashboards that never agree. A unified inbox solves the routing once. Every channel writes to the same conversation thread, so handoffs are invisible to the customer. AI agent Fynn answers the routine questions across all 8 channels with the same knowledge base. SLA policies, automation rules, CSAT surveys, and team performance reports stay consistent regardless of where a chat originated.
All 8 channels
Live Chat
A light chat widget for any site. Connect Shopify or WooCommerce and your agents see orders, fulfilment and tracking next to every chat.
Email
Forward your support address on any plan. From the Startup plan, connect Outlook and Microsoft 365 with one click, or Gmail and any other mailbox over IMAP and SMTP. Threading, signatures and canned replies are built in.
WhatsApp
Connect with Meta and reply from the shared inbox. Media in both directions, read receipts, and Click to WhatsApp ad attribution from the Business plan, with no reseller in between.
Telegram
Connect your own bot with a token from BotFather. Messages land in the same inbox your agents already use, and agents send files of up to 50 MB back.
X (Twitter)
Direct messages to your brand account land in the shared inbox. Reply as your brand without opening X, with Fynn answering common questions.
LINE
LINE Official Account messaging connected directly. Text, images and stickers arrive in the inbox, and Fynn answers in Japanese, Thai or Chinese. Made for support teams in Japan, Taiwan and Thailand.
SMS
SMS in both directions through your Twilio number. Customer replies and MMS images land in the same inbox as your other channels.
API
REST API on the Enterprise plan for messages, contacts and conversations. Build a custom channel, mobile app or in app chat that feeds the same shared inbox.
Frequently asked questions
The short answers are here. For anything else, ask Fynn below.
Which channels does Deskwoot support?
Deskwoot supports 8 customer channels: live chat (website widget), email (forwarding on every plan; Outlook with Microsoft sign in, or IMAP and SMTP, from the Startup plan), WhatsApp Business (Meta Cloud API), Telegram, LINE, SMS through Twilio, X (Twitter) DMs, and a REST API for custom channels. Every conversation across these channels lands in the same shared inbox.
Can I connect WhatsApp Business to Deskwoot?
Yes. Click Connect with Meta, pick your number, and WhatsApp messages land in the same inbox as your other channels. Deskwoot uses Meta's official WhatsApp Cloud API, which is free to register.
Is there a Twitter/X integration?
Yes. Connect your X (formerly Twitter) account to Deskwoot and direct messages from customers flow into the same shared inbox as email and chat, so the team responds without opening x.com.
Can I build a custom channel with the API?
Yes. On the Enterprise plan, the Deskwoot REST API exposes conversations, contacts, messages and inboxes, so you can build a custom channel for chat inside a mobile app, a game, devices or any other place where customers contact you. Authentication uses scoped API tokens, and webhooks send events such as new messages to your URL.
