A department is a group of people in your project who handle one kind of question, such as Sales, Billing or Delivery. When a chat needs a person, it is placed in a department, Chatonio assigns it to someone available there, and that department's members are the ones notified. Departments only decide where chats go and who is notified: everyone in the project still sees every chat, whatever department it is in.
Departments are part of the paid plans: in a project whose owner is on the Free plan, there is no Departments tab under Team. When a project moves to a plan without them, its chats are routed and notified as if it had no departments.
Creating a department
- Go to Projects → [Your Project] → Team → Departments.
- Click New department.
- Enter a Name and tick its Members. One person can be in several departments.
- If the AI should be able to pick this department, describe under Help the AI choose this department which questions belong here, with a few examples (see Routing chats to departments).
- Click Create department.
Three more fields decide how the department works. A new department follows the project's settings until you change them:
- Who gets a chat in this department: the same three choices as the project's Who gets a chat that needs a person, applied to this department's members. Use the project's setting keeps the project's choice, which the line under the field names.
- When nobody here is available: Wait for this department, Give it to someone from another department (then choose the Backup department) or Give it to anyone available in the project. Use the project's setting keeps the project's choice.
- Who is notified about a chat waiting here: see Notifications below.
The first two are explained in Routing chats to departments. Admins and managers create and change departments; other members see the list. A project can have up to 20 departments. Some app versions still call the AI's text Routing rules.
Editing and deleting a department
Each department in the list has Edit and Delete. Deleting a department deletes no chats: its chats, and any channel that sent its chats there, go back to no department (the whole project). The rules that sent chats to it are deleted, the project's default department is cleared if it was this one, and a department that used it as its backup waits for its own members until you choose another backup.
How a chat gets its department
A chat gets its department when it is handed to a person, from the first of these that applies: its channel's own department, your Rules for incoming chats, the AI's pick (where the AI is on) and the project's default department. Without any of them, it has no department and goes to the whole project, as before. A department an operator chooses is never changed by these steps. All of this, and what happens when nobody in a department is available, is in Routing chats to departments.
In the inbox
- The project switcher at the top of the conversation list shows each department under its project, with its own unread count. Pick a department to see only its conversations, or the project to see all of them again. The choice is remembered on that device.
- The inbox filters have a Department row: pick one or more departments, or No department. Custom inboxes can filter by department too (see Custom inboxes and the unread counter).
- A conversation in a department shows the department on its row in the list, and under Department in its info panel.
Notifications
A chat that waits in a department with nobody assigned notifies that department's members, as long as at least one of them is at work: on shift (even if set to Away) or set to Online. In a project with no shifts, the same rule applies as for On shift in the notification settings. If none of them is at work, the whole project is notified, so a waiting chat is never left with nobody told. To have a department's chats always notify the whole project, set its Who is notified about a chat waiting here to The whole project.
This applies to the Needs an operator and AI chats notifications and to Repeat ping. Everyone's own settings still decide what reaches them (see Notification settings), and an escalation notification names the department before the reason. A chat with no department notifies the whole project, as in a project without departments.
Transferring a chat to another department
When a chat is in the wrong department, or needs another team, hand it over:
- In the conversation, open the assignment menu: the button with the name of whoever has the chat, or Assign if nobody has it.
- Click the Department row. It shows the chat's current department.
- Pick a department. Each one shows how many of its members are on duty. No department hands the chat to the whole project.
- In the Transfer to name? dialog, add a Note for your colleagues if you like, and click Transfer.
The transfer takes the owner and any additional operators off the chat, and its status becomes Escalating. Chatonio then assigns it to an available member of the new department, following that department's settings, but never to you. If nobody there is available, the chat waits in that department and its members are notified. The chat gets a system line, Transferred to followed by the department and your name, with your note after it. Only your team sees it, not the customer. While the chat waits, the AI follows While a chat is escalating, the AI, as for any escalation.
A department a person chose stays: the rules, the AI and the default department never move a chat an operator transferred, or placed in a department when escalating it by hand (Send to department in the Escalate to operators dialog). In the people list, the chip with the chat's department name shows only that department's members. Transfers are for one-to-one chats: threads in a Telegram group are not placed in departments.