Facebookpixel Enrich Your SMS With Dynamic Landing Pages - SMSMobileAPI
Enriched SMS with personalized landing pages - SMSMobileAPI

How Rich SMS Works

Why Rich SMS works→

SMSMobileAPI transforms a standard SMS into an Enriched SMS experience by attaching a Landing Page Template powered by dynamic variables, action buttons and full response tracking.
Turn simple SMS messages into interactive digital experiences — quickly, reliably, and at scale.

Instead of a basic SMS, you can send a richer message with a simple, mobile-friendly page — personalized.
Enriched SMS (SMS + interactive landing page)
Faster replies with 1-tap buttons
Less support & fewer back-and-forth
Track actions (responses table)
Reusable templates via Template GUID
Send via Dashboard or Send via Mobile App or via API
Log in to the Dashboard Create a FREE account

What is an Enriched SMS?

We allows you to send Enriched SMS by linking any SMS to a customizable landing page generated automatically through a Landing Page Template.
Each message includes a short link that opens a dynamic page containing personalized information, action buttons and interactive elements.
✓ It works on any phone: the SMS contains a link to a mobile landing page (no RCS app required).


Templates in your dashboard

Build once: title, content, design, placeholders, buttons.

Instances per recipient

Each Enriched SMS generates a unique Landing Page Instance with a guid_instance.


This feature gives you the ability to include:

  • A Landing Page Template defined in your SMSMobileAPI dashboard
  • Dynamic placeholders filled via placeholders_json
  • Action buttons that redirect to URLs you specify or trigger backend states
  • A structured data model that stores each interaction in the responses table

SMS alone is limited

Plain SMS can’t show structured info, buttons, confirmations, or capture actions reliably.

Templates add structure

Your message becomes a clean landing page: content, details, logo, and action buttons.

Actions = automation

Each button can redirect or store a state (example: confirmed=1) for analytics & automation.

Two ways to send Enriched SMS

Option A — Dashboard form (no code)

Select destination number, choose the template, fill dynamic values, then click Send.

  • Select a template
  • Enter destination phone number
  • Fill placeholders (dynamic values)
  • Click “Generate landing + Send SMS”
Best for manual usage, quick tests, or support teams.

Option B — API (automation)

Send Enriched SMS by calling the API with the recipient number + Template GUID + placeholders_json.

  • Generate landing URL via API
  • Insert it into your SMS (replace [landingurl])
  • Send the final SMS via API to the recipient
Best for e-commerce, invoices, appointments, CRM/ERP workflows.
✓ You can mix both: build templates in the Dashboard, then send Enriched SMS automatically via API whenever you want.

How the feature works (visual tutorial)

1
Create your Landing Page Template
SAVE

Define title, content, design, placeholders and buttons. Save to get a Template GUID.

2
Generate a Landing Page Instance
GENERATE returns: guid_instance + short_link

Send Template GUID + placeholders_json. SMSMobileAPI returns a short link and a guid_instance.

3
Send SMS containing the link
SEND [landingurl]

Insert the short link inside your SMS. Keep [landingurl] in your template for automation.

4
User opens the landing page
CONFIRM RESCHEDULE

The page shows personalized content for that guid_instance, plus action buttons.

5
User clicks a button
CONFIRM

Each click is tracked with action_key and choice_label.

6
Track it in the responses table
DB Stored response guid_instance + action_key + created_at Ready for CRM / ERP automation

Every interaction is recorded: guid_instance, template_id, action_key, var_name, var_value, and timestamp.

✓ The result: users take action instantly, and your system updates automatically.

Real-life examples

Example A — Event invitation (RSVP)
Buttons: YES / NO
Template name
Event invitation
Placeholders
{name}, {event_name}, {date}, {time}, {location}
Landing page
Shows details + RSVP buttons
SMS sent to: 3249XXXXXXX
Hi {name}! You're invited to {event_name} on {date} at {time} (📍 {location}).
Please RSVP here: [landingurl]
YES → Update state: rsvp=1
NO → Update state: rsvp=0
Flow (A→Z):
  1. Create the “Event invitation” template with YES/NO buttons.
  2. Send SMS from Dashboard or API (with [landingurl]).
  3. User clicks the link → sees the invitation page.
  4. User taps YES/NO → your system stores the RSVP instantly.
Example B — Appointment confirmation
Buttons: CONFIRM / RESCHEDULE
Template name
Appointment confirmation
Placeholders
{name}, {date}, {time}, {service}
Landing page
Shows appointment + actions
SMS sent to: 3249XXXXXXX
Hi {name}, please confirm your {service} appointment on {date} at {time}.
Tap here: [landingurl]
CONFIRM → Update state: confirmed=1
RESCHEDULE → Open URL: your_booking_page
Flow (A→Z):
  1. Create the template with CONFIRM + RESCHEDULE.
  2. Send SMS with dynamic values filled (date/time/service).
  3. User opens landing page and taps CONFIRM.
  4. Your backend stores confirmed=1 (or triggers an API call).
  5. RESCHEDULE redirects to your booking page.
Example C — Confirm information
Buttons: CONFIRM / REPORT ISSUE
Template name
Confirm your details
Placeholders
{name}, {company}
Landing page
Displays details + confirmation
SMS sent to: 3249XXXXXXX
Hi {name}, please verify your account details for {company}.
Confirm now: [landingurl]
CONFIRM → Update state: details_ok=1
REPORT ISSUE → Open URL: support_form
Flow (A→Z):
  1. Create template with CONFIRM + REPORT ISSUE.
  2. Send SMS after signup or before important steps.
  3. User checks the page, confirms in 1 tap.
  4. Your system stores details_ok=1 for compliance and traceability.
Example D — Alert / incident notification
Buttons: ACKNOWLEDGE / OPEN STATUS
Template name
Service alert
Placeholders
{service}, {incident_id}, {eta}
Landing page
Incident summary + actions
SMS sent to: 3249XXXXXXX
⚠️ Alert: {service} incident #{incident_id}. ETA: {eta}.
Details: [landingurl]
ACKNOWLEDGE → Update state: ack=1
OPEN STATUS → Open URL: status_page
Flow (A→Z):
  1. Create “Service alert” template.
  2. When incident is created, your system sends SMS via API.
  3. User opens the landing page and taps ACKNOWLEDGE.
  4. ack=1 is stored so you know who saw the alert.
Example E — Delivery / pickup confirmation
Buttons: RECEIVED / PROBLEM
Template name
Delivery confirmation
Placeholders
{name}, {order_id}, {date}
Landing page
Order summary + actions
SMS sent to: 3249XXXXXXX
Hi {name}, your order #{order_id} was delivered on {date}.
Please confirm reception: [landingurl]
RECEIVED → Update state: received=1
PROBLEM → Open URL: support_ticket
Flow (A→Z):
  1. Create “Delivery confirmation” template.
  2. Send SMS automatically after delivery.
  3. User confirms with one tap → your system stores received=1.
  4. If issue, redirect to support ticket immediately.

Why use Enriched SMS with SMSMobileAPI?

Transform simple SMS into interactive journeys

Replace limited SMS text with a mobile-friendly landing page generated from your template and placeholders_json.

Fully personalized using dynamic placeholders

Each Landing Page Instance is uniquely generated based on your placeholders_json values.

Structured data through the responses table

Every action is stored with guid_instance, template_id and action_key — perfect for automation and analytics.

API-driven & developer friendly

Generate instance, send SMS, collect responses — simple API calls, easy integration.

Classic SMS vs Enriched SMS (with a Landing Page)

Feature Standard SMS Enriched SMS (SMSMobileAPI)
Content capacity Text only, limited length Full mobile landing page from a Landing Page Template
Personalization Minimal Complete dynamic placeholders_json mapping
Interaction No direct actions Action buttons stored via action_key and choice_label
Tracking No tracking Responses table with guid_instance and var_value
Automation Not possible API-generated Landing Page Instance

Technical overview for developers

Landing Page Instance structure

  • guid_instance
  • template_id and template_guid
  • placeholders_json
  • created_at, expires_at, last_access_at
  • phone_number and apikey
  • archived flag

Response storage model

  • guid_instance
  • template_id
  • action_key
  • var_name and var_value
  • choice_label
  • created_at

API example (automation)

✓ Generate the landing URL, inject it into your SMS, then send it to the recipient.
Generate landing URL: GET https://api.smsmobileapi.com/smslandingpage/ ?apikey=YOUR_API_KEY &template_guid=YOUR_TEMPLATE_GUID &placeholders_json={"name":"John","appointment_date":"2026-02-18"} Send SMS to the recipient: GET https://api.smsmobileapi.com/sendsms/ ?recipients=3249XXXXXXX &message=Hello John, confirm here: https://.../lp/xxxxx &apikey=YOUR_API_KEY

Start sending Enriched SMS today

With SMSMobileAPI, you can instantly turn any SMS into an Enriched SMS and a complete mobile experience powered by Landing Page Templates, dynamic placeholders and response tracking.

Go to Dashboard (Log in) Create a FREE account Create a template → send one SMS → watch responses appear automatically.
Step-by-step process How to use it Why Rich SMS works Create a new account Connect to my account
nriched SMS: fro
💬 Live Chat
💬 Live Chat Available
Have any questions or need assistance ?
Our team is here to help you!
Enter your email address
to help us follow up on your request :
Dashboard