Integrations
Published Updated
Before connecting your store: define data and actions
An integration name alone does not explain how your team will use it. Start with the customer question you want to resolve, then identify required data, who can read it and which actions need separate approval.
Start with a clear service question
For example, a customer asks about an order. The teammate needs its reference and available information, then explains the state supported by that data.
Do not assume that viewing an order allows cancellation, refunds or shipping changes. These are separate actions whose support and permissions must be checked.
Define connection and identity
Check the intended store, responsible account and requested permissions. Decide how contacts map to orders, especially when the contact number differs from checkout details.
A similar number or matching name is insufficient reason to disclose another person’s order. Use appropriate verification before sharing details.
Test success and missing information
Test a known order, an unknown reference and insufficient data. Review what the interface displays when access is denied or the connection fails.
When information appears old, check its source, update timing and integration scope before presenting it as certain.
Agree on ongoing operations
Name the person responsible for reauthorization and connection errors, and define what teammates should do when data is unavailable.
Confirm integration scope, plan requirements and setup with the team before relying on it for all conversations.
Apply these steps in your account
Create a Message Pro account and start with the workspace, then use the Help Center for setup steps.