Connect a Voiceflow agent to the messaging destination your customers or team already use. These manuals teach developer-hosted text relays: the platform delivers an authenticated event, the relay selects an isolated Voiceflow session, and its text reply returns to the same destination.

A bot token, integration listing or Send Message action supplies only part of that path. Each installation guide includes its account setup, incoming registration, reply mapping, customer test and release requirements. The examples are single-process starting points with persistent state; your team operates the host, secrets and recovery.

Choose a starting point

  1. Build an agent, give it a known support answer and publish a reviewed Environment.
  2. Choose an installation guide below. Obtain the required app/account access before hosting its relay.
  3. Test a real question and follow-up through that platform. A saved webhook or Voiceflow Run alone does not prove the connection. Verify the production route again after platform approval and release.

Implementation scope: The downloads implement text support through the stated provider/API. Apple requires an approved Messaging Service Provider and a tested human escalation path. WeChat uses Sinch’s verified Service Account integration. Discord uses explicit /ask commands. The manuals do not claim a managed Voiceflow connector or a second Studio installation path.

Installation guides

Guides

Existing documentation

  • Chat agents — exact session, action and trace contracts for your relay.
  • SMS — telephone text-message deployment and its provider-specific constraints.
  • Human agent hand-off — configure supported human-support integrations; a generic Messaging relay does not automatically inherit them.
  • Transcripts — inspect the agent’s exchange alongside provider delivery records.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.