Subscriptions

Overview

Subscriptions are read through connectors for recurring-billing, payments, membership, e-learning and email-marketing platforms. When a connector with the subscriptions capability is used to verify customers, the platform adds a My Subscriptionstool to your bot. Like every account tool it is verified-only: it runs after the customer has passed the one-time-code check, never before.

Questions it answers

The subscription shape

Every source is mapped to the same core fields; id and plan must be present for a row to count. Dates are normalised to YYYY-MM-DD, and amounts reported in minor units are converted to pounds.

Mailing-list platforms (Klaviyo, MailerLite, Kit, Omnisend and others) use the same shape to report which lists a customer is subscribed to, so the bot can answer “am I still on your newsletter?”. Each connector’s page lists exactly which fields it maps.

The subscriptions endpoint the bot calls

1. 1
   The session token identifies the customer record found in your platform during verification.
2. 2
   The platform reads that customer’s subscriptions from the vendor’s documented API with your encrypted credentials.
3. 3
   Rows are mapped to the standard shape; any row naming a different customer’s email address is removed.
4. 4
   The bot answers from the rows returned, and nothing else.

{
  "success": true,
  "subscriptions": [
    {
      "id": "sub_1Nx42eLkdIwHu7ix",
      "plan": "Pro Monthly",
      "status": "active",
      "next_billing": "2026-11-01"
    }
  ]
}

Plans from your own system

If you run your own billing platform, the plan and renewal date belong in your Account Connect /account-summary response — there is no separate subscriptions endpoint in Account Connect. The live demo shows the pattern: its account summary carries the plan, monthly price and contract end date.

# export SESSION=<the session_token returned by POST /verify-otp>
: "${SESSION:?export SESSION first}"
curl -s -X POST "https://www.siluxchat.com/api/account-connect-demo/v1/account-summary" \
  -H "X-API-Key: demo-account-connect-key" \
  -H "Content-Type: application/json" \
  -d "{\"session_token\":\"$SESSION\"}"

{
  "success": true,
  "account": {
    "account_number": "C1002",
    "status": "active",
    "plan": "Unlimited Calls Bundle — 24 months",
    "monthly_price": "£29.95",
    "contract_end": "2028-01-15",
    "balance_due": "£29.95",
    "name": "Jane Demo"
  }
}

If a customer holds several plans

Return them as a short array inside the account object. Keep it compact — the bot reads roughly the first 2,000 characters.

{
  "success": true,
  "account": {
    "account_number": "C1001",
    "name": "Test Customer",
    "subscriptions": [
      { "id": "S-11", "plan": "Business Line", "status": "active", "next_billing": "2026-10-01", "amount": "£19.95" },
      { "id": "S-12", "plan": "Broadband 500", "status": "active", "next_billing": "2026-10-01", "amount": "£32.00" }
    ]
  }
}

Subscription connectors

Several of these (Stripe, Chargebee, Recurly, Paddle and others) also read invoices, so one connection can answer both “when is my next payment?” and “has my last one gone through?”. See Billing & invoices.

Cancellations and changes

Because the bot cannot change a subscription, cancellation and plan-change requests follow your process:

• Put your cancellation terms — notice periods, cooling-off rights, early-termination charges — in your knowledge base, so the bot states them accurately and consistently.
• The bot reads the customer’s plan and term end so it can explain what applies to them, then raises a support ticket for your team to action the request.
• If your platform offers a self-service cancellation page, add the link to your knowledge base and the bot can point customers to it.

Errors and edge cases

Full reference: Troubleshooting.

Get help

Using a membership or billing platform that is not listed? Email support@siluxcall.co.uk and our integration team will help you find the best route.