What's the difference between two-way SMS and SMS notifications?

The marketing term "SMS" gets used loosely. Functionally, there are three different things:

1. One-way notifications:

Automated text messages sent from a no-reply number. Appointment reminders, on-the-way alerts, payment receipts. Customer can't reply meaningfully — replies either bounce or go to a black hole. This is what most "SMS-enabled" FSM platforms ship by default.

2. Two-way SMS:

Real conversation. The office can send a message and the customer can reply. The reply lands in a shared inbox where any team member can pick it up. The conversation thread persists, attached to the customer record. Two-way SMS requires real telephony infrastructure (a business DID with messaging enabled, a shared inbox UI, message threading).

3. Customer-initiated text:

A customer texts the business number with a question. This requires both a published business number that accepts SMS (not all do) and a system that surfaces inbound messages to the team in real time. In the absence of this infrastructure, customer texts go to whoever's personal phone the number forwards to.

Why two-way matters:

Customers want to text. Younger demographics increasingly prefer text over phone calls for routine service questions. A business that only sends one-way notifications loses every conversation that the customer would have continued — "actually, can we move this to Tuesday?" "What time exactly?" "I'm running late, can you wait 15 minutes?" These all evaporate without two-way SMS.

The 10DLC requirement (US):

In the US, business SMS at any meaningful volume requires 10DLC (10-Digit Long Code) registration with the carriers. Without it, business SMS gets aggressively spam-filtered. 10DLC registration takes 3-5 business days and requires brand verification + use-case approval. Most FSM platforms either include 10DLC handling or explicitly punt it to the customer.

The shared-inbox question:

Two-way SMS requires deciding who in the business can see and respond to inbound texts. Without a shared inbox, every text becomes a private conversation between the customer and one team member. With a shared inbox (the right model), any team member can pick up the thread, the customer's history is visible, and conversations don't get lost when one person is out.