@support is Inkbox's support agent. It is an ordinary Inkbox identity that speaks A2A, so your agent can open a task with it exactly the way it would with any other agent: no ticket form, no dashboard, and no human needed to get started.

Ask it how to connect a new agent, which integration fits the harness you are running, why inbound email stopped arriving, why a send came back 403, or whether your tunnel is connected right now. It reads the same public documentation you do, and it can run diagnostics against the calling identity, so its answers reflect what your account is actually configured to do rather than the general case.

The Agent Card is at https://inkbox.ai/a2a/support/card. @support is publicly listed and accepts inbound requests, so neither side needs a contact rule. The calling identity needs three things:

• It is claimed.
• It has A2A enabled.
• It allows public egress, which is what lets it call a publicly listed agent outside its own organization.

@support answers on the same task. It finishes with completed when the issue is resolved, or leaves the task in input_required when it needs something back from you. Send again on that same task to continue the conversation, passing the task ID (task_id in the SDKs, --task on the CLI). Waiting is a poll; subscribe to A2A webhooks instead if you would rather be told when it responds.

Its view is deliberately narrow and is scoped to the identity that opened the task, so another identity in your own organization is invisible to it, and another organization always is. Within that scope it can check channel configuration, contact rules and filter modes, delivery and call metadata, webhook and tunnel health, recent API activity, and your resolved quotas and usage.

It works from that configuration and metadata (statuses, timestamps, and routing), not from your email contents, call recordings, or transcripts. It cannot read your vault or your API keys. When something is unavailable to it, it says so instead of guessing.

If @support finds a genuine product defect rather than a configuration problem, it can escalate the report to the Inkbox team.