Know what connects, what it costs, and what happens next.

Each workspace connects its own WhatsApp instance during onboarding. The connection, webhook, and message events are scoped to that workspace before automation is enabled.

The inbound adapter is designed to process new direct customer messages and reject group events. Loop and duplicate protections are part of the delivery path.

Yes. Media is downloaded through the messaging adapter, normalized, and passed to the AI workflow as voice transcription or multimodal image input.

Each workspace defines approved knowledge, response language, allowed actions, and handoff conditions. The workflow can answer, act, ask for clarification, or stop for a person instead of improvising an unsupported outcome.

Yes. OrangeBee keeps the customer journey separate from the model provider so a different approved model can be introduced without rebuilding WhatsApp, payments, or the team dashboard.

The workflow can pause automation and assign a conversation to a team member. The handoff should include the conversation, captured intent, and relevant action state.

WhatsApp is the currently proven starting channel. Website chatbot, BotCall voice workflows, Slack alerts, CRM updates, calendars, and other connections can be added through a scoped rollout.

It can answer from approved business knowledge, capture and qualify a lead, recommend the next step, and move the conversation to WhatsApp or a human team member.

OrangeBee can route approved events such as a qualified lead, failed payment, urgent support request, or human handoff to the right Slack channel with enough context for the team to act.

BotCall is a scoped voice-agent workflow for inbound enquiries or approved outbound follow-ups. Provider, consent, language, call objective, and human-transfer rules are agreed before launch.

No. ₹1 is useful for testing, but order creation accepts the requested amount and generates a unique transaction reference for every attempt.

The tested flow sends the QR as WhatsApp media because the payment link is not reliable in every customer environment. The QR stays visible and scannable inside the conversation.

Only after the gateway reports a successful order state. The confirmation can include the amount, order ID, and UTR and is returned to the customer who created that order.

The currently proven QR workflow uses Vyapar Gateway. Razorpay, Paytm, PayPal, and other providers can be evaluated through OrangeBee's bring-your-own-gateway path. A provider is called live only after order creation, verification, failure, and retry cases pass testing.

That depends on the connected provider and account. OrangeBee can present UPI QR inside WhatsApp and connect cards, wallets, net banking, PayPal, or other approved checkout methods when the provider supports them.

Workspaces are the tenant boundary. Membership, WhatsApp connections, conversations, knowledge, payment records, and settings reference the owning workspace.

No. Customers work in the OrangeBee dashboard to manage their workspace, AI settings, conversations, payments, knowledge, and team access. Internal platform tooling is not part of their daily workflow.

The stack is Dockerized and PostgreSQL-based. Private or infrastructure-specific deployment is handled as a Scale engagement because networking, secrets, backups, and operations must be designed together.

Provider keys belong in server-side environment or secret management. They should never be embedded in browser code, public URLs, screenshots, or tracked environment files.

Inbound events use message identity and processing state so retries do not create duplicate work. Bot-loop protection and outbound-message filtering add another safety layer.

Test direct and group messages, duplicate delivery, media, slow AI responses, human handoff, payment pending/success/timeout, provider outage, and tenant isolation.

Launch is $20 per month for one focused WhatsApp AI workflow. Performance is 2% of sales OrangeBee can identify and verify under the agreed attribution rules. Custom is for website chatbot, BotCall, multiple channels, or tailored integrations.

A sale must be tied to an OrangeBee conversation and confirmed by the agreed order or payment source. Attribution window, refunds, taxes, cancellations, and reporting are documented before the plan starts.

No unless your proposal explicitly says otherwise. WhatsApp, model, voice, storage, payment-gateway, and other provider charges may be billed separately from OrangeBee pricing.

Yes. A good pilot is narrow but real: one customer journey, real business knowledge, one or two actions, defined handoff rules, and measurable acceptance cases.