If you run other ResultsAIx plugins on the same site, the desk reads them automatically and builds one profile per customer: what they spent, clicked, bought and subscribed to. That profile appears on every ticket as Customer 360, and the AI replies from it.
Detected on this site, zero setup:
- WP Conversion Tracker: tracked purchases with revenue and the link each sale came through.
- Audience Vault: lifetime clicks, conversions, revenue, VIP flag and last seen.
- ResultsAiX Mailer: subscriber status, lists, opens, clicks and engagement score.
- ResultsAiX Engage: opt-ins, with the campaign and page they came from.
- Launch Manager: launch sales history with product, amount, gateway and refunds.
Each detected plugin gets a card on the Integrations tab with a toggle, on by default. Untick a card to leave that system out of lookups without uninstalling anything.
Connecting Results AI Commerce:
- Copy the receiver URL from the Commerce card on the Integrations tab.
- In Commerce admin open Settings, WP Sync integration, paste the URL and set a signing secret.
- Paste the same secret on the desk's Commerce card and save.
- Use the test button in Commerce. The card flips to Test received when the ping lands.
If WP Sync already receives the Commerce push, add the receiver URL as a Forward URL on the WP Sync Commerce connector instead, and leave the secret blank on the desk side, because the relay does not carry the signature header.
Connecting the Results License Server:
- Enter the server URL and its hub shared token on the License Server card, then save.
- Click Test Connection. A green message means the token was accepted.
From then on, a license ticket pulls every key the customer owns in one call, and payment history on servers that expose the orders endpoint.
Proving it works:
At the bottom of the Integrations tab, type a real customer email into Customer Lookup. What you see is exactly what the ticket sidebar shows and what the AI replies from. If it looks right there, it is right everywhere.
About the totals:
The same purchase can legitimately be recorded by more than one system, for example an IPN tracked by WP Conversion Tracker and the same sale imported into Launch Manager. Totals are therefore shown per system, and the AI is instructed never to add systems together into one combined figure.
Customer portal and one-time sign-in links:
If you run a self-service portal with magic-link login, connect it on the Customer Portal card: the portal URL plus the support_link_secret from the portal's config. Every ticket and contact page then has a Send Portal Sign-In Link button, and license auto-resolves email the customer their one-time link as part of the reply. The portal sends that email itself, so the link never passes through your site, and the reply only claims a link was sent when one actually was.
Bought under a different email:
Open the customer's contact page and add their other addresses under Linked emails. Every lookup, the ticket sidebar and the AI replies then search those addresses automatically.
Watching the feeds:
The Diagnostics tab has a Connected Feeds panel showing when each feed last delivered. A feed that was active and then goes quiet for a week gets a warning, because a removed webhook URL fails silently otherwise.
Connecting your own database:
If your sales live in your own system, open Advanced: Connect Your Own Database on the Integrations tab. Point the desk at any table, in this WordPress database or an external MySQL, and map which columns hold the email, product, amount, date and status. Those rows then join every customer profile like the rest of the stack.
- Not sure of the columns? Click Let AI Map It. The assistant reads the table structure and two sample rows (emails masked) using your own Claude key, and proposes the mapping for you to confirm.
- Click Test With An Email to run the exact profile lookup against the mapping before saving.
- For an external database, use a read-only MySQL user. The desk only ever reads.
Developers can also add any data source in code with the asd_customer_profile filter.