A practical map of AI SNS CHAT integrations: channels, knowledge connectors, actions, handoff alerts and the REST API, with setup order and plan limits.
Most support teams do not struggle with the AI itself. They struggle with the wiring: which channels to connect, where the answers come from, and how a human gets pulled in when the bot should step aside. This overview sorts AI SNS CHAT's integrations into five groups and suggests an order for setting them up, so you can go live on a website chat or WhatsApp first and grow from there.
The five kinds of integration
It helps to stop thinking of "integrations" as one long list. In AI SNS CHAT they fall into five jobs:
- Channels are where customers talk to your agent: website chat, WhatsApp, Messenger and many more.
- Knowledge sources are where the agent learns your answers: files, websites, wikis, drive folders.
- Actions and lookup tools let the agent do something: collect a lead, check an order, book a slot.
- Handoff and alerts bring in a person, and tell your team where to look.
- API, webhooks and domains let your own systems talk to the agent, under your own brand.
Each group has its own menu location and, in a few cases, its own plan gate. Knowing which group a request belongs to saves a lot of searching.
Channels: meet customers where they already are
The Channels page in the sidebar is the deploy list. It covers the everyday options for international teams, including the chat widget, Help page, Email, WhatsApp, Messenger, Instagram, Telegram, Slack, Microsoft Teams, Discord and Shopify. It also includes regional messengers that matter in Asia-Pacific, such as LINE, LINE WORKS, Chatwork, KakaoTalk, WeChat, Zalo, Lark/Feishu and DingTalk. Help desk platforms (Zendesk, Intercom, Front, Crisp, Chatwoot) and developer routes (API, Zapier, WordPress) sit on the same list.
A few practical details are worth knowing before you start:
- Shareable link. You can send customers a link to the agent, optionally protected by a password or per-user sign-in, or restricted to your office network. This is handy for internal assistants.
- Mobile. Swift (iOS) and Kotlin (Android) snippets are available for in-app chat.
- Webhook security. Incoming webhooks from LINE, Meta, Twilio and Discord are signature-checked. For Telegram, Viber and Discord, the webhook is registered for you automatically.
- Phone and voice. Inbound AI phone calls use a Twilio number connected per agent. Outbound batch calling also needs a Twilio number.
Two channels with extra conditions
Google reviews: the agent drafts replies to reviews, but this depends on Google API approval. Without it, Google returns a 403 error.
Instagram: beyond normal conversations, you can set up auto-DM automations with six trigger types.
Where conversations land
A common surprise: the Inbox is email-only. Conversations from every other channel, including website chat, WhatsApp and Messenger, live under Activity → Chat logs.
Both views let a person take over a chat (the bot pauses), translate live, reuse saved replies and edit a reply into the ideal answer so the agent learns from it. Chat logs add filters, export and thumbs up/down ratings.
Knowledge: connect the documents you already have
An agent is only as good as its sources. There are two places to look.
Sidebar → Data sources holds the basics: Files, Text snippets, Website, Q&A, Notion, Social, Tickets and Suggestions.
Connectors under Channels pull from the tools where documentation already lives:
- Wikis and help centers: Confluence, GitBook, ReadMe, Guru, Zendesk Guide, esa.io, DocBase, Qiita Team
- File storage: Google Drive, OneDrive, Dropbox, Box, SharePoint
- Notes: Notion (re-read on demand) and an Obsidian vault through Git
Wiki-style connectors read up to 1.5 million characters and 400 pages per sync. If a space is bigger than that, AI SNS CHAT tells you it was truncated rather than silently dropping content, so split large spaces or connect the most relevant sections first.
Web search is narrower than you might expect
Answering from the live web when the knowledge base has no answer is available only on LINE WORKS (Behaviour → Web search). It defaults to Microsoft and Apple support sites, skips in-house topics and cites the page it used. For any other agent, the Tavily action gives real-time web search.
Actions and lookup tools: let the agent do things
Actions are the part of an agent that reaches into other systems. The built-in set includes Escalations, Custom actions, Collect leads, Custom form, Suggested messages, Custom button, Stripe, Shopify, Slack, Cal, Calendly and Tavily.
On top of that is a catalogue of roughly 50 read-only lookup tools. Examples include Freshdesk, Help Scout, Jira Service Management, Gorgias, HubSpot, Pipedrive, Airtable, Google Sheets, Google Calendar, WooCommerce, ServiceNow, Trello, Asana, Zoho CRM, KING OF TIME, SmartHR, Garoon and Klaviyo. Read-only means the agent can look up a ticket status or an order, not change it.
Dedicated connectors exist for Zendesk, Salesforce, Zoho Desk and Intercom, and kintone supports read and write, which is useful for Japan-based teams. A Gmail Chrome extension is also available.
Lead capture deserves a mention because it is where integrations pay off fast. The Collect leads action and custom forms save leads to Activity → Leads, and every lead also creates a contact. Custom attributes on contacts include a description that tells the agent when to ask for that field.
Handoff and alerts: connect your people
Integrations are not only about software. When the agent hands off, three things must happen: the right person is chosen, they are notified where they actually look, and the customer is told what comes next.
- Who: under Helpdesk → Scheduling you set shifts per person and timezone, and handoffs are auto-assigned to whoever is on shift.
- Where they are told: handoff alerts can go to Slack, Teams, LINE WORKS, WhatsApp, email or a webhook.
- What the customer sees: the server reads the rota and adds the "what happens next" line itself. It never invents a wait time.
Live-chat handoff targets are Sunshine, Salesforce and AI SNS live chat.
The REST API, webhooks and custom domains
If a ready-made connector does not exist, the public API probably covers the gap.
- API keys live in Workspace settings → API keys. They are shown once, can be revoked, and require Hobby or higher.
- The API is JSON REST with SSE streaming (add
stream=1) and HMAC-signed webhooks with a delivery log, so you can verify and debug what was sent. - Rate limits are published: public chat allows 30 requests per minute per IP, polling 120 per minute, and auth 20 per 5 minutes per IP.
- Custom domains (Agent → Settings → Custom domains) let a subdomain CNAME cover the embed script, iframe and agent link. DNS is verified by lookup. Hobby or higher.
A sensible setup order
You do not need everything on day one. Most teams do best by adding one layer at a time and testing between each.
- 01Add knowledge sources
- 02Test in Playground
- 03Connect one channel
- 04Add actions and handoff
A rough plan:
- Start with knowledge, because an agent with a good source answers well on any channel.
- Test in the Playground before any customer sees it.
- Connect your main channel, such as the website widget or WhatsApp.
- Add lead capture and one lookup tool that removes your most common "where is my order" style question.
- Set shifts and alerts so handoffs reach a person.
- Only then add the API, custom domain or secondary channels.
Plan gates at a glance
| Capability | Requirement |
|---|---|
| Integrations (actions, tools) | Hobby or higher |
| Actions per agent | Ranges from 0 to 20, depending on plan |
| API keys | Hobby or higher |
| Custom domains | Hobby or higher |
| Helpdesk (scheduling, tickets) | Standard or higher |
| Outbound campaigns | Standard or higher |
| Advanced analytics | Pro |
Check the pricing page for current plan details, since prices and limits are read from the platform at runtime.
Doing this in AI SNS CHAT
Here is the walkthrough from an empty account to a connected, tested agent.
1. Create the agent. Use the guided wizard, then pick a persona from the starter set or write your own. Duplicate is useful later for copying persona, model and training data without carrying over conversations.
2. Add knowledge. Open Data sources and add Files, a Website or Q&A pairs. For documentation you already keep elsewhere, open Channels and choose the matching connector, such as Confluence, Google Drive or SharePoint. Watch for the truncation notice on large wiki syncs.
3. Test. Open the Playground and ask the questions customers really ask. If you want to compare models, Playground A/B compare runs two side by side. Model choice lives under Agent → Settings → AI.
4. Connect a channel. Go to Channels, choose your channel and follow its steps. For WhatsApp and Messenger, the Meta webhook signature is checked for you. Use the shareable link first if you want colleagues to try the agent before launch.
5. Add actions. Open the integrations area for the agent and enable Collect leads, Calendly or Cal for bookings, Stripe or Shopify if relevant, and any lookup tool you need. Remember that integrations need Hobby or higher.
6. Set up handoff. In Helpdesk → Scheduling, add team members, shifts and timezones, then choose where alerts go (Slack, Teams, LINE WORKS, WhatsApp, email or webhook). This needs Standard or higher.
7. Review. Check Activity → Chat logs (and Inbox for email), rate answers, and edit weak replies into the ideal answer. The Usage page shows credits per agent, and Workspace settings → Activity records who created, edited or uploaded each item.
If you get lost on any screen, ask Synthia, the built-in fleet manager. She can answer product questions by voice or text and run guided tours that navigate to the right screen and highlight the control. The full list of what connects is on the features page, and you can start with a free account.
Frequently asked questions
Which channels should I connect first?
Start with the one where most of your customers already write to you. For many international businesses that is the website chat widget, followed by WhatsApp or Messenger. Test on the shareable link first, then add channels one at a time so you can see where problems come from.
Where do WhatsApp and Messenger conversations appear?
In Activity → Chat logs. The Inbox is email-only. In Chat logs you can take over a chat, which pauses the bot, translate live, reuse saved replies, and flag, escalate, resolve or export conversations.
Can the agent change data in my other tools, such as a help desk?
The roughly 50 lookup tools in the catalogue are read-only, so the agent can look things up but not alter them. Built-in actions such as Collect leads, Escalations and Custom actions cover writing back to AI SNS CHAT or your own endpoints, and kintone supports read and write.
Do I need a paid plan to use integrations?
Yes, for most of them. Integrations, API keys and custom domains require Hobby or higher, Helpdesk and outbound campaigns require Standard or higher, and advanced analytics require Pro. The Free plan is still good for building and testing an agent.
Is a channel I do not see listed coming soon?
The connections page lists platforms on the roadmap, including X, Threads, TikTok, Apple Messages, RCS and Signal, but these are not live yet. If you need one now, the REST API and Zapier are the usual ways to bridge the gap.


