The settings on Projects → [Your Project] → Team → Departments decide which department a chat goes to and who in it gets the chat. Admins and managers can change them. Departments themselves, the inbox and notifications are in Departments: who handles which chats.
When a chat gets its department, and in what order
A chat gets its department when it is handed to a person: when Chatonio escalates it to your team (see Escalation and Operator Handoff), or, on a channel where the AI is off, as soon as it arrives. While the AI is still answering, nothing is decided. Chatonio takes the first of these that gives a department:
- The channel's own department, set under Channel destinations. A chat on such a channel has it from the start.
- Rules for incoming chats: the first rule that matches.
- The AI's pick, on channels where the AI is on.
- If nothing else placed the chat: the project's default department.
- Otherwise the chat has no department and goes to the whole project.
A person's choice always wins. Once an operator has transferred a chat, to a department or to No department, or chosen its department in the Escalate to operators dialog, none of these steps moves it. A chat keeps its department until it starts again as New, and then starts again from its channel's department. Threads in a Telegram group are not placed in departments.
Channel destinations
Under Channel destinations, each channel can send all its chats to one department: choose the department beside the channel, or Use the rules to leave its chats to the steps that follow. Neither the rules nor the AI pick another department for those chats. A change applies to chats that start after it. On the channel's own settings page, this choice is shown as Default department, with a link to this page. Telegram group channels are not listed.
Rules for incoming chats
Rules send a chat to a department without asking the AI, so they also work on channels where the AI is off. They are checked from the top, and the first one that matches decides.
- Under Rules for incoming chats, click New rule.
- Under When, choose what to check, how to compare it, and the value.
- To check more than one thing, click Add a condition and choose All of these match or Any of these matches.
- Under Send the chat to, choose the department, then click Create rule.
A condition can check:
- Language is or is not a language: the language detected from the customer's messages, or their browser or app language until they have written enough.
- Page URL contains, starts with or is a text: the page the customer was on when they last wrote, in web chat. It is compared as plain text, and upper and lower case matter. A value that starts with
/is compared with the page's path, the part of the address after the domain: starts with/pricingmatcheshttps://yourshop.com/pricingand the pages under it, and is/pricingmatches only that page. The part of the address after a?is compared only if your value contains a?, and the part after a#only if it contains a#. Any other value is compared with the full address, such ashttps://yourshop.com/pricing. - Channel is or is not one of the project's channels.
Something Chatonio doesn't know matches nothing, is not included: a chat whose language isn't known yet is not "not German", and chats from channels other than web chat have no page URL.
The list shows each rule's conditions and department. The arrows beside a rule move it up or down, and the new order is saved at once. Click a rule to change it; there you can also switch it off (This rule is on) or click Delete rule. A rule that is switched off shows Off and is skipped. A rule that names a channel you have since deleted shows Needs fixing and is skipped until you change it. A project can have up to 20 rules, with up to 6 conditions each.
Try one chat
Below the rules, Try one chat shows where a chat would go with the settings as they are saved. Choose a Channel and a Language, type a Page URL if it matters, and click Check. The answer names the channel's own department, the rule that matches, or the default department. Nothing is sent and the AI is not asked: where the AI would pick first, the answer says so.
The AI's pick
On channels where the AI is on, when neither the channel nor a rule placed the chat, the AI picks a department. It reads only the departments' names and their Help the AI choose this department texts, the latest messages of the conversation and why a person was needed; your system prompt plays no part. Describe each department in plain words, as you would brief a new colleague: which questions belong there, with a few examples (up to 1,000 characters). If no department clearly fits, or the chat could belong to several, the AI picks none and the default department applies.
The AI is asked once for a chat (until it starts again as New), and the request is charged to the project's AI balance as an Escalation Check. With no balance left, it picks none. Where the AI is off for the channel or the whole project, it never picks; use a rule or a channel destination there.
The default department
If nothing else placed the chat chooses the department for chats that no channel destination, rule or AI pick placed. It starts on No department (the whole project). Where the AI is on, it still picks first, so the default department takes what the AI couldn't place.
Who gets the chat
Once a chat has a department, Chatonio assigns it to one of the department's members who is available: on shift and not set to Away or Offline, or set to Online. Which one follows the department's Who gets a chat in this department. With Use the project's setting, the default, that is the project's Who gets a chat that needs a person on the Members tab (see Managing Your Team); The available person with the fewest chats counts each person's chats in the whole project. A chat an operator transfers to the department is assigned the same way, never back to that operator. A chat with no department is assigned among everyone in the project.
When nobody in the department is available
If none of the department's members is available, its When nobody here is available decides:
- Use the project's setting (the default) follows the card When nobody in a department is available at the top of the page: Leave it waiting for the department and page them (the default) or Assign it to any available operator.
- Wait for this department: nobody is assigned, and the chat waits in the department.
- Give it to someone from another department, with the Backup department you choose: an available member of that department gets the chat. If nobody there is available either, the chat waits; the backup department's own setting is not followed.
- Give it to anyone available in the project.
Either way, the chat keeps its own department. A chat that waits stays unassigned in its department, and its members are notified (see Notifications in Departments: who handles which chats). It is not assigned later by itself, even when someone in the department comes on shift: someone takes it, assigns it or transfers it. When the department's choice of who gets a chat is Nobody: someone picks it up, nobody is assigned at all, so this setting doesn't come into play.