Outborn Agent Platform · Manual
Channels
Connect agents to supported communication channels while keeping provider setup, identity, permissions, and delivery behavior explicit.
Applied guidance
Best practices for channels
Recommended
- Confirm that the desired channel is available in the deployment before configuring its provider.
- Check identity mapping, consent, delivery failure behavior, and audience access.
Avoid
- Do not assume an ordinary provider connection automatically creates an agent messaging channel.
01
Provider connections
External email, collaboration, and productivity services are configured through their supported connection flows. A connected provider does not necessarily provide a direct agent conversation channel.
02
Facebook and Instagram
Messaging integrations can route supported Facebook and Instagram conversations to an agent after provider setup and access checks.
03
LINE
Configure the relevant LINE channel/provider credentials and webhook behavior where supported.
04
Use a supported WhatsApp provider and complete any provider or regional requirements before production messaging.
05
Voice and telephony
Voice channels also require telephony provider, number, routing, and regulatory configuration.
06
Web and embed
Published or embedded agents should use an explicit access model and must not expose private organization resources to unauthenticated visitors.
07
Provider-specific setup
When a provider requires configuration outside OutbornAI, use the provider's precise official setup or regulatory page rather than a generic homepage.
Related documentation