I Built a Long SMS Demo That Keeps the Message Together

Description and use

The demo shows one logical long message sent via a single Telnyx Messages API call, with carrier-level chunking handled by Telnyx and a parent record collecting child segment statuses. Two modes are demonstrated: long-message chunking and a sequence of four separate medium-length messages.

Problem

A complete appointment reminder can exceed one SMS segment, causing fragmented delivery and multiple independent message deliveries to reason about.

Outcome

The demo demonstrates two modes: long-message mode shows automatic chunking into one logical message, while sequence mode sends four medium-length appointment messages as distinct readable bubbles. The parent-child message relationship is reusable for appointment systems, logistics platforms, or incident-notification services.

Workflow

• Validate the destination number
• Require a message longer than 1,530 characters for the long-message demo
• Call the Telnyx Messages API once
• Store the returned parent message ID
• Verify the signed webhook request in the delivery path
• Read the child message ID and parent message ID from the webhook payload
• Update the delivery record with the child and parent message IDs

Evidence

The obvious fallback is to send several separate texts. That works mechanically, but it makes the notification feel fragmented and gives the application several independent deliveries to reason about.

Source

The application sends one logical long message. Telnyx handles the carrier-level chunking, and the application keeps a parent record that can collect the statuses of the child message segments.

Source

The server is an Express application using the Telnyx Node.js SDK. Its main send path is intentionally small: validate the destination number, require a message longer than 1,530 characters for the long-message demo, call the Telnyx Messages API once, store the returned parent message ID.

Source

The webhook path handles the delivery side. It verifies the signed request, reads the child message ID and parent message ID, and updates the delivery record.

Source