Asking questions of your data, as it is right now

Ask Claude or ChatGPT about your recent signups, trials, payments and attribution, and Retrixus reads them straight from Recurly. No waiting for a data sync. Up to the last 7 days; older questions belong in your warehouse.

Some questions are about one customer: "why was Jordan Ellis charged twice?" Others are about everyone: "how many trials started in the last two hours, and where did they come from?"

For the second kind, Retrixus reads the records straight from Recurly when you ask, so the answer is as current as Recurly is. If your company also copies Recurly into a data warehouse such as Snowflake, that copy usually runs an hour or two behind. This covers the gap.

Questions you can ask

Ask in your own words. For example:

• "Look at all trial signups in the last two hours and give me their attribution."
• "Did any direct signups come in with no source today?"
• "How many customers signed up from affiliates this morning? Break it down by affiliate."
• "Which payments were declined in the last hour, and why?"
• "Show me today's signups whose card was issued outside the US."

Claude or ChatGPT works out the rest. It looks at what your Recurly site records, including your own custom fields, which is usually where marketing sources and affiliate IDs live. Then it asks Retrixus the precise question.

What it can see

Records created in the time you ask about, on the sites you can use:

• Customers: who signed up, when, and every custom field your site uses (UTM source, medium and campaign, affiliate references, landing page, and so on). Also the card on file: its first six and last four digits, the country that issued it, whether it is credit, debit or prepaid, and which payment gateway it is pinned to.
• Subscriptions: plan, state, price, trial start and end, cancellations.
• Payments: purchases, refunds and verifications, with the amount, the outcome, the decline reason, and the fraud score where your site has one.

A full card number never appears. Recurly does not provide one, and Retrixus would not show it.

How far back

Up to 7 days. That is plenty for the gap before a warehouse catches up, and for a recent problem. For anything older, ask your warehouse. A question about the last two hours on a busy site takes a few seconds. A week takes longer, because Retrixus reads every record in that week.

If a question would need more than Retrixus will read in one go, the answer says so. It is labelled incomplete, and its numbers are a floor rather than a total. Ask for a shorter time, or one site instead of all of them.

Getting the rows themselves

An answer shows up to 50 rows. When you want all of them, for a spreadsheet or to work through, say so: "…and give me the full list as a file." You get a download link that works for one hour.

What it cannot do

Asking only reads. A question never cancels, refunds or changes anything in Recurly. Changes are a separate step, shown to you first and done only when you say yes: see Fixing many accounts at once.

Every question asked this way is recorded in your organisation's audit log, with who asked it.