Your support inbox has the same three questions every week. Where do I change my billing email? Why is my export empty? How do I invite a teammate? You keep answering them by hand because writing the FAQ entry feels like a separate project: screenshots to grab, files to name, a doc to format. It is not. You can capture all three in one screen-share session and publish them to a link before your coffee gets cold.
Here is the actual run, start to finish, using Cobalt Capture in a browser tab. No install, no extension, no signup to get going.
The setup: one tab, one recording session
Open the app and click Start a new review. The browser asks which window or screen to share. Pick the tab with your product logged in as a normal user account, not an admin view, so the screenshots match what customers actually see.
You are not recording video. Each time you click Capture screen, the current frame is drawn to a canvas as a still. That is the whole trick to doing three entries fast: you walk to the screen for entry one, capture, comment, then walk to the screen for entry two without ever leaving the tab or opening a second tool.
Entry one: "Where do I change my billing email?"
Go to your account settings page. Capture the screen. The full frame includes the sidebar, the header, and a lot of noise. Drag a rectangle around just the Billing section, cropping down to the field labeled Billing email and the Save button beside it. That crop is the only image edit you make; there is no drawing arrows or boxes on the still, and a cropped still beats an annotated live page because it stays readable when the layout changes next month.
Now add the answer. Click into the comment and dictate it with the browser's speech recognition (works in Chrome and Edge). You say:
Go to Settings, then Billing. Change the Billing email field and click Save. The change takes effect on your next invoice, not the current one.
Dictation is faster than typing because you already know the answer cold. If you are on Firefox, you type instead. Either way, if you want to point at the exact field, drop a numbered pin on the Billing email input so the reader's eye lands there first.
Entry two: "Why is my export empty?"
This one has two states worth showing. Capture the export dialog with the date range set to a period that has no data, crop to the dialog, and dictate:
An empty export almost always means the date range has no records in it. Widen the range here, then re-run the export.
Then change the date range so records appear, capture again, and crop to the same dialog showing rows in the preview. Now you have a before and after in two items. Add numbered pins so the reader reads them in order: pin one on the empty range, pin two on the filled one. Numbered pins that enforce reading order keep a two-step answer from being read backwards.
Entry three: "How do I invite a teammate?"
Some answers do not need a screenshot at all. If your invite flow is a single obvious button, a free-floating comment (an item with no image) is enough. But an invite that hides behind a Members tab deserves one crop of that tab with the Invite button visible. Capture, crop to the Members panel, and dictate:
Open the Members tab and click Invite. Enter their work email and pick a role. They get an email link that expires in 48 hours.
That is three entries, six or seven captured stills, and roughly ten minutes of talking. You never opened a screenshot editor, a doc, or a file manager.
What you publish, and who reads it
Click Publish. The review saves to a short public URL like /r/<slug>. Anyone with that link reads all three entries in order, screenshots and answers together. No login required to view.
The same content is available three other ways, which is why one capture session covers every reader you have. You can export a PDF or a Word document to paste into a help center or hand to a manager who wants entries in a template. The plain-text version at /r/<slug>/markdown is what a coding agent reads if a developer is wiring these into a real help widget. One recording, four outputs.
People who open the link can post a comment on any single entry ("the Members tab is called Team on our plan"), and you can mark each comment resolved as you fix the wording. There is also an owner-facing analytics page showing how many people visited and roughly where from, so you can see which entries actually get read.
The full method, including how to structure answers so they hold up over time, is laid out on the FAQ authoring use case, and there is a step-by-step companion on how to write an FAQ entry with screenshots. If you are documenting a longer process rather than a single answer, the same tab handles quick documentation the same way.
Next time those three questions land in your inbox, do not type the answers a fourth time. Open a tab, capture the screens, talk through them, and send one link.