Other supported channel types
Understand website, email, API and provider-backed channel choices without assuming every connector is ready.
Use a test channel or sample conversation first. Confirm the visible result in ValueChat before applying the setup to production traffic.
How it works
- 01
Website
Website. A website inbox supplies the customer chat widget; configure its identity, website settings and routing before embedding it on a site.
- 02
Email and API
Email and API. Email inboxes require the installation mail setup or supported provider configuration. An API channel is a custom messaging entry point for your own application, not an automatic connection to an arbitrary social network.
- 03
Provider channels
Provider channels. Telegram, LINE and SMS options use their corresponding bot credentials or service providers where enabled. Use the actual channel setup screen as the available catalog for your installation.
- 04
Per-channel behavior
Per-channel behavior. Rich content, message windows, attachments, templates, identity information and delivery receipts differ by provider. Linking a channel does not give the AI permission to use unrelated business tools.
- 05
Verify each connection
Verify each connection. Test a new inbound and an authorized reply on the target provider and confirm the correct channel identity in the inbox. Do not infer every provider is configured from the presence of a channel card.
What to verify
✓The expected channel, conversation, contact or execution is visible.
✓The assigned person or agent matches the routing rule.
✓No customer-facing message claims an action that failed.
✓Activity or execution history contains enough context to investigate.
Collect the workspace, channel, conversation and execution identifiers, then contact support@valuechat.app. Never send API keys or passwords.