Telnyx Messaging

Save the Telnyx API key and public signature key once, then choose that connection when creating another connector. Each connector has its own channel and sender, so you can use several numbers or messaging channels from the same account. The saved connection also works with Telnyx Voice for incoming calls.

Manage numbers, messaging profiles, WhatsApp registration, RCS agents, and channel approvals in Telnyx. Connic lists the senders available to your account. Appearing in the selection list does not replace the provider's registration, testing, or production approval requirements.

A Telnyx messaging profile contains message-delivery settings, including the incoming webhook. For a Telnyx-owned SMS or WhatsApp number, Connic configures its existing profile only when that profile belongs to the selected number. Profiles shared with other numbers or short codes must be separated in Telnyx first. RCS uses the selected RCS agent's webhook.

SMS and WhatsApp on the same number can share one Connic webhook while using separate connectors and linked agents. Use the same saved connection and profile for both channels. Connic routes each message by channel and recipient. Remove existing failover webhooks or Telnyx AI assistant routing before setup; the setup guide also covers manual webhook setup for external WhatsApp numbers.

Removing one channel keeps the other channel's shared route in place. When the last connector using the route is removed, Connic clears the callback only if it still points to Connic. Manually changed URLs are preserved; earlier provider routes are not restored.

Connic verifies Telnyx's signature and checks the message's channel, sender, recipient, and profile before dispatching it. The agent receives normalized text and addresses, message and event identifiers, a conversation identifier, and the original provider payload. Supported attachments are downloaded into Connic's file-input format.

Choose a model that can process the supplied image, audio, or document types. Incoming attachments have a combined limit of 10 MiB per message. Repeated delivery of the same accepted event is deduplicated, and delivery or read notifications do not start a new agent conversation.

For replies, use matching inbound and outbound connections, channels, senders, and profiles. Leave the outbound recipient unset to reply to the verified sender of the incoming message. Connic checks the originating connector before using that destination.

For notifications, supply to in the message output or save a default recipient. A recipient in the output takes precedence over the default, and the default takes precedence over the incoming sender. Return plain text for a simple reply or structured output for media and templates. Explicit connector calls work as agent tools or from middleware.

Enable Connic sessions on the agent and set the session key to input.conversation_id. Choose a session lifetime that fits your use case. Messages from the same customer to the same sender on that inbound connector can then use the earlier conversation while the session remains active.

The conversation identifier separates connectors, accounts, channels, and senders. Sharing a Telnyx connection between SMS, WhatsApp, and Voice does not merge their histories. Without session configuration, messages start independent runs.

Provide public media URLs for Telnyx to fetch: up to ten attachments for MMS or one for WhatsApp or RCS, subject to each channel's media limits. WhatsApp needs a media_type such as image, video, document, audio, or sticker. Images, videos, and documents can include a caption. Send audio or stickers separately from text; RCS text and media also use separate messages.

Outside WhatsApp's 24-hour customer-service window, use an approved template. Set whatsapp_template as a connector default or pass it with an individual message, using the template ID or its name and language with any component parameters. A default template replaces free-form output. The message examples show the supported fields and limits. RCS sends through the configured RCS agent without automatic SMS fallback.

Review the incoming message, tool calls, and generated response in the Connic run. The outbound result records the Telnyx message ID, message type, and returned sender and recipient details. Use that ID to find the corresponding message in Telnyx and investigate channel or carrier errors.

A successful outbound result means Telnyx accepted the request. Check final delivery in Telnyx. If submission has an unknown outcome after a timeout or server error, inspect the provider's message logs before resending so the customer does not receive a duplicate.