You spot the question while you are away from your desk. A teammate asks how to change their notification settings, or you notice the password reset screen confuses everyone, and you want to write the FAQ entry while it is fresh. You are on your phone. Phone browsers cannot capture the screen the way a laptop can, so the capture button is not your path here. The fix is simple: take a normal screenshot first, then add it.
Here is the whole flow for one entry, top to bottom, in the order you actually do it.
Step 1: Take the screenshot on your phone the normal way
Open the screen the FAQ is about, whether that is your app, a settings page, or a web page. Take a screenshot with your phone's usual shortcut (side button plus volume up on iPhone, power plus volume down on most Android phones). The outcome: a still image sitting in your camera roll, showing exactly the state you want to explain. If the screen scrolls, take two or three shots so each covers one piece of the answer.
Step 2: Open a new review and add the image
In your phone browser, go to start a new review. There is nothing to install, no extension, and no password to set up. Tap Add image and pick the screenshot from your camera roll, or paste it if you copied it. The still becomes an item in the review. This is the same path a desktop reviewer uses when they annotate a screenshot in a browser tab, minus the live capture step that phones do not support.
Step 3: Pin the exact spot the answer is about
Tap the still to mark it. Drop a numbered pin on the control you are describing: the toggle, the menu item, the button people miss. Add an arrow or a box in a bright color if a whole region matters. Keep text labels to a single short line, since they are labels, not sentences. The pins and drawings are baked into the exported image, so whoever reads the finished FAQ sees precisely what you meant without a separate caption explaining where to look. Dropping a pin on the exact spot is what turns "go to settings" into something a reader can follow.
Step 4: Write or dictate the answer
Add a comment to the item. On a phone you can type, but dictation is usually faster for a full answer. Chrome and Edge support the browser's built-in speech recognition; Firefox does not, so if you are on Firefox you type instead. Say the answer the way you would tell a coworker: what the pin points at, what to tap, what happens next. The outcome is a written answer attached to the exact screenshot it explains. If you have a second screenshot for the next step, add it as its own item and repeat. For the longer story on this whole use case, see how teams approach FAQ authoring start to finish.
Step 5: Add a free-floating note if the answer needs context
Not every part of an FAQ entry needs a screenshot. If there is a caveat ("this only applies on the paid plan") or a warning ("do not do this while a sync is running"), add an item with no image and just the note. The outcome: the entry reads as a complete answer, with pictures where pictures help and plain text where they do not.
Step 6: Publish and get the link
Tap Publish. You get a short link at /r/<slug> for the full review and a clean read-only page at /s/<slug> for anyone who just needs to read the answer. Cobalt asks for your email so it can send you the link; you can sign in later with Google or an emailed link. Anyone with the link can open it on any device, no app required. If this answer is for a customer or a teammate on a phone, that matters: you can send a review link that opens on a phone with no app.
What you can hand off from the same entry
The published entry is not locked to one format. The read-only /s/ page is the human-friendly version for your support site or a Slack reply. The same review is available as plain markdown at /r/<slug>/markdown, which is what you paste into a doc or hand to a coding agent if the FAQ reveals a bug worth fixing rather than documenting. A signed-in owner can also export to PDF or Word for a knowledge base that expects attachments.
Two limits to know before you lean on this. A review made without signing in is kept for 30 days unless you sign in and save it to an account. After 7 days a review goes read-only for you, the owner: editing, exports, and agent access stop, though the shared link keeps working for everyone you sent it to, comments included, and nothing is deleted. If you are building a library of FAQ entries you will edit over time, Pro at $5 a month keeps every entry editable with no cutoff and reopens read-only ones instantly.
If you want to batch the work, the same phone flow scales: you can capture three FAQ entries in one sitting by adding several screenshots to one review and splitting them into items, or publishing each as its own link. Start the next one the moment the question comes up, before you forget the exact wording of the screen.