Skip to content

Channels

Channels overview

Every channel you can connect to ClickFix, how each one connects, and links to the detailed set-up guides.

A channel is a way your customers reach you. Messages from every connected channel land in the same inbox as conversations, and your reply goes back through the channel the message came from.

Connect channels from Channels → Add channel in the left menu.

Supported channels

ChannelHow it connectsGuide
EmailRouting address or your own mailbox (IMAP + SMTP)Email
WhatsAppSign in with Meta, pick a WhatsApp Business numberMeta channels
InstagramSign in with an Instagram professional accountMeta channels
MessengerSign in with Facebook, pick a pageMeta channels
TelegramBot token from BotFatherTelegram
SlackAdd ClickFix to your Slack workspaceSlack and Teams
Microsoft TeamsYour own Azure bot registrationSlack and Teams
Google ChatYour own Google Chat app (Cloud project + service account)Google Chat
SMSYour own Netgsm, İleti Merkezi or Twilio accountSMS and phone
Phone (voice)Your Twilio number or Netgsm PBXSMS and phone
API channelAny system over signed HTTPBelow on this page
Web widgetOne line of code on your siteWeb widget

Channel settings

Each channel's Settings menu lets you set:

  • AI agent: let the AI agent answer this channel's conversations first.
  • Automatic greeting: the first message sent to a new conversation.
  • Business hours and Time zone.

Channel health

The Channels page shows each channel's status: last inbound message, last webhook, messages sent and failed in the last 24 hours, and the access token expiry when there is one. If the provider rejects the connection, the channel is marked Needs reconnect. Use Check to refresh the status and Pause to stop a channel temporarily.

When you disconnect a channel it stops receiving and sending messages; existing conversations are kept.

API channel

The API channel connects a system ClickFix does not support directly (your own app, another messaging service) to the inbox:

  1. Create it with Add channel → API channel. The screen shows the Inbound message URL and a signing secret. Secrets are shown only once.
  2. POST customer messages to that URL as JSON.
  3. Agent replies are sent to the webhook URL you provide, signed the same way.

Every request carries two headers: X-ClickFix-Timestamp (Unix seconds) and X-ClickFix-Signature, computed as:

X-ClickFix-Signature = sha256=hex(HMAC-SHA256(secret, timestamp + "." + body))

The message body schema is in the API reference.