Phone cancellation, integrated into your product.

A result with evidence

The goal is to return a confirmation number, effective date and a filtered excerpt supporting the cancellation. We review evidence before charging. No success or an inconclusive result means no charge.

How the integration would work

1. POST a request with the current mandate accepted by the account holder. An integrator cannot replace that authorization.
2. The agent identifies itself as AI. The holder must be able to join the call for identity verification if Xfinity asks; otherwise the request remains incomplete.
3. A signed result webhook, planned for the pilot. B2B authentication, signatures, retries and the delivery contract for integrators still need to be defined.

Proposed volume success fee

USD 9.00 per confirmed cancellation. Final pricing will be confirmed before the pilot starts. No success, no fee. Provider balances, fees and equipment are excluded.

Pilot limits

Residential Xfinity cancellations in the United States only. We do not promise maximum completion times or that the provider will accept AI representation. The pilot requires telephony validation, holder participation and human review; it is not open yet.

API draft

Illustrative example of the existing web contract: POST /api/jobs, authenticated with a Google ID token, then GET /api/jobs/:id. POST is blocked in waitlist mode. This is not yet an integration contract.

Read the mandate version from GET /api/product-config; accepted:true applies only after the holder actually accepts it. POST creates a request: it does not start a call. The current flow requires PayPal authorization and a separate dispatch.

POST /api/jobs
Authorization: Bearer <Google ID token>

{
  "playbook": "xfinity-cancel",
  "customer": {
    "name": "Example Holder",
    "account_number": "EXAMPLE-ACCOUNT",
    "address": "123 Example Street",
    "zip": "10001"
  },
  "customer_phone": "+12025550123",
  "services": [
    "internet"
  ],
  "language": "en",
  "mandate": {
    "version": "2026-10-15.1",
    "accepted": true
  }
}

Illustrative creation response · 201

{
  "job": {
    "id": "example-job",
    "state": "created",
    "price": "14.99",
    "services": [
      "internet"
    ],
    "language": "en",
    "report": null,
    "receipt": null,
    "verification": null,
    "reviewReason": null,
    "failureReason": null,
    "paymentStatus": null,
    "createdAt": 1792022400000,
    "updatedAt": 1792022400000
  }
}

price is the current web-product fee (USD 14.99 by default), not the proposed B2B fee. Actual amounts are set by the server, never sent by the client.

Illustrative excerpt from GET /api/jobs/:id after completion

{
  "job": {
    "id": "example-job",
    "state": "succeeded",
    "report": {
      "cancellation_confirmed": true,
      "confirmation_number": "EXAMPLE-REF",
      "effective_date": "2026-10-15",
      "services_cancelled": [
        "internet"
      ],
      "customer_auth_completed": true,
      "evidence_excerpt": "The internet service cancellation is confirmed, effective October fifteenth. Reference EXAMPLE-REF."
    }
  }
}

The existing HMAC webhook runs from the calling engine into CallHandler; it does not deliver results to businesses. There is no public B2B subscription endpoint or accepted callback_url field on creation.

Request B2B pilot access

Contact details and business context only. Do not include customer details, accounts, PINs, SSNs, verification codes, passwords or cards. We store your request to evaluate interest and contact you about the pilot.