Teams settings: Allow users to be in multiple teams
A
Ashwin Sadananthan
Business Problem:
Currently, users can only be assigned to one team within a single space on respond.io. This limitation restricts flexibility for users who need to participate in multiple teams, such as Customer Support and Sales, but not Management.
Desired Outcome:
Allow users to belong to multiple teams within a single space on respond.io. For example, a user could simultaneously be part of both the Customer Support and Sales teams while not being assigned to the Management team, enabling better collaboration and access to relevant resources.
Brenda Buckley
I am very interested in the ability to be able to add agents to multiple teams. This wuold be huge for the functionality of my business.
Yasser Soltanieh
Feature Request: Allow a User to Belong to Multiple Teams
Hi team,
I'd like to request an important capability: the ability to assign a single user to more than one Team within a Workspace.
The problem
Currently, a user can only belong to one Team. This becomes a hard blocker the moment you build language-based or skill-based routing, because many sales and support agents are multilingual or cross-functional.
A simple example: a business advertising in both English and Arabic typically has some agents who speak only English, some who speak only Arabic, and some who speak both. The natural structure is an English Team and an Arabic Team, with the bilingual agents belonging to both so they can receive leads in either language.
Today that's not possible. Bilingual agents have to pick one team, which means either one language is under-staffed or businesses are forced into complex workflow branches and external tooling to handle what should be a native routing capability.
Why this matters
This isn't an edge case — it's the default reality for any business operating in multilingual markets (the entire MENA region, Southeast Asia, Europe, etc.). It also applies to agents who cover both Sales and Support, multiple product lines, or act as overflow across teams during peak load or PTO.
What I'd like to see
The simplest version: allow a user to be a member of multiple Teams, with round-robin and least-open-contacts logic including them in every team they belong to.
Thanks for considering this.
A
Alyaa See
Hi Yasser Soltanieh, thanks for the detailed context — this is really helpful.
We understand the need for agents to belong to multiple teams, especially for language-based, skill-based, or overflow routing. We’ve noted your use case and will keep you updated if there’s any progress.
A
Alyaa See
Merged in a post:
That an agent can be in more than one workgroup
O
Oscar Villalobos
The idea would be that the same agent can be in more than one working group in order to give different approaches to their activity and to be able to give greater traceability to the interactions
A
Alyaa See
Merged in a post:
Urgent Feature Request: Multi-Team Assignment for Single User
Mohamed Ashif
Hi respond.io Team,
We urgently need the option to assign one user to two or more teams within the same workspace.
Current requirement:
One staff member handles work for multiple departments, so they need visibility/access to conversations from more than one team without creating duplicate users or changing teams manually.
Requested feature:
Please enable multi-team assignment for a single user.
This is urgent for our operations, as respond.io already supports users across multiple workspaces, but we need the same flexibility at the team level. ()
Mohamed Ashif
Please provide this option i wan to implemented
A
Alyaa See
Merged in a post:
User x Teams
Vicente Falconi
That 1 user can be in more than 1 team, otherwise it limits a lot and you have to do giant workflows for something that doesn't end up being pure round rubin
A
Alyaa See
Merged in a post:
Allow Users to Be أعضاء في Multiple Teams
محمد عباس
We would like to request the ability to assign a single user to multiple teams داخل النظام.
Requirements:
Allow one user to be a member of more than one team
Enable the user to:
Receive conversations from multiple teams
Participate in different workflows across departments
Expected Benefit:
This will provide better flexibility in team management, improve resource utilization, and help balance workload across different departments.
N
Nabilah Binti Salleh
Merged in a post:
Allow user's in multiple work groups
J
Javier Mendez
Please implement the option to allow to have a specific or multiple users in differente work groups.
Ivan Amador
So many years of the application and it is incomprehensible that such a useful function is not implemented from the start and there is so much delay in its implementation.
We have users who speak different languages, we all speak Spanish, one part also speaks English, another part speaks additional Portuguese and a couple of us speak all 3 languages, the simple fact of not being able to organize the teams according to the languages and that the conversations are distributed accordingly, is a disregard for the purpose of Respond.
Have a team in Spanish with all the agents, another in English with the corresponding agents, another in Portuguese with whom they speak that language and the users who speak all 3 languages, added to the 3 groups equally.
We know that AI is something important today, but they cannot concentrate all their efforts on this point as long as important configurations for the distribution of the workload remain in limbo, even more so when they have started to implement functions with fewer votes and less time to be requested compared to this function.
Jerry (CEO)
N
Nabilah Binti Salleh
Ivan Amador: Hi! Thank you for sharing your perspective and for highlighting the importance of this capability. We understand how enabling users to belong to multiple teams could offer greater flexibility and value.
While we don’t have an update to share at the moment, this request is noted and remains part of our broader considerations as we continue to evaluate improvements to team and role management. We’ll be sure to provide an update here when there’s progress to share. Thank you for your patience and for taking the time to provide feedback.
Ivan Amador
Nabilah Binti Salleh It's been almost 5 years since this functionality was first requested and they haven't given it any kind of priority at any time, while other functions requested later have given it due priority and have already been implemented or are under development.
This function (Assigning a user to different Teams) or more simply, being able to have within the Flow generator a functionality to choose the individual agents to whom to assign conversations, would be another solution.
Not everything is AI, “simple” functions should also be a priority because they facilitate the development of the daily activities of the companies that use their service.
Daniel De la Chica
Nabilah Binti Salleh I agree with Ivan. This feature is reasonably easy to implement and has been open for several years. It is also one of the most upvoted features. I don't get why it takes that long to make it work.
Rudy Rocha
Yes please!!
Load More
→