Refund a damaged order
Use this when a customer reports a damaged item. It takes about a minute in the payments portal.
1. Go to portal.example.com/orders.
2. In Search orders, type the order number.
Use cases
Teams use Autessa Autodocs to turn the tasks they do in web apps into step-by-step guides with screenshots and into workflows that replay those tasks: operations SOPs, support articles, IT how-tos, onboarding guides and no-code website checks.
By team
REFUNDS, ACCOUNT CHANGES, VENDOR PORTAL CHORES
Record the task once for an SOP with screenshots. Replay the workflow from an Autobot on a schedule, and the SOP’s screenshots stay current from those runs.
The feature behind it →ANSWERS THAT WALK CUSTOMERS AND AGENTS THROUGH A PRODUCT
Publish guides to the knowledge base so the support chatbot answers from them, with a highlighted screenshot for every step.
The feature behind it →ADMIN CONSOLE HOW-TOS, ACCOUNT SETUP
Document admin consoles step by step, and give a guide its own agent so a teammate can just ask for it to be done.
The feature behind it →NEW-HIRE GUIDES FOR EVERY WEB TOOL
The person who knows the job records it once; the guide is written for them, ready to edit and publish.
The feature behind it →CHECKING SIGN-UP, SIGN-IN AND CHECKOUT STILL WORK
Replay recorded flows as no-code checks; every step is reported as passed, healed, failed or skipped.
The feature behind it →MONTHLY STATEMENT DOWNLOADS, PORTAL EXPORTS
Record the download once and let an Autobot replay it every month, asking you for a one-time code when the portal needs one.
The feature behind it →KEEPING A LARGE HELP LIBRARY ACCURATE
Runs refresh screenshots and list the steps each site changed, so reviews focus only on what moved.
The feature behind it →MAKING AI AGENT WORK REPEATABLE AND REVIEWABLE
Autobot browser work arrives as draft docs with every step shown; written steps become workflows.
The feature behind it →By industry
Wherever work happens in a browser, the same pattern applies: do it once, document it, replay it.
| Industry | How teams use Autodocs |
|---|---|
| Government and public sector | Procedures for permit, records and benefits portals, documented by staff who do them, with drafts reviewed before publishing. |
| Healthcare administration | Step-by-step guides for scheduling and billing portals; passwords and one-time codes stay out of the docs. |
| Financial services | Repeatable portal downloads and account maintenance with each step’s result reported. |
| E-commerce and retail | Order, refund and catalog tasks documented for support and replayed for routine work. |
| SaaS companies | Help-center articles that refresh their screenshots, plus no-code checks of key flows. |
| Professional services | Client-portal procedures captured once and handed to an Autobot. |
FAQ
To write down how work gets done so anyone can repeat it: SOPs, work instructions, onboarding and support guides. Autodocs writes those guides from a recording and also automates the task.
Yes. Any procedure done in a web browser can be recorded once and becomes a numbered SOP with a highlighted screenshot per step.
It records in a real browser, so it works with websites you can reach and sign in to from that browser.
Pick the one you explain most often.
No extension to install · nothing is published until you publish it
100% customizable, code and all
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours