AddMyBot Support Team
For a business’s answers or consented contact request, contact that business directly through its published details.
The operator must provide platform support contact details before public availability. This development installation has no configured support mailbox. Never share passwords, verification codes or API keys.
Owners can inspect readiness/usage, manage knowledge and approvals, revoke API keys and disable website access in their workspace.
Get your workspace ready
- Knowledge: add content you may use, review extracted text and index the current revision.
- Playground: test a known question and check the cited source. Avoid sensitive data. New chat starts independent context.
- Business settings: preview greeting, accent and launcher position locally before saving.
- Website: approve current sources and exact origins. Enable publication only when ready; copying the snippet alone does not enable it.
- API access: keep keys on a trusted server. Use the same request UUID and unchanged message for an uncertain retry.
Billing recovery
Use Billing → Refresh payment status after a closed checkout, failed renewal or uncertain confirmation. Resume the existing Test checkout when offered. Wait for verification before another change; never open a replacement subscription to bypass a pending operation. Preserve the payment/subscription reference for operator assistance, but never send API secrets, card details or OTPs. Receipts are owner-only and are not GST tax invoices. Merchant identity, tax treatment, refund policy and a working support contact remain owner prerequisites before live sales.
When an answer is unavailable
Review readiness and allowance in Overview and current indexing in Knowledge. Citation and consent checks still apply. Don’t publish confidential sources or repeat uncertain requests with new IDs.