Connect the surface where the customer writes or calls as the correct channel. This page clarifies the difference between channels, commerce data integrations, and webhook workflows.

Overview

In Yanitly, a channel is the surface where a customer conversation arrives. WhatsApp, Instagram DM, Messenger, Telegram, and the web widget belong here. Shopify, Trendyol, or SMM panels are usually data or action integrations.

Messaging channels
WhatsApp, Instagram DM, Messenger, and Telegram conversations flow into the inbox, AI replies, and human handoff.

Web widget
The website widget turns visitor messages into Yanitly conversations and supports identity handoff.

Webhook delivery
External events are processed through signed webhooks or provider callback endpoints.

Channel Types

WhatsApp setup requires Meta Business, WABA, and phone number selection.
Instagram DM and Messenger require Meta Business Suite permissions and a connected professional account.
Telegram requires a BotFather token and webhook URL verification.
The web widget requires correct tenant ID and domain/origin settings.
Commerce or SMM panel connections should be treated as data/action integrations, not customer message channels.

Setup Flow

Choose the correct channel card on the Channels page.
Approve provider permissions or enter the required token values.
Verify webhook URL, verification token, and secret values.
Send a test message through the real customer channel.
Confirm conversation, contact, message, AI reply, and handoff records are created.

Webhook Endpoints

Provider callback endpoints vary by channel. Public URLs should not be shown to customers; use branded, readable redirects when a customer-facing link is needed.

Code example

Meta webhook:
https://api.yanitly.com/v1/webhooks/meta

Telegram channel webhook:
https://api.yanitly.com/v1/public/channel-webhook/<CHANNEL_ID>

Yanitly outbound webhooks:
https://yourapp.com/webhooks/yanitly

Security Checks

Do not disable webhook verification token or signature checks.
Never place provider access tokens or secrets in public docs, ticket notes, or customer messages.
Keep domain/origin restrictions active for web widget and public callback endpoints.
Explain Meta template and payment requirements accurately for business-initiated WhatsApp messages.