Frequently Asked Questions (FAQ)
Direct answers to common questions regarding architecture, Meta compliance, and billing.
Overview
Answers to frequently asked questions regarding platform architecture, channel connectivity, data privacy, and operational usage.
Channels & Integrations
Yes. Pro and Enterprise workspaces support multiple connected numbers. Each number can operate with distinct agent personas or route to dedicated department queues.
No. Meta's official WhatsApp Business Cloud API strictly restricts API phone numbers to direct 1-to-1 customer interactions to prevent group spam. Automated participation in user groups is not permitted by Meta's Terms of Service.
Whenever a customer sends an inbound message to your business, Meta opens a 24-hour window where you can send free-form text and media responses. Once 24 hours elapse with no customer reply, you must use a pre-approved Message Template to contact them.
Privacy & Model Grounding
No. Orbion enforces strict zero-retention data agreements with model providers. Your customer chats, uploaded PDF documents, and proprietary business knowledge are never used to train foundation models.
Orbion uses Retrieval-Augmented Generation (RAG). Inbound customer questions are embedded as dense vectors, matching relevant chunks in your uploaded documents. If the similarity score falls below threshold, the agent explicitly admits it does not know or triggers human handover.
Billing & Credits
AI Credits cover LLM inference tokens (GPT, Claude, Gemini). Meta WhatsApp Conversation Charges (WCC) cover Meta's official per-conversation rates billed directly for 24-hour service or marketing windows.
Yes. In /user/admin/billing, configure your Legal Business Name and 15-digit GSTIN under Billing Profile. Completed charges in the Payment History table can be downloaded as PDF receipts for your accounting records.