Understand the subscription
The intended context would distinguish the customer, subscription and billing state instead of treating them as one record.
Integrations Chargebee
ChargebeePlanned
Chargebee subscription context for support.
Plan a Chargebee connection for subscription and invoice context, helping agents understand billing questions before taking action.
Planned connector. Native setup is not available yet. The workflows below describe the intended scope; release depends on provider access and testing.
Billing
What we’re planning to connect.
- 01Chargebee
- 02Planned connection
- 03Message support
Explain invoice questions
Selected invoice details can help an authorized agent investigate an unexpected bill.
Separate lookup from cancellation
A customer asking to cancel still needs an explicit authorized process. A read-only connection cannot change the subscription.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Matched customer
Subscription status
Selected invoice context
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Choose the subscription fields support needs and document how they relate to your service access rules.
- 02
Agree on data and permissions
Decide which fields may be read, which people may use them and whether any separate write action is needed. Native setup is not available yet.
- 03
Define the acceptance test
Test a customer with two subscriptions so an answer cannot accidentally describe the wrong one.
Before you connect
Chargebee integration questions
Can I connect Chargebee to Message today?
The native connector is planned. The workflows on this page describe the proposed design; there is no native installation to activate yet.
What should we test before using it with customers?
Test a customer with two subscriptions so an answer cannot accidentally describe the wrong one.