Support platforms now ship AI agents that can call outside tools and, increasingly, other companies' agents. Two open protocols carry that traffic. Neither says who an outside agent belongs to, what agreement covers the exchange, or which partner agent handles a given product, and those are the questions TSANet already answers for people. This page sets out what the protocols and the platforms support today, where a neutral member organization fits, the direction TSANet is considering, and what you can do with an agent and Connect right now. Nothing on the agent-to-agent side is built, and every claim says how it was checked.
This page describes a direction, not a product. The protocol and platform facts were read from the sources in the Verified against table on the dates shown there. The TSANet pieces are proposals: none is approved, scheduled or built, and none has been tried against a member's agent platform. What works today is the Connect REST API, which any agent can already call.
The gap
The protocols make it technically cheap for one company's agent to reach another's. They solve the connection. They do not solve four things that two support organizations have to settle before their agents can work a mutual customer's problem:
| Question | What the protocols say | What TSANet does today, for people |
|---|---|---|
| Who is this agent, and which company answers for it? | A2A lets an agent sign its own card. Verifying that the signer is who it claims to be is left to whoever runs a registry. No cross-company agent identity standard has been ratified. | Vets members before they can open or receive a case. |
| What agreement covers what the two agents exchange? | Out of scope for both protocols. | One Code of Conduct, with an addendum for each relationship type, in place of a contract between every pair of members. |
| Which partner agent handles this product, and what does it need to start? | A2A describes curated registries but does not define one. | The partner directory, and each partner's process form with its required fields. |
| What happened on the case, and who is accountable? | Each side keeps its own task history. | One case record that both members see, with a respond-by time. |
As read
| MCP | A2A | |
|---|---|---|
| What it connects | An agent to a tool or data source. | An agent to another agent, which takes on a task. |
| Governance | The Agentic AI Foundation, under the Linux Foundation. PRIMARY | The same foundation. PRIMARY |
| Version read | Specification 2026-07-28. PRIMARY | Specification 1.0.0. PRIMARY |
| What matters here | A server must accept only tokens issued for itself and must not pass them on to another service. Sessions are gone: each request stands alone. Machine-to-machine sign-in is an optional extension, not part of the core. | An agent describes itself in a card that can be signed. Registries of cards are described but deliberately not standardized. A formal extension mechanism lets a group add rules for one use case without changing the protocol. |
| What it does not cover | Shared memory or context between agents. | Shared memory, and trust between organizations. |
Comparison
Every platform below can reach an outside MCP server. Fewer speak A2A. The column that decides whether a hosted server is usable is the third one: how the platform is able to sign in to it.
| Platform | MCP | A2A | Sign-in it offers to an outside MCP server | Evidence |
|---|---|---|---|---|
| Salesforce Agentforce | Client and server | Inbound and outbound; an administrator registers each outside agent | None, or OAuth client credentials | PRIMARY |
| ServiceNow | Client and server; its client speaks MCP 2025-06-18 | Client and receiver, on A2A v0.3 rather than 1.0; no streaming, parallel tasks or artifacts yet | None, an API key, or OAuth | PRIMARY vendor community and documentation |
| Microsoft Copilot Studio | Client; server in preview | Calling other agents is generally available. Being called is in preview, in early-release environments only, for a signed-in user of the agent's own tenant. Whether another company's agent can call in is NEEDS PROBE | None, an API key, or OAuth with a signed-in user | PRIMARY see Agentic usage |
| Microsoft Dynamics 365 Customer Service | Server, open to non-Microsoft clients | None found | Not applicable: it is a server | PRIMARY |
| Zendesk | Client; no server confirmed | None found | Not read | SECONDARY |
| Fin | Client and server | None found | A fixed token, or OAuth through one connection shared by the whole workspace; no per-user sign-in | PRIMARY for sign-in; SECONDARY for the rest |
Three things follow from the table.
Direction
The direction is to extend what TSANet already does for people to agents, on top of the open protocols, and not to invent a protocol or operate agents. Members' agents stay the members' own, on whatever platform and model they choose.
A hosted server a member registers once in its agent platform. Its tools find a partner, read the partner's process form, open a case, respond, add notes and close, under the member's own Connect credentials. It holds no cases; Connect stays the record.
A published extension that says how a collaboration case travels as an A2A task: the fields a partner's form requires, how Connect's case status maps to task states, and how either side asks for a person to take over.
A curated registry of members' support agents, in which TSANet attests that each agent belongs to a member in good standing. A2A leaves registries to implementers; the attestation is the part a membership body can supply.
Members accept a Code of Conduct, and each relationship type is defined by an addendum to it. Neither mentions automated agents. The approach under consideration has two parts, because they would bind different members.
| A short change to the Code of Conduct | An opt-in agent addendum | |
|---|---|---|
| Would cover | Two confidentiality points. What an agent retains is not the unaided memory of a person, which the Code excuses. Training or tuning a model on a partner's case content is not a permitted use of it. | Operating terms: the member answers for its agent, a partner is told when it is dealing with an agent, either side can require a person, how long partner content is kept, and listing in the directory. |
| Would bind | Every member, because these points protect the member whose content it is. | Only members that accept it, before their agents take part. |
| Adopted by | The Board, under the Bylaws, with notice to members before it takes effect. | The Board, then accepted by each member that wants it. |
Mapping
Connect's case statuses line up with A2A's task states closely enough that a case can be carried as a task. The statuses below are from the Connect API specification. The mapping is a first pass, and which transitions Connect allows between them has not been checked on Beta.
| Connect case status | A2A task state | Note |
|---|---|---|
OPEN | Submitted or working | Waiting for the receiving member to respond. |
INFORMATION | Input required | The receiver has asked the submitter for more. |
ACCEPTED | Working | An engineer is engaged on the receiving side. |
REJECTED | Rejected | Final on both sides. |
CLOSED | Completed | Final on both sides. Connect has no reopen. |
A2A's states are coarser than Connect's, so the Connect status would travel in the task's metadata and remain the authority. Notes map to task messages. NEEDS PROBE
Now
None of the proposed pieces is needed to put an agent to work on partner cases. The REST API is the same for an agent as for a connector.
Give your agent tools that wrap the Connect operations it needs. The API page covers the behavior that is easy to get wrong, and how a member issues its own client secret.
Working with the API → ShippedThe skills TSANet ships teach an assistant the Connect semantics, and the topic compares what each provider's agent framework needs from the API.
Agentic usage → ShippedIf your agent's tools run on the JVM, the SDK already carries authentication, the case lifecycle and the local cache.
Connect SDK →Unknowns
| Question | What it decides |
|---|---|
| Which sign-in mode reaches a working call from each platform against a hosted Connect MCP server | Whether one server serves every platform, and where it has to run |
| Whether platform agents can send A2A structured data and activate a custom extension, or only text | Whether a support extension is usable from those platforms or only from in-house agents |
| Which transitions Connect allows between case statuses | The lifecycle mapping above |
| Whether the two confidentiality points clarify the Code of Conduct or change it, and how an opt-in agent addendum is adopted | The terms agents work under, and everything beyond a tool server. A question for counsel and the Board, not engineering |
| Whether members want this yet | The order of the three pieces, and whether to build them at all |
Verified against
| Read on | Source | Used for |
|---|---|---|
| 2026-11-10 | A2A specification 1.0.0, agent discovery and extensions | Task states, signed agent cards, registries left unstandardized, what an extension may and may not change |
| 2026-11-10 | MCP specification 2026-07-28: authorization and key changes | Token audience rule, no token forwarding, removal of sessions, machine-to-machine sign-in as an extension |
| 2026-11-10 | Agentic AI Foundation | Both protocols hosted by one foundation |
| 2026-11-10 | Salesforce: Agentforce interoperability guide, register an external MCP server | A2A inbound and outbound, MCP registration and its sign-in types |
| 2026-11-10 | ServiceNow: enable MCP and A2A (FAQ), Action Fabric | MCP client and server, A2A roles, sign-in types; re-read 2026-11-17 for the A2A and MCP versions (page last updated 2026-09-04) |
| 2026-11-10 | Microsoft: What's new in Copilot Studio, MCP and A2A channels (preview) (read 2026-11-17), Dynamics 365 Customer Service MCP server, agents across a multitenant organization | A2A general availability, inbound MCP and A2A in preview and their sign-in, the MCP server and its clients, single-tenant agent identities |
| 2026-11-10 | Fin: add MCP connectors | Sign-in types for a custom MCP server; re-read 2026-11-17 for the shared OAuth connection |
| 2026-11-10 | Third-party write-ups and search summaries | Zendesk's MCP client; Fin's MCP server and client roles. Marked secondary where used |
| 2026-11-10 | The Connect API specification (private repository) | Case statuses |
| 2026-11-11 | TSANet legal documents: the Code of Conduct, the relationship addenda and the Bylaws | What members agree to today, and how the Code is changed |
| not probed | Any TSANet component registered in any agent platform; inbound A2A on Copilot Studio from another company's tenant; Connect's status transitions; structured data and extensions from platform agents | Each is marked where it appears |