Cook.ai
Documentation Browse

Start here

Prompting basics

How to phrase a job in plain English, where the answer comes back, and what to do when it is wrong.

You use Cook by asking for things in the chat box, in ordinary sentences. There are no commands to learn and no menus you have to find first.

Ask for the result, not the steps

Say what you want to end up with. Cook works out which department does it and what order the steps go in.

Good:

Get me more driveway jobs in the Tampa area. I charge $250 and I can do three a day.

Also good:

My busy season ends in August and I go quiet. What should I be selling in September?

You do not need to say “build a funnel” or “run a campaign”. If you do not know the word for what you want, describe the outcome and Cook will name it back to you.

Type the job here, in your own words. No commands, no menu to find first.
Type the job here, in your own words. No commands, no menu to find first.

Give it the things only you know

Cook can find out what your competitors charge. It cannot find out what you charge, how far you will drive, or which jobs you refuse. Say those out loud the first time they matter:

  • what you sell and what it costs;
  • the area you cover;
  • the jobs you do not want;
  • anything that must never be said in your name.

It keeps what you tell it and uses it next time. You will not have to repeat it every day.

One job at a time

A single request with one clear outcome works better than a list of five. If you have five, send the first, look at what comes back, then send the next.

Where answers come back

  • In the chat, for anything short.
  • As a file in your Library, for long research, so the chat does not fill up with pages of text.
  • As an approval request, for anything that spends money or reaches a customer.
  • In Slack or Discord, if you connect one. Cook then works in the channels your team already uses — see Slack and Discord.

When it gets something wrong

Correct it in the same conversation, the way you would correct a person:

Too formal. My customers are homeowners, not property managers.

The price is wrong — it’s $250, not $180.

Never say “affordable”. Say “no call-out fee”.

A correction sticks. It applies to the next piece of work too, not just the one in front of you. You will not have to say it twice.

Asking it to keep doing something

If a job needs to happen every time something occurs — every new enquiry, every Monday morning — say so, and Cook saves it as a routine that runs on its own. See the Answering people without doing it yourself.

If you want the same set-up repeated for a second and third business, that is a playbook. See Build a playbook for your systems.

How to approve work — the limits on what Cook can do while you are not watching.