Passwords, one-time codes and card details
You type them, Kaer never sees them.
A lot of the work that matters sits behind a login on a site that was never built to be automated. Kaer opens it in its own browser, does the steps you ask for, and hands control back to you where it should: signing in, paying, confirming.
Start a chat and brief it the way you would a colleague, naming the site: “log in to the supplier portal and download this month's invoices”, or “check whether Friday at 14:00 is free and hold it”.
A live browser opens beside the chat, labelled Errand, with the site's address and a Live badge. You see Kaer's cursor and every step as it happens; the footer reads “Kaer has control”.
When the site asks for a password, a one-time code or card details, Kaer stops and the footer says it is your turn. Click Take over, type the details yourself, then Hand back. Kaer can't see or keep your password.
Before a click that pays, books or confirms, Kaer asks you: Approve, or Check it myself. Nothing is bought or confirmed until you say so.
Kaer reports what it did in the chat. The browser closes when the job is done, or after ten minutes with nothing to do; ask again and it opens a fresh one.
You type them, Kaer never sees them.
Held until you click Approve.
Handed to you, never worked around.
Find what's overdue, draft each reminder in your tone, and approve it before it goes. A step-by-step guide to chasing invoices with Kaer.
Set up Kaer Mail, let it sort the morning's enquiries, approve drafted replies before they send, then choose how much runs automatically.
Attach the spreadsheet, describe the tool, check the live preview and publish it on its own address. A step-by-step guide to building tools with Kaer.
Describe the report once, run it by hand, add an approval step and put it on a schedule. A step-by-step guide to recurring work with Kaer Workflows.