Ep 04 · Level 1 · The map
The keys
Same refund question, two keys, the right answer. Don't hand AI a master key: cut a key for each door it needs, and nothing more.
Last episode, a customer asked for a refund ten days after buying, and AI answered with the general rule: most shops allow fourteen days. Wrong for a business whose policy is seven days, with no refunds on sale items.
Same customer, same question, same brain. This time it gets two keys, and the right answer.
Key 1: your refund policy, one folder
Not your whole Google Drive. One folder, called Policies, with the refund policy, the warranty and the delivery terms in it. The AI reads what's in that folder and nothing else.
Key 2: your billing system, read only, one customer
Only this customer's orders, and only to read. It can see what they bought and when. It can't change a thing.
That matters. If it can only read, the worst it can do is give a wrong answer. If it can write, it can send, change or delete.
Same brain, right answer
Ask again, and it answers from your policy and the order itself: bought ten days ago, a sale item, not eligible for a refund. Here's a polite reply.
No master keys
That's the trick: don't hand over a master key. Cut a key for each door it needs.
- One folder, not the whole Drive.
- Read, not write.
- This customer, not every customer.
What a master key would open
Your cash flow Excel, sitting in the same Drive. Your whole customer list, every name and number. Your ordering system, where one write key can place an order you're not ready for. None of that is needed to answer one refund.
Try it
Pick one task you'd like AI to help with, like answering refund questions. Write down the exact folder, system and records it needs to read. Anything else it can reach today is a key you can take back.
Share your answer with OC in the comments@onecrew.aiSmall, well-cut keys are how AI gets useful in your business without putting it at risk.
Read the transcript
Same customer. Same refund question. Same brain. Last time, AI got it wrong. This time, we give it two keys. Let's go.
No keys? "Sure, most shops allow fourteen days." Wrong for you.
Key one: your refund policy. But not your whole Google Drive. One folder, called Policies. It reads what's in that folder, and nothing else.
Key two: your billing system. Read only. And only this customer's orders. It can see what they bought, and when. It can't change a thing. Because if it can only read, the worst it can do is give a wrong answer. If it can write, it can send, change, or delete.
Now ask again. "Bought ten days ago. Sale item. Not eligible for a refund. Here's a polite reply." Same brain. Right answer.
That's the trick. Don't hand over a master key. Cut a key for each door it needs. One folder, not the whole Drive. Read, not write. This customer, not every customer.
Now look what else a master key opens. Your cash flow Excel, sitting in the same Drive. Your whole customer list, every name and number. Your ordering system, where one write key can place an order you're not ready for. None of that is needed to answer one refund.
So before you plug anything in, ask: what does it need for this job? Give it that. Nothing more.
Next, we put it all together: size up any AI in ten seconds. I'm OC. Follow so you don't miss it.