Your contacts can tell when a message was written for a list. Not for them.
Messages that feel written, not generated. Dynamic personalization uses real contact data to build every SMS around the person receiving it — their intent, location, behavior, history, and timing.
Every message is unique. That’s why it gets answered.
Generic messaging gets ignored because it signals mass broadcast. Personalized messaging gets responses because it signals individual attention. The Dynamic Personalization Engine uses four data layers — identity, location, service, and behavior — to build messages that reference the contact’s actual situation. The same template. Thousands of unique outputs. Every one more relevant than a generic alternative.
First name, last name, relationship history. The contact’s name at the start of a message changes the read rate before a single word of the offer is processed. Identity data is the baseline — but it’s the other layers that make the difference between reply rates.
City, market, zip code, service area. One template with a location field serves every market — Baltimore gets ‘Baltimore,’ Phoenix gets ‘Phoenix,’ DC gets ‘DC.’ Combined with a local area code sender, the message reads entirely local to the recipient.
The specific service, vehicle, product, inquiry type, last purchase, or last interaction from the contact record. This layer makes a re-engagement message feel like a personal follow-up from someone who remembered — because the data says exactly what to reference.
‘Hi Sarah’ performs differently than ‘Hi there.’ The identity layer inserts first name, last name, or full name from the contact record at send. This is the most basic personalization, but it’s also the most immediate signal to the recipient: this message was sent to me, not to everyone.
first name · last name · identity keyword · personal address‘Your AC special in Baltimore’ resonates with a Baltimore contact in a way that ‘Your AC special’ does not. The location layer inserts city, region, zip, or service area — and combined with a local area code sender, creates a message that reads entirely local. One template, local relevance in every market.
city · region · zip code · service area · local area code pairing‘Your 2019 Ford F-150 is due for service’ is a different message than ‘Schedule your next service.’ The service layer inserts the specific vehicle, service type, product, or inquiry from the contact’s record. This is the layer that makes re-engagement messages feel like personal follow-up — because they reference what the contact actually asked about.
service type · vehicle · product · inquiry · specific referenceLast service date, last interaction, rep name, last offer received — timing and behavior fields make a message feel like the natural next step in an ongoing relationship, not a cold outreach. ‘It’s been 8 months since your last visit’ is more compelling than ‘We miss you.’ This layer is the difference between a re-engagement campaign and a re-engagement system.
last interaction · timing fields · rep name · behavior history · custom fieldsAt send time, TextingOnly renders each contact’s message individually. All four data layers are inserted simultaneously — name, location, service, behavior — producing a uniquely composed message for every recipient. No two messages in the campaign are identical. This protects deliverability (carriers flag uniform bulk sends) while maximizing relevance per recipient.
unique rendering · variable messaging · deliverability protection · simultaneous layer insertionVehicle year, make, model, last service date, service advisor name — the automotive contact record has enough data to make every message feel like it came from the service advisor who actually knows the car.
Service type, last visit date, property address, city, rep name — an HVAC company can reference the system installed three years ago and the technician who serviced it. That’s a different message from ‘Time for your annual checkup.’
Price range, neighborhood preference, last inquiry date, agent name — a real estate follow-up that references what the contact was looking for performs at a different level than a generic ‘Are you still searching?’
Role applied for, location, last application date, recruiter name — a candidate follow-up that references the specific role they applied for reads as personal attention, not a blast to a candidate pool.
Any dormant list has contact history — last purchase, last service, last interaction. The behavior and timing layers turn a re-engagement campaign into a message that says ‘we remember you’ rather than ‘please come back.’
Location data makes a centrally managed campaign read as locally sent. Each market’s contacts get their market’s message — city, local service reference, and local area code sender — all from one dashboard.
Fastest takes 30 seconds.
See dynamic personalization in action in your Messages app. 30 seconds.
Live demo →OTTO configured for dynamic personalization. Real contacts, real results, 90 days.
Start the pilot →We map the personalization engine to your contact data and campaign goals.
Schedule a call →