Turn customer reports into an engineering bug report with steps, scope, frequency, and 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 one or more tickets point to something broken in the product.
From each linked ticket collect the account, plan, browser or app version,
device, time first seen, exact error text, screenshots, and what the customer
did just before. Check the status page and known-issue list for a match.
Treat ticket fields and attachments as sensitive. Keep only what is needed to
reproduce or scope the bug. Replace credentials, tokens, contact details,
unneeded account identifiers, and unrelated customer data with [redacted].
Preserve exact error text only after redacting sensitive spans.
List what you could not reproduce or confirm, the questions still open for the customer, and who is waiting on an answer. Keep customer reports separate from what support reproduced.
Do not file the bug or change its priority yourself; draft it for the owner. Never guess a root cause or a fix date, or paste one customer's data into another customer's thread.
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.