Skip to main content
This guide shows how to connect messaging channels to the iCommerce engine using an agent-driven flow.

Prerequisites

  • ResponseCX or an MCP-enabled agent
  • Access to iCommerce SDKs or CLI
  • Channel provider credentials

Connect a channel and route to iCommerce

  1. Connect your channel provider (chat, SMS, email, voice).
  2. Route incoming messages to a ResponseCX agent or MCP tool.
  3. Call iCommerce APIs or CLI for deterministic actions.
  4. Return results to the channel.

Run a gateway

Each channel has its own gateway process, and they all share one database and one ~/.stateset/channels.json:
Gateways answer questions in read-only mode and take no action that changes data until you pass --apply. Leave it off until you have watched a gateway handle real messages — with it on, anything that can message the account can drive a write against live commerce data.

Verify the result

Send a message from the channel and confirm the reply contains the expected order or return data. If the agent answers but with nothing specific, the gateway is connected and the --db path is pointing at a database without that order in it.

WhatsApp gateway

The linking flow for WhatsApp specifically, which needs a device scan.

iCommerce agent

What the gateway hands messages to.

CLI workflows

The commands an agent runs once —apply is on.

Skills

Teaching the agent how to handle a channel request end to end.
Last modified on August 29, 2026