The Catalog tab in Connect is the shop window of every channel Natiq offers. It is deliberately honest: a channel only says Ready when it can carry a conversation in both directions, receiving customer messages and sending replies. Everything else stays visible but locked, so you can see what's on the way.
How the catalog is organised
The catalog groups channels into tiers, each with a short note:
- 1N live
- 2Ready
- 3Coming soon
- Available now: connect these today. Messages arrive in your inbox and the agent you assign replies.
- In development: channels we can already send on but can't yet receive from. They stay locked so a channel never quietly drops what customers say. At the time of writing nothing sits in this tier.
- Planned: on the roadmap.
Each tile shows a pill: Ready, Coming soon, or N live when you already have that many channels of the type connected. Use the search box to find a channel by name.
Available now
| Channel | What it's for | What you provide |
|---|---|---|
| Web Chat | Our chat widget on your website. | Nothing: created automatically for each agent you publish. |
| A WhatsApp Business number through Meta Cloud. | Phone number ID, access token, business account ID. See Connect WhatsApp. | |
| Telegram | Your Telegram bot's conversations. | A bot token from BotFather. See Connect Telegram. |
| Messenger conversations from your Facebook Page. | Page ID and a Page access token. | |
| Instagram DMs from your professional account. | Instagram account ID, linked Page ID and a Page access token. | |
| A support mailbox turned into conversations. | Mailbox address and an email provider key. See Connect Email. |
For Facebook and Instagram the form also offers an optional Verify token and App secret. The Page ID and Instagram account ID are numeric IDs from Meta Business Suite, not the Page name or the @username.
Coming soon
These tiles are locked today. The right-hand column is the reason each tile gives.
| Channel | Status |
|---|---|
| SMS | Waiting on our SMS carrier integration. |
| Microsoft Teams | Needs a Bot Framework app and Azure registration. |
| Slack | Needs Slack workspace authorisation and the Events API. |
| API | The contract is being finalised so it stays stable once published. |
| RCS | Needs a verified Google RBM agent. |
| Voice | Needs a telephony provider, and conversations that are not text. |
| TikTok | Not started — tell us if you need it. |
| Not started — also needs a decision on China-region hosting. | |
| LINE | Not started — tell us if you need it. |
Need a locked channel?
The catalog notes say that telling us which planned channels you need moves them up the roadmap. Contact support.
One agent, many channels
On every channel except Web Chat, one agent can answer several channels, but each channel has exactly one agent. Web Chat is the reverse: there is one Web Chat per agent, created by publishing, and Connect lists it read-only. The one thing you can set there is which queue it lands in (Choose queue); its agent, key and design stay with publishing in Agent Builder.