Chief works in the browser in front of you, signed in as you, in your own accounts. Before it clicks anything it shows you the exact button and waits — and auto-accept is off until you turn it on.
Chief wants to press this button.
The words on it“Send reply”
WhyThe reply is written, and it follows the rules you set.
Say no and Chief stops here.
Chief is a Chrome extension. It works on the page you already have open, signed in as you, in the accounts you already use — the same windows, the same logins, and the same trail in your sent items as if you had done it by hand.
There is no second copy of your inbox living somewhere else, and nothing goes out on your behalf from anywhere but your own account. The trade is honest: if your machine is off, Chief is off with it. The work happens while you are at your desk, and nothing happens anywhere you cannot watch it.
Chief asks twice over: once before it presses anything, and again before it takes you somewhere new. Both questions come with the details rather than a summary of them.
The confirmation shows the exact element, cropped out of the page in front of you, and the words written on it. You are approving that button rather than a description of one. Say no and nothing happens.
When Chief needs another page it names the destination, gives you the full web address, and says what it wants to do when it gets there. Going somewhere is its own question, asked on its own.
The safest way to judge it is to watch it ask.
Get started freeSome of this is how Chief is built and some of it is the instruction it works to. Either way, none of it is a box you could tick by mistake.
Chief is told to fill fields in, never to send, save or submit off its own bat. Anything that commits is a separate ask, and you get asked every time.
Clearing out is not a job Chief is given. It is also one of the four things the auto-accept warning names, because we would rather say it twice than assume you read it.
One conversation at a time, answered in the thread it arrived in. Nothing blasted across a site, and nothing that would make your account look like a machine.
None of this is a setting you have to find. It is how Chief arrives.
Get started freeThree things, none of them long. You can be approving your first reply the same afternoon.
Chief works from a Chrome extension, which comes from the Chrome Web Store. About a minute, and you will see it in the toolbar when it is done.
The same account as the meetings side. One sign-in covers both, so there is nothing new to set up if you already use Chief.
Who you want and who you do not, what to find out before you book anyone in, and a few replies you have sent before. That becomes your standing brief, and every draft is written against it.
Change your mind about the brief later and you tell us rather than hunting for a settings screen — we make the change for you.
Automation is priced by the work it does — see pricing.
Chief learns a site from a short written guide: what its pages are, where the useful parts of them sit, and the handful of jobs worth a shortcut. That is a row of configuration rather than a release, which is why adding one is quick rather than a project.
We do the adding. Tell us where your work lives and we write the guide — there is nothing for you to set up, and nothing to maintain when the site changes. Email needs no guide at all: Chief works in the webmail you already use, whichever one that is.
Because Chief works inside your own accounts, your messages stay in them — the automation side keeps no copy of your inbox. Where your conversations are stored, who can see them, and what is and is not done with them are set out plainly in one place.
Read the security page →Install it, tell Chief how you work, and approve the first reply yourself. Auto-accept will still be off when you get there.