Enrich Your SMS With Personalized Landing Pages

What Does “SMS + Landing Page” Mean?

SMSMobileAPI allows you to enrich any SMS by linking it to a customizable landing page generated automatically through a Landing Page Template.
Each message can include a short link that opens a dynamic page containing personalized information, action buttons and interactive elements.

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
• A detailed data model that stores each user interaction in the responses table

How the SMS + Landing Page Feature Works

1. Create Your Landing Page Template

Inside SMSMobileAPI, you start by creating a Landing Page Template. This includes:

• Title of the page
• Main content and static information
• Color scheme and layout
• Defined placeholders such as {invoice_number} or {amount_due}
• Custom action buttons pointing to URLs, documents or payment workflows

Once saved, SMSMobileAPI generates a unique Template GUID that you will use in your API calls.

2. Generate a Landing Page Instance via API

When sending an SMS, your system calls SMSMobileAPI with:

• The Template GUID
• Dynamic values sent through placeholders_json
• The target phone number

SMSMobileAPI builds a unique Landing Page Instance identified by a guid_instance. This instance contains all generated content, the template_id, and all placeholder values.

3. Send an SMS Containing the Landing Page Link

After the Landing Page Instance is created, the API returns a short link. You simply insert this link inside your SMS body:

“Hi John, your invoice {invoice_number} is available here: <short link>”

The recipient opens the link and sees the personalized landing page generated for their guid_instance.

4. Track All User Interactions in the Responses Table

Any interaction with the landing page — clicking a button, confirming a choice, submitting a value — is recorded automatically inside the responses table.

Each response stores:

• guid_instance
• template_id
• action_key of the pressed button
• var_name and var_value
• choice_label (user-facing label)
• created_at timestamp

This structured format allows direct integration with your CRM, ERP or automation scripts.

Why Use SMS + Landing Page with SMSMobileAPI?

Classic SMS vs SMS Enriched With a Landing Page

Use Cases Powered by SMSMobileAPI

Invoices & Payment Information

Display invoice details using a Landing Page Template containing placeholders such as {invoice_number}, {amount}, and {due_date}.

Appointment Confirmation

A Landing Page Instance can include buttons like “Confirm”, “Cancel” or “Reschedule”, all tracked through the responses table.

Order Information & Status Updates

Provide real-time updates and clickable actions in a structured mobile page instead of long SMS text.

Technical Overview for Developers

Landing Page Instance Structure

Each generated instance stores:

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

Response Storage Model

User interactions are saved using:

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

Start Enriching Your SMS Today

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