For the complete documentation index, see llms.txt. This page is also available as Markdown.

Source Configuration

Purpose

Create and configure channel sources that define how traffic enters Syntphony Messaging and where it is routed—whether to a bot in the portal, a WebChat widget, or an external HTTPS endpoint (WhatsApp Forward).

Source types

Type
Use when

Widget

WebChat on your website; routes to a bot and optional Source Theme.

WhatsApp

WhatsApp handled in the portal; routes from a phone number to a Bots Configuration destination.

WhatsApp Forward

WhatsApp events are forwarded to an external system (for example AWS API Gateway). See WhatsApp Forward source.

Prerequisites

  • For WhatsApp and WhatsApp Forward: Phone Configuration is complete for the number you will use.

  • For WhatsApp and Widget: a bot is available in Bots Configuration.

  • For WebChat: a Source Theme is recommended before go-live.

  • Permissions to manage administration settings in the Messaging Portal.

Configuration order

Complete administration assets in this order when setting up a new environment:

  1. Bots Configuration (required for Widget and standard WhatsApp sources)

  2. Phone Configuration (WhatsApp and WhatsApp Forward)

  3. Source Theme (WebChat branding, optional but recommended)

  4. Source Configuration (this page)

For WhatsApp Forward integrations only, steps 1 and 3 can be skipped; you still need step 2 before creating the forward source.

Create a source (general steps)

  1. Open Administration → Source Configuration and start Create Source.

  2. Enter Source Name and optional Description.

  3. Select Type (Widget, WhatsApp, or WhatsApp Forward).

  4. Complete fields for the selected type:

    • Widget: widget configuration and destination bot; assign a Source Theme when available.

    • WhatsApp: origin phone number and destination bot.

    • WhatsApp Forward: phone number, Destination URL, Model, and optional headers/token settings — full reference in WhatsApp Forward source.

Create Source with WhatsApp Forward type selected
Create Source — WhatsApp Forward type (external forwarding)
  1. For WhatsApp and Widget sources only: if your operational model requires it, enable Console Direct so handover attempts go directly to the Live Agent Console without contacting a bot first.

  2. Save the source.

  3. Validate the created source:

    • Widget: installation widget script and theme.

    • WhatsApp: linked phone and bot are active.

    • WhatsApp Forward: destination URL responds over HTTPS and receives test events (see WhatsApp Forward source).

Configure handover schedule by source

Applies to sources that use portal routing (Widget and standard WhatsApp), not WhatsApp Forward.

  1. Open the source in edit mode.

  2. Enable the schedule option for the source.

  3. Select the source timezone.

  4. Add one or more time ranges.

  5. Save the source.

Schedule behavior:

  • You can define multiple ranges (for example, 08:00-14:00 and 15:00-19:00).

  • Each new range must start after the previous range ends.

  • The full-stop option to disable handover for the source overrides schedule ranges and blocks all handovers.

  • You can configure a custom message shown to end users when handover is unavailable.

Operational notes

  • Source routing defines how conversations move from channel origin to their destination.

  • WebChat: routing uses the selected destination bot.

  • WhatsApp: routing uses the selected origin phone and destination bot.

  • WhatsApp Forward: routing leaves the portal; events go to the configured Destination URL. Outbound replies typically use the Syntphony Messaging API from your external platform.

  • Use Console Direct on bot-routed sources when handover should skip the bot-contact attempt.

Expected outcome

  • A functional source is available for Communication and routing (or forwarding) as designed.

  • Each source type is mapped to the correct channel assets.

  • WhatsApp Forward sources deliver events to the external endpoint documented in WhatsApp Forward source.

Last updated

Was this helpful?