Channel Hub

Channel Hub is the Volt area for Tier 1 messaging connectors— including Slack, WhatsApp, Telegram, Microsoft Teams, and Instagram DM. All channels share HTTPS webhook ingress in volt-engine-service. Each customer registers their own bot or app; Maeyr routes inbound messages to the correct project by a unique routing key (Slack App ID, Microsoft App ID, WhatsApp phone number ID, Telegram tenant key, etc.).

Below the Volt Channels header, the Customer / User base strip opens your project's user directory — one place to define schema, import customers, and map connector primary keys (phone, email, Telegram ID) to customer rows for invoker subject binding.

Connector identity links are managed from each customer's detail drawer (not a separate tab). API reference: Directory sync & project users API.

• Open your project → Volt → configure Customer / User base if agents need per-user data (schema + CSV or Data sources sync + connector bindings).
• Open Channel Hub → choose a channel.
• Create the bot or Meta app on the provider side (see per-channel guides).
• Paste credentials → Validate → Connect.
• Configure Access — allow all users (*) or add per-user grants with channel-specific identities.
• For self-scoped agents (e.g. "my orders"), set up subject binding so identity fields are injected by the platform, not the AI.
• Deploy at least one enabled agent in builder-service, then test from an allowed identity.

Your platform operator exposes these URLs on volt-engine-service (replace the host if self-hosted):

1. User sends a message on the channel.
2. The platform posts a webhook to volt-engine-service at /v1/webhooks/*.
3. Engine resolves account, org, and project from the global routing index (App ID, phone number ID, tenant key, etc.).
4. Access is checked via channel_grants_v1 and optional Maeyr project membership.
5. The same Think→Act→Observe pipeline loads your project agent catalog and runs agents.
6. The reply is sent back through the channel API (Graph, Telegram Bot API, Bot Framework, etc.).

Current Tier 1 connector capabilities:

• Plain text inbound messages and text replies
• Per-project connection via Channel Hub (validate → connect → access grants)
• Unified access model (channel_grants_v1): allow all users (*) or per-user grants
• Conversation history (last 20 turns) per thread
• Same agent brain across all Tier 1 channels — shared HTTPS ingress in volt-engine-service
• Encrypted credentials at rest; secrets never stored in webhook queue payloads

Not yet supported in the pilot:

• Media (images, audio, video, documents)
• WhatsApp template / proactive messages outside the 24-hour session window
• Telegram bot commands (/start, slash commands) — send plain text instead
• Instagram/WhatsApp story mentions and reactions
• CSV import/export of access grants

• Customer support — let approved users query ops agents from WhatsApp or Telegram
• Field teams — run checklists and remediation agents from mobile messaging apps
• Internal IT — Teams bot for on-call runbooks and platform health agents
• Social DM triage — Instagram business inbox routed to your agent catalog