Deploy

Messaging channels

Connect Facebook Messenger, Instagram, WhatsApp, Telegram, Slack, or Email to a bot so people can reach it where they already are. This is the connect counterpart to voice numbers — a number is purchased, a messaging channel is connected with your own credentials. Manage them in the console under Channels.

Supported platforms

Each platform is connected by pasting a token (plus a few ids for the Meta platforms). Tokens are stored encrypted and never shown again.

Platform	What you provide	Credential
Messenger	`page_id`	Long-lived Page access token
Instagram	`page_id` + `ig_account_id`	The linked Page's long-lived access token
WhatsApp	`phone_number_id` + `waba_id`	System-User token
Telegram	nothing extra	Bot token from @BotFather
Slack	the app's signing secret	Bot User OAuth token (`xoxb-…`)
Email	the inbox address	None — Hania gives you a webhook URL; your email provider generates a signing secret you paste back

For the Meta platforms (Messenger, Instagram, WhatsApp) the token must be long-lived (a System-User token for WhatsApp). A channel receives messages around the clock, so a short-lived token would stop working within hours and break the channel. Use a long-lived Page token or a Business Manager System-User token. (Telegram bot tokens don't expire.)

Telegram is the simplest channel to connect — free, instant, no app review or fees.

In Telegram, open a chat with @BotFather.
Send /newbot and follow the prompts to pick a name and a username.
BotFather replies with a token (looks like 1234567:AA…). Copy it.
In the console, Channels → Connect a channel → Telegram, choose the bot to assign, and paste the token. That's it — no ids to enter.

Slack

Slack connects a Slack app to a bot, so the bot answers direct messages and @-mentions in your workspace.

Create a Slack app in your workspace. Under OAuth & Permissions, add the bot scopes im:history, app_mentions:read, and chat:write, then install the app to get its Bot User OAuth token (xoxb-…). Copy the Signing Secret from Basic Information → App Credentials.
In the console, Channels → Connect a channel → Slack, choose the bot to assign, and paste the bot token and signing secret.
Hania returns a Request URL. In your Slack app under Event Subscriptions, enable events, paste it as the Request URL, and subscribe to message.im and app_mention.
Reinstall the app so the new scopes and subscriptions take effect.

Email

Email is passive — there's no token to paste. You give Hania an inbox address, wire your email provider to forward mail there, and the bot reads each message and replies through its own email tool (your SMTP/ESP — Hania isn't the sender). Setup is two steps, and the inbox stays Pending until you finish the second.

In the console, Channels → Connect a channel → Email, choose the bot to assign, and enter the inbox address (e.g. [email protected]). Hania shows a webhook URL — copy it.
In your email provider, set up inbound forwarding for that address to the webhook URL. The provider generates a signing secret for that webhook. Any provider that supports signed inbound webhooks works — BlacklistGuard is one example.
Back in Hania, paste that signing secret into the inbox's Signing secret field (on the setup screen, or later via the inbox's Edit view). This arms the inbox — it flips from Pending to Active. The secret is write-only; Hania shows only whether one is configured, and the same field rotates it.
Make sure the assigned bot has an email-sending tool and is configured for email replies (not, say, a voice receptionist). Without a sending tool it can read incoming mail but can't respond — the setup screen warns you when that's the case.

Connecting a channel

Open Channels in the console and choose Connect a channel.
Pick the platform — the form then asks for what that platform needs (ids for the Meta platforms; just the token for Telegram; a token + signing secret for Slack; just the address for Email).
Choose the bot that should answer messages on this channel. (Create a bot first if you have none.)
Enter the platform ids and paste the token. You can add a display name, but you don't need to — leave it blank and the channel is labelled with the account's own name (the Messenger Page name, the Instagram @username, or the WhatsApp verified name and phone). Set it only to override that with your own label.
Connect. A bot can have more than one channel, and you can connect the same platform for several bots.

Connecting a channel no longer asks for a tenant or workspace id — the workspace is taken from the bot you assign.

Validation on connect

When you connect, Hania subscribes the account's webhooks before saving — which also validates the token, ids, and permissions. If any of those are wrong, the connect fails and the underlying platform (Graph API) error message is shown so you can fix it. Connecting an account that's already connected is rejected too.

Editing, reassigning & removing

Use Edit on a channel to rename its label or reassign it to a different bot — no reconnect needed. The platform, its ids, and the token are fixed; to change any of those, remove the channel and connect it again (you'll paste the token once more, since tokens are never stored in a readable form). Removing a channel stops it from receiving messages immediately.

Coming later: one-click "Connect with…" OAuth onboarding (no token pasting), outbound calling on channels, and per-channel billing. For now, connect by pasting a token as above.

Every message that arrives on a connected channel becomes a conversation tagged with that platform's channel, so you can review and report on it alongside your other channels.