SMS usage and pricing, without the guessing.

This is first for a reason. The biggest savings rarely come from swapping a curly quote for a straight one — they come from asking whether something needed to be a text at all.

A simple test: does this need to interrupt someone? If yes, text. If no, email.

Well suited to SMS: "Your session is coming up." · "Can you make it today?" · "Haven't seen you this week — everything okay?" · time-sensitive schedule changes · personal, two-way conversations.

Better as email: newsletters and community updates · policy and pricing changes · event details and schedules · educational and long-form content · broad announcements and promotions.

Email inside Naamly doesn't carry a per-segment cost, so moving the right traffic to email is usually the single largest improvement available — and it isn't a compromise. It's the right channel doing the right job.

Before any broadcast, ask one question: who needs to receive this by text? Not who could receive it — who needs it.

Sent to all 400 members with a 2-segment message: 800 segments. The same message tightened to 1 segment: 400. Sent to the 75 members it actually applies to: 75.

That isn't a rounding difference — it's the same announcement delivered for a fraction of the usage. And it usually performs better, because the people who receive it are the people it was written for.

Targeting protects more than usage. Irrelevant messages drive opt-outs, and opt-out rates are one of the signals telecom carriers watch.

Don't use more segments than you need. If the same message can be communicated clearly and personally in one segment instead of two or three, tighten it up.

At the same time, do not sacrifice a meaningful member conversation simply to save a segment. Optimization matters most when a message is automated, recurring, or being sent to a large audience.

• Automated reminders and recurring templates — every edit compounds.
• Broadcasts to your full member list.
• Anything with merge fields. A template that looks like 150 characters may send at 175 once a long name, location or class title fills in — write to fit your longest value, not your shortest.

One-to-one conversations are where SMS earns its keep. Let those breathe.

Segment count isn't always obvious just by looking at a message, which is why it catches people out. Before sending a large broadcast or activating a recurring SMS automation, take a few seconds to check it.

Paste your message into the segment calculator above. It applies the same segmentation rules used by Twilio, our SMS gateway, and shows you exactly how many segments your message consumes and whether a small edit would bring it down.

Cutting a message from 2 segments to 1 saves one segment per recipient. Send that message to 500 people and you've saved 500 segments on a single send — from one edit, made once.

Don't eliminate personality — just understand the tradeoff. An emoji in a personal, one-to-one message probably isn't something to worry about. An emoji in an automated message sent 5,000 times may be.

These all switch a message to the denser encoding, dropping capacity from 160 characters to 70: any emoji; curly quotes and apostrophes (use "class" and Sarah's); em and en dashes (use a hyphen); the ellipsis glyph (use three periods); symbols like the euro sign, trademark or one-half (write EUR, TM, 1/2). Keep accented letters when a name needs them.

Word processors and phone keyboards insert curly quotes, em dashes and ellipses automatically. If you draft a template in Word or Google Docs and paste it in, you're very likely pasting characters you never typed. Drafting in a plain-text editor avoids this entirely.

Automations are powerful precisely because nobody has to think about them day to day. That's also why they're worth a periodic look.

• Does this automation still need to run at all?
• Does every step need to be an SMS, or could one be an email?
• Is anyone receiving two reminders about essentially the same thing?
• Can the trigger or audience be tightened?
• Has the template grown longer since it was written?

A four-touch sequence going to 200 members uses 800 segments each cycle. Move two of those touches to email and it drops to 400 — roughly 5,200 segments a year, from editing one automation once.