Integrations

The Leadiosa plugin is the fastest install path for WordPress sites — and the only one you need for WooCommerce shops:

1. 1Download the plugin from Settings → Installation → WordPress and install it in your WordPress admin (Plugins → Add New → Upload).
2. 2Open the Leadiosa menu in your WordPress admin — a first-run wizard connects the plugin to your workspace. No keys to copy by hand.
3. 3The chat widget appears on your site immediately.

On stores with WooCommerce active, the plugin can also sync your product catalog into the workspace knowledge base — names, prices, descriptions, availability. The AI agent then answers product questions from your real catalog, and re-syncs keep it current as the catalog changes.

The plugin also reports orders back, so Analytics can show the revenue your chat touched: how much of the period’s turnover came from people who talked to you before buying, how many orders that was, and how their average order compares to everyone else’s.

An order is credited when the buyer’s browser carries the same visitor id the chat used, or — failing that — when the billing email matches a contact who had a conversation in the previous 30 days. Orders from people you never spoke to are still recorded, because "revenue the chat touched" only means something next to the total.

Beyond the website widget, your workspace can take conversations straight from Telegram: visitors message your bot, the thread appears in the shared inbox, and everything that works for widget chats — FAQ bot, the AI agent in autopilot or copilot, handoff, tags — works there too. Available on Pro and up.

1. 1Create a bot: open @BotFather in Telegram, send /newbot and follow the prompts.
2. 2In the dashboard, go to Settings → Integrations → Telegram channel and paste the bot token.
3. 3Send your bot a message — it appears in the inbox within seconds, marked with a Telegram badge.

Replies you (or the AI) send from the inbox are delivered back to the visitor in Telegram — text, and file attachments too (photos render inline, other files arrive as documents, captions included). Inbound is text-only: if a visitor sends a photo or a voice message, only its caption reaches the inbox, and a file with no caption does not appear at all. Widget-specific mechanics — typing preview, page context, the offline email transcript — don’t apply to Telegram threads.

Customers write to your WhatsApp Business number and the conversation appears in the shared inbox — with the FAQ bot, the AI agent (autopilot or copilot), handoff and tags working exactly as for widget chats. The connection is bring-your-own Meta app: you create a free app in your own Meta account, so no approval from us is involved. Available on Pro Plus.

1. 1In Meta for Developers, create a Business-type app and add the WhatsApp product. Meta gives every app a free test number you can use before connecting a real one.
2. 2Copy four values: the Phone number ID and WhatsApp Business Account ID (WhatsApp → API Setup), a permanent access token (system-user token with the whatsapp_business_messaging permission), and the App secret (App settings → Basic).
3. 3Paste them under Settings → Integrations → WhatsApp — Leadiosa validates them with Meta and returns a Callback URL and Verify token.
4. 4In the Meta App under WhatsApp → Configuration, set that Callback URL and Verify token and subscribe to the “messages” field. Send your number a message — it appears in the inbox within seconds.

Replies you (or the AI) send from the inbox are delivered back to the customer in WhatsApp. Text travels both ways. Inbound photos and documents are imported into the thread when the file type is one the inbox accepts (images, PDF, text, CSV, Office documents, ZIP) and stays under 25 MB; voice notes, videos, stickers and anything else leave a note in the thread instead, with the caption kept. Outbound: JPEG and PNG arrive as inline photos, every other file as a document.

Customers email your workspace address (or your own support@ forwarded to it) and the mail appears in the shared inbox — with the FAQ bot, the AI agent, handoff and tags working exactly as for widget chats. Available on Pro.

1. 1Enable the channel under Settings → Integrations → Email inbox — Leadiosa mints your inbox address (ws-your-workspace@leadiosa.com).
2. 2Give customers that address directly, or set up forwarding from your existing support mailbox to it — every provider (Gmail, Outlook, your host) has a forwarding setting.
3. 3Send a test email to the address — it appears in the inbox within seconds, as a conversation from that sender.

Replies you (or the AI) send from the inbox are delivered to the customer’s mailbox as a normal email reply, properly threaded under the original message. Text and attachments travel in both directions. Inbound mail keeps up to 5 attachments of 10 MB each (whole messages above 20 MB are refused), skips images embedded in the message body such as signature logos, and trims very long bodies; a file whose type the inbox doesn’t accept is skipped while the text still arrives.

The Telegram integration sends notifications to a group (or a direct chat with your bot) the moment something happens: a new conversation, an offline lead, a rating, a resolved thread. Each message carries a button that opens the conversation in the Leadiosa inbox. It is one-way: you read in Telegram, you reply from the inbox.

1. 1In Telegram, message @BotFather, send /newbot, and copy the token it gives you.
2. 2Paste the token under Settings → Integrations → Telegram.
3. 3Add your new bot to the group where notifications should land (or open a direct chat with it and press Start), and send any message there.
4. 4Click Find my chat — Leadiosa lists the chats your bot can see; pick yours. No hunting for numeric chat IDs.
5. 5Pick which events to forward, send a test message, save.

Personal data in notifications is scrubbed by default — see the note on third-party sharing in Webhooks → PII in payloads; the same switch applies here.

Register a delivery URL under Settings → Webhooks (Pro Plus). A signing secret is generated for you — copy it from the endpoint card. Verify the X-Signature-256 header on every delivery:

See Webhooks for the event catalogue, payload format, verification code in Node.js and Python, and retry behaviour.

The Rocket.Chat integration sends notifications from Leadiosa into a channel of your choice — useful when your team already lives in Rocket.Chat and shouldn't have to watch a second inbox. It is one-way: you read in Rocket.Chat, you reply from the Leadiosa inbox.

• Configure under Settings → Integrations → Rocket.Chat — paste an incoming-webhook URL from your Rocket.Chat server (or API URL + auth token), pick a target channel.
• Choose which events to forward: new conversation, offline message, conversation rated, conversation resolved.
• Notifications carry the event type, the conversation reference, and an excerpt of the visitor message.