Teams and routing
Split the people who answer into teams, and decide which conversations reach each one.
Every workspace starts with one team, named Support, that holds everyone who can reply. Every conversation handed to a person goes to it. That is all most workspaces need.
When different people handle different things, you can add teams on the Pro and Business plans, and during the free trial. Each conversation that needs a person then reaches one team, and that team is told.
Create a team
Open Settings → Team → Teams and choose New team. A team needs three things:
- Name, unique in your workspace. Your customers never see it.
- Scope, one line in your own words, such as "Refunds, invoices and payment problems". Aiva reads the scope to decide where a request goes. It is optional.
- Members, the people who answer for it. A member can belong to several teams.
Everything else starts from the defaults and is set on the team's page: its websites and channels, automatic assignment, a response target and its lead. The default team has no scope and no websites or channels: it takes every conversation no other team takes.
Creating a team draws no conversation to it by itself. It receives conversations from the websites and channels you give it, the requests Aiva names it for, the campaigns that hand their conversations to it, and what a teammate transfers to it.
How a handoff finds its team
When a conversation is handed to people, the first rule that applies decides the team:
- Transfer. A teammate transferred it to a team.
- Campaign. The visitor started it from a campaign whose conversation step hands it to a team.
- Earlier handoff. An earlier handoff or transfer of the same conversation already placed it with a team, and it stays there.
- Website or channel. A team takes the website or the channel it came from.
- Scope. Aiva handed it over and named the team whose scope covers the request.
- Default team. Nothing above applies, so the team that takes everything else receives it.
In the conversation, the line above the handoff names its team. Hover over it to see which rule applied.
Websites and channels
On a team's page, Websites and channels lists every website where Webchat runs and every channel you connected: Discord, Telegram and the API. A conversation from a place a team takes belongs to that team from the start, and its handoffs go there with or without Aiva.
A place belongs to one team at a time. When another team already takes a place, the page says which one, and choosing it moves the place to this team when you save.
Team scope
Aiva reads each team's scope only where it can decide something: the conversation's website or channel belongs to no team, and no earlier handoff placed it. When Aiva hands a request over, it names the team whose scope covers what the customer needs done, or none, and then the request goes to the default team.
Write the subject the team takes care of, not instructions or a kind of customer: "Refunds, invoices and payment problems" works, "Always send angry customers here" and "Customers who write in Spanish" do not. Two teams whose scopes overlap make the choice less predictable, so keep them distinct.
Team names and scopes are internal. Aiva is never given a team's name, so it cannot tell a customer which team or person will answer. What it tells them about the wait (where the reply will arrive, and how quickly requests are usually picked up) holds for whichever team receives the request.
Handoffs
Handoffs on a team's page sets what happens to a conversation handed to the team:
- Automatic assignment, on by default, gives the conversation to the member with the fewest open conversations among those who are available and connected to the workspace, from the dashboard or the mobile app. If that member leaves before replying, the handoff moves on after five minutes. With nobody available, or with automatic assignment off, everyone on the team is alerted and the first reply takes the conversation.
- Response target is optional. A handoff with no reply within the target goes, with automatic assignment, to another available member who has not had it; otherwise the lead is alerted. A teammate who took the conversation themselves keeps it. When your workspace sets its hours under Settings → Team → Hours, the target counts open hours only. Without a target, nothing is ever overdue.
- Lead is who a passed target alerts, the workspace owner unless you choose someone else. With several teams, the lead also reads the team's figures in Reports.
- Typical pickup appears once the team has enough history: the wait Aiva and Webchat state to visitors when a conversation is handed to the team, read from the handoffs of the last 30 days. A visitor who waits longer than they were told is told once that it is taking longer.
Members lists each member with their status and open conversations, which is what automatic assignment compares.
Members
Every member who can reply belongs to at least one team, and every team keeps at least one member who can reply. A new member joins the default team, or the teams their invitation names. While your workspace has one team, membership follows each member's role. With several, you add and remove members on each team's page.
When a member leaves the workspace or becomes a viewer, a handoff given to them that they had not answered goes to another member of the team who is online, or back to the whole team, which is alerted. The other conversations they hold go back to their team. A conversation they finished keeps their name, and loses it if the customer writes again.
A viewer reads every conversation and writes internal notes, and can be mentioned in a note, but never replies to a customer, is never assigned and is on no team. A viewer takes no seat: your plan's seats count the members who can reply and the invitations for them, so you can invite a viewer when every seat is taken. Making a viewer an agent or an admin takes a seat.
Mention a teammate by typing @ and their name in an internal note. A mention notifies them, works for names in any script, and reaches only teammates who can read that conversation. In a reply to a customer, @ offers Aiva only, so a teammate's name never reaches the customer.
Conversation access
Every member who can read conversations reads all of them, unless you limit an agent to the conversations of their own teams. The limit suits someone who works one team only, such as an outsourced billing desk, a regional team or a contractor for one product. It is offered once your workspace has several teams.
Open Settings → Team → Members, open the member's menu and choose Limit to own teams. An invitation can set the same limit, under the teams it names, so the new member is limited from their first visit. The limit applies to agents: owners and admins read every conversation, and viewers are on no team.
A limited member reaches the conversations of their teams and the conversations assigned to them. Any other conversation does not exist for that member:
- The inbox, its counts and the unread badge hold only the conversations they reach, and Teams lists their own teams.
- Search, a contact's history and the figures on a contact count only those conversations. Contacts stay visible to every member, so a returning customer is recognized.
- Reports compute every conversation figure over the conversations they reach and every handoff figure over their teams. The weekly report email describes the whole workspace, so they do not receive it.
- They are not notified about other conversations, and a teammate cannot mention them there.
- A link to a conversation outside their reach answers that the conversation was not found.
A limited member can still transfer a conversation to any team. Once it belongs to a team they are not on, it leaves their inbox.
The limit follows the member's teams. Adding the member to a team, removing them from one or changing the limit takes effect at once, in the dashboards they have open too.
Answering from Discord and Telegram
A member can answer customers from Discord or Telegram instead of the dashboard. They are the same agent there: the same role, the same conversation access, the same assignments and the same figures. Linking an account is the only step:
- Discord: Settings → Account → Security, then Connect on the Discord row. Signing in with Discord links it too.
- Telegram: on the same page, Connect on the Telegram row opens your workspace's bot in Telegram. Press Start, and the bot confirms the link. The row appears once your workspace has connected a Telegram bot.
Settings → Team → Members shows who has linked an account on each platform your workspace uses.
Once linked, a member's message in a Discord ticket, a Discord mirror thread or a topic of your Telegram team group is their reply, as if typed in the dashboard: it takes the conversation when nobody holds it or when automatic assignment gave it to someone who has not answered, it stops Aiva, it answers the handoff, and it counts in their figures. Their controls act as them: the control post and Manage ticket on Discord, and the buttons on the card pinned at the top of each Telegram topic (claim or unassign, resolve or reopen, stop Aiva or hand it back).
Nobody else reaches a customer from your team places. In a Discord mirror thread or a Telegram topic, a message from someone without a linked account, from a viewer, or from a member limited to other teams stays where it was written, is marked as not delivered, and the place says why once an hour. Being in your Telegram group grants nothing on its own.
Where a customer reads what your staff write directly, in a Discord ticket or a Telegram Business chat, a message from your side that cannot count as a member's reply still reached the customer. It stays in the conversation under the name the customer saw and Aiva steps back, but it counts for no one. For Telegram Business, the member who owns the business account links their Telegram account, and Settings → Channels → Telegram says whether they have.
When a conversation calls for a person (a handoff, a customer writing while a teammate holds it, or a passed response target), the Discord mirror and the Telegram group mention the teammate it is assigned to, through the account they linked. With nobody to name, a handoff or a passed target pings your Discord staff roles, and the Telegram group is notified as a whole.
Who reads your team places
Discord roles and Telegram group membership decide who reads your Discord threads and Telegram topics, not Assistify. A member limited to their teams reads whatever the platform shows them there, other teams' conversations included, but cannot reply to them or act on them from Discord or Telegram. Match your Discord roles and your Telegram group to the people who should read those conversations.
Transfers
With several teams, the control at the top of a conversation shows its team and the person holding it, such as Billing · Ana. Choose another team to transfer the conversation, with an optional note that only your team sees. The receiving team's own wait starts, with its response target when it keeps one, and whoever receives it is told. The teammate who held it is told too, when someone else made the transfer. Aiva keeps answering the customer around a transferred request until a person replies, as after any handoff.
Inbox and reports
With several teams, the inbox lists them under Teams. Each row opens that team's live conversations and counts what the team owes: its handoffs nobody holds yet, and the ones past its response target. A saved view can filter on a team.
In Reports → Workload, you can filter the report to one team and break the trend down by team. Reports → Availability filters to one team too, with the handoffs opened, answered and received outside your hours. Conversations count for the team that holds them now. Handoffs count for the team they went to, and a transferred handoff is its own figure, neither answered nor missed by the team it left.
Deleting a team
The default team cannot be deleted, but you can rename it. Deleting another team moves its conversations and waiting handoffs to the default team; the confirmation states how many. A member for whom it was the only team joins the default team. The websites and channels it took no longer belong to any team.
Webhooks and the API
Every workspace webhook event and the API conversation read carry the team that holds the conversation. The conversation.transferred event names the team a conversation left and the one it reached, and reaches only the endpoints you subscribe to it. See Workspace webhooks.