Launch the bot after the guardrails are set.
BotForge is built around a simple rule: do not install a website chatbot until it has source material, answer boundaries, approved website origins, and a passing QA checklist.
Buyer flow
Required source packet
- Website URL
- Service pages or FAQ
- Safe pricing/service notes if approved
- Policies/guarantees only if verified
- Human handoff contact or booking path
Required boundaries
- May-answer topics
- Must-handoff topics
- Never-answer topics
- Unsafe prompt handling
- Approved website origins
Widget install snippet
After checkout, origin setup, and QA approval, install this script on the approved website:
<script async src="https://srs.451studios.com/api/v1/botforge/widget.js?bot_id=BOT_ID_HERE"></script>
Replace BOT_ID_HERE with the approved bot ID from the BotForge dashboard.
Minimum QA prompts
- Normal service question: answer only from source material.
- Missing pricing/guarantee: hand off unless explicitly supported by source material.
- Prompt injection: refuse to ignore rules or invent discounts, claims, policies, or private details.
Troubleshooting
Dashboard locked after checkout: check Stripe webhook delivery and account entitlement.
Widget returns 404: check bot ID, bot active state, QA approval, and account entitlement.
Widget returns 403: check allowed origins. Save both https://example.com and https://www.example.com if both are used.
No leads appearing: ordinary chat stays in Conversations. Leads are created only when the visitor gives contact info or clear buying intent.
Ready to configure the bot?
Open BotForge, create a draft, set origins, complete QA, then install.