What a Service Does Besides Text
What follows is a set of capabilities that do not come down to a conversation. Transcribing recordings, talking out loud, voiceover, video, code, and search with a written report.
This part has one purpose: so that you know these things are possible. What a person does not know exists, they do not look for.
Why there are no step-by-step instructions here
Buttons move, mode names change, plans are revised several times a year. A chapter describing menus would be out of date before the book left the printer.
So each chapter says the short version: what the service does, where it helps, where it falls down, and which rules hold regardless of the version.
Who will explain the details
The chat itself will. Describe the task in your own words and ask for it broken into steps: which services fit, what to prepare, where to start, what to watch out for.
A conversation like that also shows what your service can do. Ask outright: "what can you do with audio," "can you take a video recording," "what file formats do you read."
Answers about capabilities are easy to verify: you try it, and it either works or it does not. A mistake here is cheaper than a mistake in the facts of a report.
Some tasks cannot be solved in a chat directly. They require generating a piece of code or building a small application of your own. That is the next stage of working with AI.