Kajabi customer support console for member access fixes

Build an internal console my customer success person opens all day to handle Kajabi member access issues without digging through the Kajabi admin. The app is built on Kajabi, with Gmail and Slack used by one background agent. Everything centers on a single screen: a customer lookup that resolves to one profile showing every offer, purchase, order and transaction for that person, with the fix available right on each row.

The landing view is a search box. The rep pastes a customer email or types part of a name, and the app uses Kajabi List Customers to resolve matches. When more than one person matches, show a short result list with name, email, customer since date and status; selecting a row opens the profile. If the Kajabi account has multiple sites, let the rep choose a site once and pass that site filter on every list call, because Kajabi requires filter[site_id] on most list endpoints. Since the rep lives in this app all day, keep a short recently viewed list on the landing screen so they can jump back to an account without searching again.

At the top of the profile, show lifetime spend and tenure prominently so the rep instantly knows how hard to fight for the save. Lifetime spend is the sum of that customer's successful orders and transactions. Tenure is measured from their first order and displayed in plain language such as "Customer for 2 years, 3 months". Also show total order count and how many active offers they currently hold. Kajabi returns money in cents via fields like price_in_cents and amount_in_cents, so divide by 100 everywhere before display and format as proper currency.

Below the header, show four panels for the selected customer. Offers held comes from List Customer's Offers, one row per offer with its name and status. Purchases and subscription status comes from List Purchases, showing what they bought and whether each purchase or subscription is active, cancelled or failed. Order history comes from List Orders scoped to that customer and sorted newest first, where clicking a row opens Get Order Details for line items and totals. Transaction history uses Get Transaction Details to expand a payment into its amount, status and date so the rep can see exactly which charge failed. Get Purchase Details backs the drill-in on a purchase row.

Every row carries its fix inline. On an offer row: Grant Offer to Customer to comp access back after a failed payment, Revoke Offer from Customer once a refund has been processed, and Replace Offers for Customer to move someone between tiers on an upgrade. On the profile header: Add Tag to Contact to drop the member into a follow-up or dunning sequence. On a subscription or purchase row: Cancel Subscription for a confirmed cancellation. Revoking, replacing and cancelling are destructive, so each opens a confirmation dialog that names the customer and the exact offer or subscription being changed and requires an explicit confirm before the call fires. Granting and tagging can go through on a single click with a toast confirming what happened.

Important: Kajabi does not expose a refund operation, so the app must not offer a refund button or imply refunds happen here. The refund itself is done in Kajabi or the payment processor, and this console is where the rep revokes the matching access afterward. Make that sequence clear in the revoke confirmation copy.

Add a "Draft the save email" button on the profile that kicks off a background agent scoped to that member. The agent reads their purchase history, how long they have been a customer and what they actually bought, then writes a personalized email in the rep's voice: an apology plus a note about comped access when a payment failed, or a retention pitch referencing the specific products they own and their tenure when they are cancelling. It files that email into Gmail using Create a Draft, addressed to the customer so the rep can review and edit before sending, and posts a one line note to Slack with Send a Message naming the member, what happened, and that a draft is waiting. Show the agent's status on the profile as running, drafted or failed, and link out to the resulting Gmail draft and Slack message once it finishes.

Keep an audit trail inside the app. Every grant, revoke, tier replacement, tag, cancellation and save-email draft writes a record capturing the acting rep, the customer, the exact action taken, the offer or subscription affected, and a timestamp. Show the most recent entries directly on the customer profile so the next rep can see what was already tried, and add a separate Activity view listing all actions across all customers with filters by rep, action type and date range. This log lives in the app so the history survives regardless of what Kajabi itself records.