BYOK from day one
You bring the WABA, phone number, and credentials. The platform never holds the carrier relationship. If you leave, your number stays yours.
Bring your WhatsApp Business Account. OrcaLinq answers routine messages with AI, hands off valuable conversations to your team, and respects every template, window, and pricing rule Meta enforces.
For most non-US teams, WhatsApp is the primary inbound channel for customer questions, support, and pre-sale. OrcaLinq treats it as a first-class semantic PBX channel — not an afterthought next to web chat.
You bring the WABA, phone number, and credentials. The platform never holds the carrier relationship. If you leave, your number stays yours.
Routine questions get an answer in seconds. Sonar reads intent, knowledge cites the source, confidence threshold protects against guessing.
When the conversation needs a person, the platform pages the right agent on the endpoint they already use — even if that's not WhatsApp.
Outbound outside the 24-hour window goes through approved templates. The platform tracks approval state and category-based pricing.
These constraints are platform-level. The semantic PBX layer respects them and surfaces them clearly.
Once a number is on Cloud API, the WhatsApp Business mobile app for that number is deactivated. Plan migration timing.
Free-form replies are allowed within 24 hours of the customer's last message. Outside the window, an approved template is required.
Marketing, utility, and authentication templates have different pricing on Meta. The platform exposes the active category per template.
Quality rating, throughput, and country-level rules are enforced by Meta. The platform surfaces health metrics on the Podium.
Yes. WhatsApp Cloud API requires a WABA on Meta. The platform is BYOK — you own the WABA and the phone number. The platform connects via your app credentials.
Usually no. Once a number is migrated to WhatsApp Cloud API, the WhatsApp Business app for that number is deactivated. Plan the migration when you're ready to commit.
Inbound messages are signed and verified. The Sonar intent engine reads the message; if confidence is high and policy allows, AI replies. If not, the conversation is paged to the right human on their preferred endpoint.
Outbound messages outside the 24-hour customer service window require approved templates. The platform tracks template categories, approval state, and pricing tier.
Yes. Inbound media is downloaded to tenant-scoped storage; outbound media is uploaded to WhatsApp via your credentials. Image, document, audio, and video are supported subject to platform rules.
Agents pick the endpoint they prefer. A WhatsApp customer can be answered by an agent on Telegram, the PWA, or a custom endpoint. The reply lands on WhatsApp regardless.
Bring a sandbox WABA or a real number you're ready to migrate. We'll wire BYOK live during the demo.