Briefing
Most jobs that go wrong were briefed in one vague line.
“Every invoice more than 30 days overdue gets a polite reminder from my address” works better than “chase invoices”.
Paste a reply you were happy with, or the report you want back. One example says more than a paragraph of description.
“Skip anyone we spoke to this week”, “only the Leeds branch”. Limits let it make the call without stopping to ask.
Hand over ten invoices before you hand over all of them. You can widen it next time.
Watching
When a job uses a website, its browser opens beside the chat. You see each page as it works, and you can take over at any point.
When a site asks for a password or a one-time code, Kaer stops and hands you the browser. You type it, then hand back.
On a new job it looks around before it acts. Give it a moment before you step in.
Approving
Anything with a consequence: the email before it sends, the invoice before it goes out, the click that pays, books or confirms.
Right customer, right amount, right wording. You do not need to check how it got there.
If a draft is off, tell it in the chat (“too formal”, “wrong contact”) and it carries on from there. No need to start again.
Getting unstuck
Most stops are a question in disguise: a missing login, an unclear instruction, two rules that disagree.
If it fails at the same point more than once, something has changed: an expired login, a site that moved a button. Sort that first.
When a job has come back right a few times, make it a workflow that runs every week or whenever something arrives.
Try it on a small job first.
Something you know well, so you can tell straight away whether it got it right.