SMS and Telnyx

Lyntaris supports SMS workflows with Telnyx for inbound webhook handling, DreamOS-style messaging UI, status updates, and outbound send via the Telnyx REST API.

Supported patterns

• Inbound SMS: Telnyx delivers webhooks to a dedicated HTTPS tunnel (e.g. {stack}-sms.{domain}) forwarded to a local listener on your SMS webhook port; messages appear in the messaging UI.
• Outbound SMS: Tool or automation flows can send SMS using your API key, messaging profile, and from number (often the same caller ID used for SIP).
• Optional Flowise auto-reply: On builds that include the SMS bridge, inbound text can be answered with a non-streaming Flowise prediction (today mapped to Primary (RAG) - Web Text until a dedicated SMS Primary RAG seed exists). See WhatsApp Cloud API for the full Primary RAG / tunnel / prediction model; WhatsApp uses Primary (RAG) - WhatsApp instead.

Typical usage

• A voice or chat session triggers a follow-up SMS (Flowise tool → Unity executes send with session context).
• Inbound SMS notifications appear in MessagingManager chats; operators can reply manually when the integration allows.
• Status webhooks (queued, sent, delivered, etc.) can drive UI or logging.

Configuration (conceptual)

• Telnyx API key, messaging profile ID, SMS webhook port (often derived from slug like WhatsApp), and from number live in the same service configuration asset as the rest of the stack.
• Tunnel hostname and httpHostHeader follow the same Cloudflare pattern as WhatsApp Cloud API (separate -sms hostname).

For field-level detail, use your deployment’s Lyntaris service configuration reference or support runbook.