TextPreflight is a provider-neutral API for analyzing final SMS text before delivery. It detects GSM-7 or Unicode encoding, exact billable segments, invisible-character risks and boundary changes. Simulate real template variables, surface worst cases and estimate campaign cost from your own unit price—without storing message bodies.
Hi Product Hunt — I created TextPreflight to solve a deceptively expensive messaging problem: a single Unicode character, extension-table symbol or real template value can change an SMS encoding and push it across a billable segment boundary.
TextPreflight turns that hidden behavior into a deterministic pre-send check. It reports encoding, segment count, remaining capacity and Unicode risks; simulates realistic template-variable combinations to surface worst cases; and estimates campaign cost using recipient volumes and a unit price supplied by the caller.
The service is provider-neutral, runs at the edge and does not store message bodies. Developers can try the interactive tools without creating an account, integrate through the documented API or use the lightweight JavaScript client.
I would value candid feedback from teams working with multilingual or variable-heavy message templates. Which edge cases would make this preflight check more useful in your production workflow?