Follow the transaction
A proposed lookup would help agents locate the transaction relevant to the support request.
Integrations Paddle
PaddlePlanned
PaddlePlannedPaddle billing questions, with useful context.
Plan a Paddle connector for selected customer, transaction and subscription context without exposing billing records through public search.
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.
- 01Paddle
- 02Planned connection
- 03Message support
Keep subscription context separate
The customer’s transaction history and recurring subscription status should not be conflated.
Preserve financial controls
Refunds, payment changes and subscription edits require separate permission and are outside the proposed read-only scope.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Confirmed customer
Selected transaction
Subscription reference and state
Prepare for the connection
Define your first workflow.
- 01
Choose the first workflow
Identify whether the support question concerns a transaction, a subscription or both.
- 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 several purchases for the same email and require an unambiguous record before sharing details.
Before you connect
Paddle integration questions
Can I connect Paddle 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 several purchases for the same email and require an unambiguous record before sharing details.