Describe what your bot should do

Give BOTS SI a concrete job

Explain who will use the bot, what they need to do, what information it uses, and what success looks like. Mention private records and owner-only actions. Describe behavior when information, permission, or a service is unavailable.

• Audience: customers asking about a small shop’s opening hours and returns.
• Actions: answer from saved policies, collect a support enquiry, and show its reference.
• Permissions: customers see their own enquiries; only the owner changes policies.
• Failure behavior: admit when an answer is missing and offer a human contact.
• Acceptance example: one customer cannot retrieve another customer’s enquiry.

Start with a recipe or template

Recipes and templates fill the description with a starting idea. Read it and replace assumptions with your requirements. A template is a build request; integrations still need connection and normal billing applies.

1. Choose a recipe that matches the selected platform.
2. Remove unnecessary features and supply your own public business facts.
3. Add two or three realistic examples of what people will ask.
4. State which actions need approval, then submit the request.

Improve one journey at a time

Use project chat for follow-ups. “Add a cancel button to booking confirmation and keep existing appointments” gives a concrete goal. For a bug, include steps, the result, and what you expected. Ask for a diagnosis when you are unsure what needs changing.