Three ownership states
AI answering, waiting for a teammate and taken over by a teammate are visible at a glance; the default filter is All.
- Ownership
- State
- Team
—PRODUCT
Hands the conversation AI escalated to the right person with the right summary; context is not lost while the customer waits.
One queue, three ownership states and a 0/3/10-minute notification ladder. A teammate takes over, replies and can return the conversation to AI.
—SUMMARY
Brings every channel into one queue; the agent who takes over sees history and a handover summary.
01HOW IT WORKS
Each step is one screen in the panel; nothing goes live without confirmation.
An external handover request or the ###DEVIR### marker at the end of an AI answer starts the handover; one of six reason codes is recorded.
The default ladder is panel + Telegram + browser at minute 0, email at minute 3 and SMS at minute 10; only OWNER and ADMIN receive it.
The moment a teammate replies, they take over automatically and AI goes silent. When done, “Return to AI” reopens the conversation to AI.
02WHAT IT DOES
The three capabilities below are today’s scope; the sample dialogue is fictional and contains no real customer data.
AI answering, waiting for a teammate and taken over by a teammate are visible at a glance; the default filter is All.
Customer need, open work, what AI tried and the sources used arrive together for the person taking over.
An internal note has a yellow background and a lock with “not shown to the customer”; files can be added only in customer-reply mode.
03THE DIFFERENCE IS IN THE DETAILS
25 items, each tied to a rule, setting or automatic behaviour in today’s product. No unsupported number, ratio or promise appears in this list.
There are three ownership states: with no assignee and open, AI is answering; PENDING means a teammate is awaited; a filled assignee means a teammate has taken over.
The filter is Waiting for teammate / With AI / All, and the default is All, so an empty list is not mistaken for “messages disappeared”.
The queue shows 50 records and at most 100; counters are not derived from those 50 but come from the server.
Smoke-test conversations are hidden by default; unless “Show test conversations” is on, they are excluded from the list and counters.
A taken-over conversation is put at the top of the list even if it leaves the filter, preventing a reply to the wrong customer.
The handover summary has four lines: customer need, open work, what AI tried and the sources used.
An internal note has a yellow background and a lock with “Internal note — not shown to the customer”; the button says “Save note”.
@mention is saved but does not send a notification; the response returns notified:false.
A file can be added only in “Reply to customer” mode; images are 5 MB and documents 10 MB, and no file button is drawn for internal notes.
Ctrl/Cmd+Enter sends; plain Enter starts a new line.
The widget customer polls for messages and other channels write to Chatwoot; if Chatwoot fails, the local record is kept and the panel warns “NOT DELIVERED”.
The moment a teammate writes a reply, the conversation is taken over automatically; PENDING becomes OPEN and AI goes silent.
There are two handover triggers: an external handover request and the ###DEVIR### marker at the end of an AI answer; six reason codes are recorded.
The confidence or keyword threshold is not hard-coded; the handover decision lives in the automation flow, and this repository only parses the marker.
Automatic handover can be turned off; when off, the model writing ###DEVIR### does not create a handover, while manual takeover still works.
AI goes silent after handing over; “Return to AI” clears the stamps and reopens the conversation to AI.
The handover notification is panel + Telegram + browser at minute 0, email at minute 3 and SMS at minute 10; SMS can be turned off.
Only OWNER and ADMIN receive the notification; MEMBER, passive and archived users are excluded, and a step is skipped when no address exists.
Quiet hours are off by default; when defined, email/SMS between 22:00 and 08:00 are postponed to the end of the window, panel/Telegram go immediately, and synchronous web/phone are exempt.
Automatic close is 5 minutes and runs every 60 seconds; it closes OPEN and PENDING conversations, so an unanswered handover can also close.
Automatic close triggers the conversation.resolved email notification; clicking “Resolved” in the panel does not trigger it.
If the same visitor returns within 3 hours of the last message, the same conversation is reused; if closed, it becomes OPEN and resolvedAt is cleared.
The operator assistant is off by default; when on, it produces rule-based sentiment/urgency and AI suggestions/summaries, capped at 200 requests per day.
Sentiment/urgency is a rule engine, not an LLM; messages shorter than 3 words get no badge, “urgent” alone is not high, and the panel labels it “AI estimate · not certain” without auto-assigning.
When privacy consent exists, the customer detail shows “Privacy consent received”, the date and the text.
04CONTROL AND SECURITY
These are this surface’s current security behaviours; no general “GDPR compliant” certificate is claimed.
An internal note is written in a separate mode, marked with a yellow background and a lock; sending is possible only in “Reply to customer” mode.
Handover notifications go only to OWNER and ADMIN; MEMBER, passive and archived users are excluded.
Email/SMS are postponed in quiet hours, but panel and Telegram go immediately; when a customer is waiting on web/phone, push also goes immediately.
Automatic close is 5 minutes and also closes PENDING conversations; a handover nobody takes can close unanswered. Teams should set the notification ladder with this in mind.
05WHICH PLAN
The inbox is available on every plan. The only gate is the operator assistant: it is off at platform level and limited by role; it is not on by default.
All amounts are monthly and exclude VAT. See the plans page for the current list and calculator. Plans and calculator →
06FAQ
+RELATED POSTS
Posts from the same topic cluster that complete this page. Inbox & human handover posts.
What WhatsApp Business API is, how it differs from the WhatsApp Business app, how to set it up, and how conversation-based pricing works.
Why Trendyol “Ask the Seller” questions pile up, how response time affects sales, and what sellers can automate and what should stay with a human.
A plain guide to what an AI customer agent does, how it answers from a knowledge base and when it hands a conversation to a person.
Try free for 14 days without a credit card; we will do the first setup together.