Overview
Connect providers that receive customer messages, carry Agent Desk replies, return delivery state, deliver notifications, and expose governed communication channels such as email, SMS, WhatsApp, voice, in-app, and push.
Capabilities
-
Customer message ingress into case conversations
-
Customer reply transport selected by case communication policy and conversation ownership
-
Delivery/read/failure status updates
-
Customer and staff notification delivery through configured providers
-
Channel capabilities for email, SMS, WhatsApp, voice, in-app, and push
Setup Steps (4)
-
1
-
2
Step 2
Create the inbound/outbound connection and select the supported capability roles.
-
3
Step 3
Configure case communication policy and channel routing for the relevant sources.
-
4
Step 4
Send and receive a test conversation and verify message, recipient, and delivery state.
Limitations
-
Customer-visible replies and staff-only internal notes remain separate records with separate visibility rules.
-
Transport ownership is stored with the conversation/case policy so replies return through the configured owning connection.
FAQs
How does Agent Desk choose where a customer reply is sent?
CustomerReplyRouting and case communication policy resolve the configured CUSTOMER_REPLY_TRANSPORT or source-owned route for the conversation.
Can notification delivery use different providers from conversation replies?
Yes. Customer and staff notification delivery are separate provider capabilities from the customer reply transport.
Pricing
Starter
USD 292.12 / annual
Team
USD 730.42 / annual
Pro
USD 1,460.91 / annual
Enterprise
USD 2,921.89 / annual