{
  "id": "p_X3ARo7GRUkHFgXqr",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_X3ARo7GRUkHFgXqr",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apievangelist"
  },
  "body": "A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: \"Twilio API Pricing: What a Text Message Costs, and What Gets Added,\" Kin Lane, November 12, 2026, https://apievangelist.com/2026/11/12/twilio-api-pricing-what-a-text-message-costs-and-what-gets-added/\n\nMarisol ran operations for a small group of dental offices, and the reminder texts were her project. She had a spreadsheet with one column for patients, one for messages a month, and one for the price. The price was $0.0083, which she'd copied from a Twilio page weeks ago and never questioned.\n\nShe opened the post over lunch, expecting confirmation. It started well. Twilio charges for what you send, not for seats or a subscription, and there is a free trial with no credit card. That suited a project she hadn't been allowed to budget for yet.\n\nThen she reached the part about incoming messages. Her reminders asked patients to reply C to confirm, and most of them did. The post said Twilio charges for incoming messages at the same SMS rate, so a two-way conversation costs twice what the outgoing side alone suggests. She looked at her spreadsheet. Her single column was about half of what it should have been, and she felt a small, specific embarrassment, the kind that comes from finding an error before anyone else does.\n\nThe next section made it worse. Segments, not messages. Her reminders included the office name, the date, a street address and sometimes a tooth emoji the front-desk staff liked. She had no idea whether those were one segment or three. According to the post, a long message or one with emoji and special characters splits, and each piece is charged.\n\nShe read the list of additions with her arms crossed. Carrier fees, a monthly charge for the number, $1.15 for a long code, $0.001 for each failed message, and registration for US business texting. The post gave her a formula: messages × (Twilio rate + carrier fee), plus numbers, plus registration. It was a fair formula, but it had a hole in the middle. The carrier fee had no number in it. The post said the fees vary by carrier and live on Twilio's pricing page. Marisol wanted a figure she could put in a cell, and to her the answer felt like homework handed back. She also thought the post was kinder to Twilio than she would have been. Pay-as-you-go sounded friendly until you tried to predict the bill.\n\nStill, she couldn't argue with the honesty of the dates. The post said it read the pages on November 9, 2026, and quoted Twilio's own line that its SMS pricing was \"current as of October 2026\". It also warned, plainly, \"Prices change.\" She had been about to show her director a number with no date on it at all.\n\nShe skipped the Conversations section. Her patients weren't chatting across WhatsApp and the web, they were confirming appointments, so per-user pricing didn't apply to her. She noticed that she was relieved to be able to ignore something.\n\nShe didn't rewrite the whole budget that afternoon. She added three columns to the spreadsheet: replies, segments per message, and carrier fee, the last one left empty and highlighted yellow. Then she exported last month's reminder texts from the scheduling system and started counting how many of them ran past a single segment, beginning with the ones that had the tooth emoji.",
  "title": "Fiction: A reader of \"Twilio API Pricing: What a Text Message Costs, and What Gets Added\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-11-12T18:51:32.731Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}