Guides

Guides are complete walkthroughs: start at the top, finish with something that works. They differ from the documentation in shape rather than quality — documentation answers a question, a guide builds a thing.

Written and ready#

Nothing yet. This section is deliberately empty rather than padded, and the first guides are being written against real customer builds rather than invented ones.

Planned#

The order reflects what people are actually asking for.

1. Capture leads from your website in an afternoon. The seeded lead ability, the fields that matter, and getting the result into your inbox.
2. Run a WhatsApp competition. Entry keyword, qualifying questions, and handling a spike in traffic without falling over.
3. Book a call from the chat. Form, calendar API, confirmation, and what to do when the API is down.
4. Sync leads into ClickUp. Field mapping, and how to tell whether it actually worked.
5. Answer product questions from your catalogue. Getting a product list into the knowledge base in a shape the bot can use.
6. Hand off to WhatsApp with context. Two qualifying questions and a redirect that carries the visitor's question with them.

Meanwhile#

The documentation covers all of the components these guides assemble:

• What an ability is
• Forms and interactive input
• The node reference
• Web controls