One business line. Every customer channel.
Customers start where they are — your website, WhatsApp, Instagram, Messenger, Telegram, LINE, or Shopify. OrcaLinq keeps the conversation coherent across all of them.
Pick a channel to read the full setup, tradeoffs, and AI behaviour.
-
Website chat widget
2.4 KB loader. Lazy-loaded UI. CSP-safe. Live, beta, planned status visible per page.
-
WhatsApp Cloud API
Bring your WABA. Templates, media, signed inbound, AI-first answering with handoff. The highest-demand channel for support.
-
Instagram & Messenger
One Meta app for both. Page tokens, IG business ID, HMAC-verified deliveries. 24-hour windows respected.
-
Telegram
Bot API with webhook or long-poll. Inline keyboards, file handovers, agent endpoint, command routing.
-
LINE
Official Account with rich messages, push and reply tokens, LIFF handoff, channel-secret verified.
-
Shopify
Order, cart-abandoned, customer-created event webhooks. HMAC-SHA256 verified. Pre-sale and post-sale support across web and messaging.
Every channel has constraints. We document them.
A semantic PBX cannot break platform rules. Each channel page lists what's possible, what's restricted, and how the platform handles each constraint.
- WhatsApp templates. Outbound outside the 24-hour window requires approved templates. The platform integrates with template approval and respects pricing categories.
- Instagram windows. 24-hour and 7-day messaging windows are enforced. The routing layer surfaces window state to the agent.
- LINE quotas. Free-tier message quotas are tracked. Routing avoids exceeding paid thresholds without explicit permission.
- Webhook validity. Provider signatures are verified before processing. Misconfigured webhooks are surfaced on the Podium.
Frequently asked questions
Are all channels live?
Web chat, WhatsApp Cloud API, Telegram, LINE, Meta Messenger and Instagram, and Shopify webhooks are live. Email, voice, and additional integrations are on the roadmap with explicit live/beta/planned status on each channel page.
Can the same conversation move across channels?
Yes. Identity is matched where possible (phone number, email, customer ID), and the Wake transcript carries forward so a conversation that started on the website can continue on WhatsApp without losing context.
Are channels BYOK?
Yes. Every messaging channel is BYOK by design. You bring the credentials; the platform never holds the carrier relationship.
Which channel should I start with?
Most teams start with web chat plus WhatsApp Cloud API. Web captures intent on the site; WhatsApp continues the conversation when the visitor leaves the site.
Keep exploring
Connect a channel during the demo.
Bring a sandbox WhatsApp number, Telegram bot, or LINE channel. We'll wire it live so you see end-to-end routing on your own keys.