Connect customer-owned telephony, email, messaging, and social services. WonderCX does not supply carrier service, numbers, trunks, or provider subscriptions. Optional FreeSWITCH setup is a preview, not a production-certified PBX.
Administrators assign compatible SIP-over-WSS/WebRTC PBX accounts; agents connect their assigned phone and use audio, hold, mute, DTMF, and transfer controls without editing SIP credentials. An explicit Windows native-SIP preview supports UDP/TCP/TLS PBXs. Standard installers remain WebRTC-only; live PBX/audio qualification is still required.
Windows x64 Server setup can download and verify FreeSWITCH or connect to an existing PBX. Reviewed LAN configuration, per-Agent assignments, and explicit deployment controls remain required. macOS has a separate preview path; standard macOS/Linux builds do not install an engine. Production telephony publication is blocked.
Explore next stepsAn embeddable support widget with queue routing, attachments, agent replies, and governed scripted automation. Requires an exact allowed HTTPS origin, a public HTTPS proxy, and an awake, running WonderCX Server.
Up to ten customer-owned IMAP/SMTP mailboxes with separate queues, threading, approved sender aliases, mailbox-specific time zones and weekly routing hours, attachments, and a durable Server-local reply outbox. Mail continues importing while routing is closed; uncertain sends require review. Provider permissions and service limits apply.
Twilio SMS/WhatsApp, direct Telnyx, Vonage and AWS SMS, Meta WhatsApp Cloud, and a bounded configurable HTTP SMS adapter. A Twilio account can configure up to ten senders per SMS and WhatsApp channel, including the primary address. Each inbound sender can route to a queue, published channel flow, or direct Agent with a fallback queue; replies remain tied to the original sender. Server-owned outboxes, consent/opt-out handling, and reviewed campaigns respect provider rules. WhatsApp templates, reply windows, account approvals, and charges still apply.
Direct Facebook Messenger, Instagram Login, LINE, Telegram, and single-tenant Microsoft Teams personal text chats in the public cloud. Configured connectors can receive and reply to supported private conversations; explicitly configured LINE/Telegram groups and Facebook/Instagram public-comment replies have separate account and permission requirements. Local sentiment labels and moderation/transition controls in the Social care screen do not perform provider-side actions. Permissions, supported media, reply windows, and live provider qualification vary by connector.
Explore next stepsCreate, review, schedule, and cancel campaigns for up to 100 existing, scoped, opted-in conversations: SMS and WhatsApp, plus private Social conversations on Telegram, LINE, Messenger, and Instagram. The Server rechecks consent, opt-outs, sender, policy, reply windows, and quiet hours before dispatch. Public comments, groups, imported contact lists, and automatic catch-up after a missed schedule are excluded; uncertain deliveries need individual review.
The desktop contains draft, review, sentiment-label, and moderation controls for public Social content, but these controls currently update local workspace state rather than publishing or moderating posts on Facebook/Instagram. Provider-side Page publishing, like/hide actions, and moving public comments into a private thread are not available. Private messaging replies and governed private-message campaigns are separate supported workflows when their provider accounts and permissions are configured.
A disabled-by-default, scoped server-to-server API supports limited queue/minimal-interaction reads and idempotent Chat/Social intake. Reviewed outbound metadata webhooks require a compatible receiver. This is not a general-purpose write API.
X and LinkedIn access contracts and live customer-provider qualification remain outstanding. Fax support is not confirmed. No universal provider coverage, production certification, or availability date is promised.
