Saving your own setup to reuse

There is no long form to fill in. Describe the set-up in a chat, the way you would explain the job to a new employee.

A playbook can set up the complete journey for one business, or provide a reusable starting point for several clients. Each install has its own setup.

Ask for the result you want

For example:

Create a playbook for new roofing customers. Text new enquiries right away, email them the next day, and let me know when someone replies. Reply within one hour, never quote a price by text, and always confirm the address before booking.

Cook asks about anything important that is unclear. Then it saves the new playbook to your Playbooks page.

Tell it these four things

1. What starts the work

Say when it should begin: when a lead arrives, an appointment is booked, or a job is completed.

2. What happens next

List the steps and timing. For example: text now, email tomorrow, then remind them after three days if they have not booked.

3. What changes from one business to the next

Name the details that are never the same twice: the business name, the booking link, the area covered, the number messages go out from, and where you want to be pinged. Cook turns each of those into a question it asks at install time.

4. Your rules and limits

State what must always happen and what must never happen. For example:

• Reply within one hour.
• Do not send texts before 8am or after 9pm.
• Do not ask for a review until the customer says they are happy.

Read it before you use it

Ask Cook to explain what it built. You can request changes in plain language:

• “Make the second message shorter.”
• “Send the reminder two days before the appointment.”
• “Tell me when someone replies.”

Install it once, then press Test on every routine. A test sends nothing to a real person.

Changing it later

Ask Cook for the change. The playbook gets a new version. Anywhere already running the older version keeps its saved routines until you ask Cook to update that install. Cook prepares and tests drafts, preserves independent customizations and flags conflicting edits before activation.