Write a help article from repeat tickets, using only confirmed steps and the customer's own words.
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 question keeps coming back and the help centre does not answer it well.
Choose one question. Count the tickets that asked it, the period, and the plans affected. Pull the phrases customers used, since those are the words they will search for. Check whether an existing article already covers it and should be fixed rather than replaced. Remove names, contact details, account identifiers, and private business details before using customer wording. Generalise any phrase that could point back to one customer.
Use only steps that the product notes confirm or a teammate has tested. Mark any step that needs a screenshot or a check in the product.
In an internal approval note, list the ticket ids the article came from, the notes or teammates that confirmed each step, and the open questions. Keep that note out of the publishable article.
Do not publish the article or edit the help centre yourself. Never document a workaround or limit that nobody has tested or confirmed.
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.