Claritty

Point at a list of leads, orders, invoices or prices. Ask about all of it, then make it a weekly job. Never reads your typing.

Claritty turns work you do in your browser into jobs your agents carry out for you. This extension is how you hand them over, and how you keep up with what they are doing. POINT AT A LIST AND ASK ABOUT ALL OF IT Hold Alt and point at a list of leads, candidates, orders, jobs, invoices. The rows go with your question, so you can ask about the whole list and get an answer straight back: which of these are worth chasing, which are missing a detail, which changed since last week. It reads the list from YOUR browser, not by going off and fetching the page again. That matters more than it sounds: it means this works on the pages that are behind your login, where most of your real work lives. Your CRM, your store admin, your billing dashboard, the portal your suppliers use. Nothing needs connecting and nothing needs an API. If it is worth doing again, make it weekly in one press. OR SHOW IT HOW For a task worth repeating, record it instead. Press Record, do the task the way you always do it, and press Stop. What you did becomes a job your agents can repeat: the pages, the order, the decisions. You review it in plain language, correct anything that came out wrong by saying so, and then it runs on a schedule, or your agents follow it as a written procedure for the work that needs judgement rather than a clock. OR JUST ASK Open the side panel and describe the job in a sentence. The agents you already have pick it up. FOLLOW IT WITHOUT LEAVING THE PAGE The side panel is the other half of this extension, and it is where a job stops being something you launched and forgot. It shows what each job is doing right now, what it has got to, and which ones are stopped on you. When an agent needs something from you it asks in the panel, and you answer there. When one is about to send, post or file something, it shows you what it wrote, on real data, and waits. You let it go ahead, or you correct it in a sentence and it carries on with what you said. When a job needs an account joined up, it names which one and connects it without moving you off the page. You can also read how the job actually went: what each agent did, in order, in plain language, including the questions they put to each other and the answers that came back. IT SAYS WHAT REALLY HAPPENED A job that prepared something and sent nothing says so, rather than reporting itself finished. A job that did part of what was asked names the part it did not do. A job you closed yourself is not counted as the agents' work. This matters more than it sounds: you cannot hand work over to something that overstates what it did. WHAT IT READS When you point at something: the part of the page you pointed at, and the rows of the list it belongs to, so the answer is about what you were actually looking at. It is read and sent for that question. Claritty is dormant on every page until you hold Alt or press Record. While you are recording: the structure of what you did, not the content you did it with. The label and role of each control you used ("the Submit button", "the Vendor column"), the page titles, the address of each page, the shape of the table you were reading, and screenshots at a few key moments so the task can be understood from what the page actually looked like. WHAT IT DOES NOT READ The values you type while recording. They are masked inside the extension, before anything is sent. Not your passwords, and nothing at all on any page while you are not recording or pointing. The address of each page is kept in full, including anything after the "?", because that address is how the job finds the page again. A list you filtered down to one batch is a different address from the unfiltered one. Anything in that address carrying a token or a password is dropped before it leaves your browser. TALKING WHILE YOU WORK You can narrate. Turn the microphone on and say why you are doing something, such as "skip this one, it is already paid", and that reasoning is kept with the step it belongs to, which is usually the part a recording cannot see. It is off until you turn it on, and off again when you turn it off. Where your voice is transcribed depends on your machine. Claritty asks Chrome to do it on the device first, and where Chrome can, the audio never leaves your computer. Where it cannot, Chrome's own speech service transcribes it and the audio goes to Google. The recorder says which of the two is happening every time the microphone is on, in the recorder itself, while it is on. BEFORE IT CHANGES ANYTHING A job that sends, files or submits pauses first and shows you exactly what it is about to do, on real data, and waits for you to approve it. You see the message before it is sent, not after. A job set to act on its own says so on its own card, so you are never surprised by one. SIGNED-IN SITES If a task needs you signed in, you can hand the job the session you already have by pressing "connect this site" while you are on it. It is a session and not a password: we never ask for, receive or store the password itself, it expires on its own, and signing out of that site revokes it. It is stored encrypted and scoped to one job on one site. Sites with a real integration, such as Gmail, Slack or HubSpot, never use that path. They use the provider's own authorization. You need a Claritty account. Uninstalling the extension stops all capture immediately, and deleting a job deletes the recording behind it. Privacy policy: https://app.claritty.ai/privacy