Start free
← Example scenarios

A request routes itself to the right team

The message is read and sent where it will be answered: sales, support or accounts.

What the scenario looks like

Обращение
Куда это▶
Модель▦
Отдел▶
В продажи▶
В бухгалтерию▶
В поддержку▶
Ушло в продажи▶
Ушло в бухгалтерию▶
Ушло в поддержку▶
  • Execute + Data
  • LLM
Open in your workspace →

A shared inbox or a shared chat is a place where requests wait for somebody to sort them. Sorting takes seconds and goes by meaning rather than keywords: “the invoice hasn’t arrived” and “we’d like to buy” differ not in their words but in who is writing.

What is inside

  1. The request — the entry.
  2. Where does this go — the model returns a team and one line saying why.
  3. Team — a three-way branch.
  4. Three endings format the request for each team.

The reason travels with the request, and it is not decoration: without it a misrouted request looks like an accident, and you only find out routing has drifted from complaints.

What to set up for yourself

  • The teams. Three because three is the typical minimum. A fourth means a line in the field description, a branch and an ending.
  • The boundary between teams is set by the department field description. Sales and support are currently separated by “are they already a customer or not yet”.
  • The endings. They only format text today. Put what you actually have in their place: a message to the team’s chat, an email, a CRM record. The branch does not change.

What to connect

Nothing, to try it. Real delivery arrives with whatever you send to: a Telegram bot for a team chat, a mail connection for an email, amoCRM for a deal.