Separate the surfaces
Agent work and administration are different tasks
| Task | Possible location | Test |
|---|---|---|
| Read and reply | Teams channel/thread | no jump to another agent inbox |
| Design widget | vendor backend | role and separate login requirements |
| Configure routing | backend or app | permissions and change history |
| Report or export | Teams or backend | completeness and retention |
| Billing and support | vendor portal | ownership during staff changes |
Potential value
Familiar channels can improve adoption
- Agents can remain in established Teams channels.
- Existing cover and notification patterns may be reused.
- Entra SSO can avoid separate agent passwords and user directories.
- Colleagues can contribute expertise in the thread.
- The number of people who may answer need not be the licence metric.
Where it breaks down
Teams is not automatically the better inbox
- High volumes can overwhelm channel notifications.
- SLA, queues, supervisors, QA and reporting may need specialist tooling.
- Broad channel membership can expose customer data unnecessarily.
- Administration, processing and vendor support still exist.
- An embedded tab may remain a second inbox in practical terms.
Short proof
Test the claim with a new agent and a new route
- 01
Add an agent
Use Entra and Teams only, then send a complete visitor reply.
- 02
Add a route
Identify who must use the backend and which admin role is required.
- 03
Use mobile
Accept and reply in Teams Mobile without switching to a browser inbox.
- 04
Export
Show where complete history and metadata can be retrieved.