Use when a fraud alert fires, a payment looks stolen, an account looks taken over, or a chargeback notice lands: verify, hold-or-clear, and defend with evidence.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when a fraud alert fires, a payment looks stolen, an account looks taken over, or a chargeback notice lands: verify, hold-or-clear, and defend with evidence.
You need the alert or chargeback notice, the transaction records (amount, method, date), the customer's history, and the fraud-hold authority from prefs.
Confirm the amount, method, date, and account, each labeled FACT or UNKNOWN. Pull history for velocity, new device or address, and past friendly-fraud markers. A case with no transaction record is UNKNOWN, never "confirmed fraud".
Write one block with signals for and against, each with its source. Check account-takeover signs (credential-stuffing pattern, email or password changed just before spend) separately from first-party abuse (the customer disputes their own real charge).
Clear with a one-line reason when the evidence is thin, or stage a hold for owner yes when money is still moving. Never hold funds, lock an account, or accuse the customer before the owner says yes.
Look up the reason code first and match compelling evidence to that code: the order receipt, delivery or usage proof, the customer's own messages, and the policy quote with its source, plus a short rebuttal letter. File it only after approval, then diary the representment date — the deadline for resubmitting evidence to the card network. Track win rate per code; after a loss, stage the second-chargeback or pre-arbitration path.
Log the outcome on the case: cleared, held, or defended, with the evidence IDs. Offer to draft the customer-facing line — plain, no accusation — when the owner wants contact.
Deliver the risk profile, the hold-or-clear call, and the staged hold or defense packet with its evidence list.
No transaction access means an UNKNOWN profile with the access need named, not a padded verdict. Say which record would settle it.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.