Skip to content

Overview ​

Customer context lets a draft cite what a customer actually bought, pays for or is licensed for. When someone writes in about an order, a renewal or a license, Overdesk looks them up in the stores and billing systems you connect, so the draft answers the question instead of asking the customer to repeat their order number.

Sources you can connect ​

SourceCategory on IntegrationsWhat a draft can cite
StripeBillingSubscriptions, prices, renewal and end dates, failed payments, recent invoices
ShopifyCommerceOrders, what was paid, what has shipped, order count and total spend
WooCommerceCommerceOrders, what they cost, order status, refunds, order count and total spend
FreemiusLicensingLicense plan and status, expiry, sites in use, payments and refunds

Plans ​

Customer context is part of the Pro and Scale plans, and of the free trial. On Assist, each of these sources shows Included on Pro and Scale in place of its connect form. If a workspace moves to Assist with a source still connected, its page says Connected, but not in use on your plan and drafts stop citing it. Moving back to Pro resumes it on the next draft, with nothing to reconnect. See Plans and pricing.

How it works ​

  1. An admin connects a source from Integrations. Overdesk only reads through every connection, and each setup page asks for the narrowest key that system offers.
  2. Each time a draft is written, Overdesk looks the customer up by the email address they wrote in from, in every source you connected, at that moment.
  3. The draft gets their recent history: up to the 10 most recent orders and the 5 most recent payments, plus totals such as order count and lifetime spend when the source can show the whole history.
  4. Your team reads the draft, with those details in it, before anything reaches the customer, unless your workspace has turned sending on and your guardrails approve the reply; see Sending.

A source that is slow or unavailable does not stop a draft. Overdesk waits a few seconds at most, then writes the draft without it.

What Overdesk keeps ​

For a draft, Overdesk reads these systems while it writes and keeps no copy of the orders, subscriptions, licenses or payments it reads. For each draft it records only which sources it checked, and whether each one found the customer, had no record of them, or could not be read. The draft's own text, including anything it quotes, is stored like every other draft.

For a finding, Overdesk keeps a little more. After Churn signals or Frustration signals names customers who may leave, it looks them up in Freemius and Stripe and keeps, with the finding, the licenses or subscriptions each holds, when they expire or renew, and what they have paid, so the finding can say what is at stake. It keeps no email address, name, license key, order, site or payment, and none of it reaches the AI model. It ages out with the finding and goes when you erase that customer. See Intelligence.

Disconnecting a source deletes its stored credentials. Anything a finding already keeps from it stays with that finding until the finding ages out or you erase the customer.

Names that a store or billing system holds are masked before anything reaches the AI model, the same way the name from your help desk is, and restored in the draft your team reads. See How customer data is handled.

What it never does ​

  • It never changes anything in these systems: no refunds, cancellations, charges, order edits or license changes.
  • It never reads a whole license key into a draft. Freemius licenses show the last four characters of the key only.
  • A purchase made under a different email address, or as a guest in WooCommerce, is invisible to the lookup. Drafts are told the account data may be incomplete and never to tell a customer that an order or license does not exist.