Customer support

Agentic Commerce Testbench - synthetic data only; nothing here is a real account.

Broadband, TV and mobile support. Sign in to see your bill, pay your balance, change your plan or book a technician.

• Sign in to your account
• Chat with support: check for an outage in your area, ask about your bill, or ask for a person

For developers and AI agents

Start with llms.txt.

• Capability API (REST): every capability as an HTTP operation; see /openapi.json
• OpenAPI 3.1 document: the capability contract with x-agent-* policy
• MCP (streamable HTTP): every capability plus composite journeys as MCP tools
• rest adapter: `rest` - the baseline adapter: the L1 capability API's own HTTP form, as an agent reading /openapi.json uses it. [channel: api]
• a2a adapter: `a2a` - the Agent2Agent protocol, on the official a2a-sdk (1.x, protocol version 1.0; design D5, D8). [channel: api]
• acp adapter: `acp` - Agentic Commerce Protocol 2026-04-17 over REST (upgrade-acp-2026-04-17; spec protocol-adapters.1/.2). [channel: api]
• acp-mcp adapter: `acp-mcp` - Agentic Commerce Protocol 2026-04-17 over its MCP binding (upgrade-acp-2026-04-17; design D19). [channel: api]
• chat adapter: `chat` - a personal agent typing into the provider's chat widget, served by a pattern-NLU stand-in (lossy). [channel: chat]
• voice adapter: `voice` - the agent places a phone call into the provider's IVR / voice bot: chat plus a speech transform. [channel: voice]
• ACP discovery: Agentic Commerce Protocol 2026-04-17
• PAP discovery (poppy.json): Personal Agent Protocol draft 0.2 (39b35bd)
• A2A Agent Card: A2A discovery (404 until A2A is enabled)
• OAuth server metadata: simulated sign-in (code + PKCE)
• OAuth resource metadata: scopes account.read / account.write
• Customer sign-in: the customer signs in and grants your assistant access