A logical bridge between the conversation and your systems.

No. Each tool shows its status: initial validation or planned integration. A logo identifies a system being considered; it does not establish a completed integration, certification or partnership with its maker. Availability is confirmed for the specific operational journey.

Not necessarily. Implementation identifies which system remains the source of truth and what information the agent needs to read or update. Connecting an existing tool requires reviewing its API, permissions and rules; an API alone does not establish compatibility.

Authentication, permission scope, inputs and results are checked. Failures, retries and repeated operations must also be tested to prevent duplicate changes or false confirmations. Acceptance covers the complete journey, including how the team is notified when something goes wrong.

The agent must not report an operation as complete without valid confirmation from that system. The journey defines what may be retried, what remains pending and when a person must intervene. Recovery behaviour and limits are agreed for each integration.