{"id":2938,"date":"2026-09-02T10:06:08","date_gmt":"2026-09-02T04:36:08","guid":{"rendered":"https:\/\/www.smsgatewaycenter.com\/blog\/?p=2938"},"modified":"2026-09-02T10:12:55","modified_gmt":"2026-09-02T04:42:55","slug":"message-preview-cost-estimation-before-sending","status":"publish","type":"post","link":"https:\/\/www.smsgatewaycenter.com\/blog\/message-preview-cost-estimation-before-sending\/","title":{"rendered":"Message Preview and Cost Estimation: Showing Users What They Are About to Send"},"content":{"rendered":"\n

The Preview Message API returns encoding, length, parts, estimated cost per part and, when you supply a DLT entity ID, the registered template your body matches. It does not multiply by parts, it does not multiply by recipients, and it does not know what your variables will expand to. This is how to build a preview and cost estimator that is right instead of reassuring.<\/p>\n\n\n\n

\"Abstract<\/a>
One character past the boundary is not one character more. It is a second billable segment.<\/figcaption><\/figure>\n\n\n\n

Table of Contents<\/h1>\n\n\n\n
    \n
  1. The Short Answer<\/a><\/li>\n\n\n\n
  2. TL;DR<\/a><\/li>\n\n\n\n
  3. What the Preview API Actually Returns<\/a><\/li>\n\n\n\n
  4. The Three Multiplications the API Does Not Do<\/a><\/li>\n\n\n\n
  5. Preview the Rendered Message, Not the Template<\/a><\/li>\n\n\n\n
  6. Reverse Template Lookup Is the Real Feature<\/a><\/li>\n\n\n\n
  7. Two Counters, and Why They Disagree<\/a><\/li>\n\n\n\n
  8. Building the Local Counter<\/a><\/li>\n\n\n\n
  9. Never Call Preview From the Browser<\/a><\/li>\n\n\n\n
  10. Debouncing, Caching and the Request Budget<\/a><\/li>\n\n\n\n
  11. What the Preview UI Should Actually Show<\/a><\/li>\n\n\n\n
  12. Preview at Save Time and in CI, Not on the Send Path<\/a><\/li>\n\n\n\n
  13. A Local Template Registry From template\/read<\/a><\/li>\n\n\n\n
  14. Decision Matrix<\/a><\/li>\n\n\n\n
  15. Build Order<\/a><\/li>\n\n\n\n
  16. Implementation Checklist<\/a><\/li>\n\n\n\n
  17. Ten Mistakes<\/a><\/li>\n\n\n\n
  18. What This Article Deliberately Does Not Claim<\/a><\/li>\n\n\n\n
  19. FAQs<\/a><\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n

    The Short Answer<\/h2>\n\n\n\n

    The Preview Message API<\/a> accepts a message body and a sender ID, and returns msgType<\/code> (text or unicode), length<\/code>, parts<\/code>, amount<\/code> (the estimated cost of one part), and, when you also pass dltEntityId<\/code>, the dltTemplateId<\/code> of the registered template your body matches. That last field is the capability worth building around, because it inverts the usual relationship: instead of you asserting a template ID and the platform checking it, you supply a body and the platform tells you which template it is.<\/p>\n\n\n\n

    What the endpoint does not do is finish the arithmetic. amount<\/code> is documented as the cost per SMS, and the official Python sample on the documentation page multiplies it by parts<\/code> and then by the recipient count to reach a campaign total. Those two multiplications are yours. So is a third one that nobody mentions: the body you preview is usually a template containing {#var#}<\/code> placeholders, and the body you send is that template with real values substituted in. Seven characters of placeholder can become forty characters of customer name. Preview the template and you will quote a number that the actual send does not honour.<\/p>\n\n\n\n

    An accurate estimator therefore does three things the naive one does not. It previews a rendered worst case rather than a template. It multiplies parts by recipients by cost per part, using the widest recipient in the list rather than the average. And it runs the preview call on your server, not in the browser, because the documented ways to authenticate that endpoint are an account password or an account API key, and both of them can send messages.<\/p>\n\n\n\n

    \n\n\n\n

    TL;DR<\/h2>\n\n\n\n