Notes
A good AI setup should come with an off switch
Most people set up an AI assistant by asking what it can do. The better first question is what it is allowed to do, and how you make it stop.
That is not fear of the technology. It is the same thing you would settle with any new helper: which keys they get, what they can sign for, and what they should call you about first.
This note is a simple way to write that down before anything is connected.
Think in steps, not on or off
“Should I let AI run this?” is too big a question. It is easier to give each job a level on a short ladder:
- Look only. The assistant may read what you share with it and answer questions. It changes nothing.
- Draft. It may prepare a reply, a list, a price check, or a post, and leave it for you. Nothing goes out.
- Act after you approve. It may do the thing, but only after you have seen the exact version and said yes.
- Act on its own. It may do the thing without asking, inside limits you wrote down.
Every job starts at the bottom. A job moves up one step only after it has done the lower step well for a while, and you could explain to someone else why you trust it.
What should almost always ask first
Some actions are hard to take back. For most small businesses, these belong at “act after you approve” or lower, no matter how good the tool seems:
- Sending a message or email to a customer, vendor, or anyone outside the business.
- Publishing anything: a post, a review reply, a change to your website.
- Changing a price, a booking, or an order.
- Spending money, issuing a refund, or touching a payment account.
- Deleting files, records, or accounts.
Things that are easy to undo, or only seen by you, can usually move up sooner: sorting your own notes, summarizing a report, tidying a draft, reminding you of something.
The off switch is a real thing, not a feeling
“I can always turn it off” only counts if you know exactly how. Before you connect anything, be able to answer these:
- Where do I pause it? Know the setting, button, or schedule that stops it from running.
- How do I take away its access? Know where to disconnect it from your email, calendar, files, or website, and check that it really lost access afterward.
- What can it reach while it is paused? Ideally nothing.
- Who else can turn it on again?
If you cannot answer those in a minute, the setup is not finished yet.
Give it its own keys
The cleanest off switch is separate access. Where you can, give the assistant its own login, its own inbox, or limited access to one folder, instead of your main account and password.
Then turning it off is simple: remove that one access. Your own accounts keep working, and you never have to change every password you own because a tool had all of them.
It also keeps payment details, private customer records, and anything you would not want repeated out of reach by default. Connect those later, one at a time, only if a job truly needs them.
Keep a short record of what it did
You do not need a dashboard. You need to be able to answer “what did it do yesterday?” in a minute. Many tools keep a history of actions or messages. If yours does not, ask it to keep a plain list of what it sent, changed, or scheduled.
Read it now and then. If something surprises you, move that job back down the ladder. That is the system working, not failing.
A hypothetical example
This is an illustration, not a client story.
Picture a small tour business that gets the same booking questions every day. The owner sets up an assistant at “draft” for customer replies: it writes answers about times, meeting spots, and what to bring, and the owner sends them.
After some weeks the drafts are usually right, so the plain questions move to “act after you approve,” where the assistant sends once the owner taps yes. Anything about refunds, weather cancellations, or changing a booking stays at “draft.” The assistant has its own access to one inbox and the booking calendar in read only mode, and the owner knows where to disconnect both.
Where Grok Bot fits
This is the way we set up assistants, and Grok Bot is usually where we start right now. It works well at the draft and approve steps: reading what you share, preparing replies and summaries, and asking before anything goes out under your name. Other tools come in when they fit a particular job better. The ladder matters more than the brand.
Start lower than you think
A good assistant earns its way up. Start every job at look only or draft, write down what must always ask first, and make sure you can actually stop it before you need to.
The point is not to hold the tool back. It is to make trusting it a decision you made on purpose.