For SaaS support teams

A plan question. An answer from your subscription system.

Connect your read-only subscription API so customers can check their plan and available seats in the conversation. Your system supplies the facts; account changes stay with authorized people.

Start free trial

Sample data · fictional

SaaS

Customer

Which plan are we on, and can we add one more seat?

Read-only tool

get_subscription() → plan: "Team Demo", seats_used: "4/5", extra_seat: "1 available"

AI reply

You are on Team Demo with 4 of 5 seats in use. One seat is available. Your administrator can add a teammate; this lookup does not change your subscription.

This lookup reads subscription details. Changes stay with your team or the customer’s administrator.

A subscription lookup scoped to the session

Tool name: get_subscription
Description: Read the plan, used seats, and available extra seats for the authenticated account.
Endpoint URL: GET https://api.example.com/accounts/{account_id}/subscription
Authentication: Authorization: Bearer {{SUBSCRIPTION_API_SECRET}}
Input mapping: account_id ← server.session.account_id customer_id ← server.session.customer_id
Output mapping: plan ← $.subscription.plan seats_used ← $.subscription.seats_used extra_seat ← $.subscription.extra_seat

Example configuration for your read-only subscription API. Replace the endpoint and field mappings; no native billing connector is implied.

Account and customer identity come from server.session, not chat input. Your endpoint must verify account membership and permission before returning subscription fields.

Read the plan and seats from your source

Configure get_subscription to return plan, seats_used, and extra_seat from your subscription API. Explain the current values without guessing about entitlements or availability.

Scope the lookup to the authenticated account

The server supplies account and customer identity from the authenticated session. Your endpoint must verify membership and permission before returning that account’s subscription.

Return only what the answer needs

Map the plan and seat fields needed for the conversation. Keep API credentials on the server and exclude payment details, private member records, and unrelated account data.

Keep changes with an authorized person

The lookup does not add seats, invite teammates, upgrade plans, or cancel subscriptions. Explain the next step and hand requests for changes to your team or the customer’s administrator.

Questions before you connect

What do we need to connect subscription data?

A read-only API you control, server-side credentials, and mappings for the plan and seat fields. Configure the endpoint and authorization checks; this is an example setup, not a native billing-platform connector.

Can a customer ask about another account?

A chat message does not establish account access. The server takes identity from the authenticated session, and your endpoint must verify membership and permission for the account being queried.

Can the assistant add a seat or change the plan?

No. Version one reads subscription details only. An authorized administrator or your team must make any changes through your existing account workflow.

Is the Team Demo conversation live account data?

No. The plan, seat counts, and replies are fictional example data. Real answers depend on the connected API and the current customer’s permissions.

Let customers ask. Let AI check your system.

Connect your knowledge and read-only APIs for orders, transfer status, invoices, or plans. Answer in your customer’s language.

Start free trial