Connectors guide
Connectors let a Skill talk to people on popular channels. Requirements and availability can vary by channel, but the rollout strategy is usually the same: start small, learn, then expand.
Recommended rollout
- 1) Start with one channel and one outcome.
- 2) Define tone, privacy rules, and when to hand off to a human.
- 3) Launch with a limited audience (or internal team) before scaling.
- 4) Add more channels only after behavior is stable.
Channel requirements (high level)
Discord
What you’ll need
- • Admin permission to add a bot
- • A list of channels to start with
Notes
- • Great for communities and support channels.
- • Start with one channel and clear handoff rules.
What you’ll need
- • A supported WhatsApp connector setup
- • A rollout plan (who can message first)
Notes
- • Availability can vary by region/provider.
- • Treat onboarding and consent as part of setup.
SMS
What you’ll need
- • A phone number / SMS provider integration
- • A simple policy for opt-in and stop keywords
Notes
- • Universally accessible.
- • Keep messages short and avoid sensitive data.
What you’ll need
- • A supported connector and access to the account
- • A plan for business/creator messaging
Notes
- • Availability can vary.
- • Expect setup to involve account permissions and policies.
What you’ll need
- • A supported connector and access to the page/account
- • A plan for message routing and handoff
Notes
- • Availability can vary.
- • Make escalation to a human easy.
Twitter/X
What you’ll need
- • A supported connector and app access
- • A plan for rate limits and usage rules
Notes
- • Availability can vary based on platform policies.
- • Start with low volume and clear boundaries.
Want a recommendation? Tell us your audience and channel preference, and we’ll suggest a simple first Skill to launch.