Skip to main content

SMS Review Requests – Create & Use Custom Templates for Recurring Messages

Create, manage, and assign custom SMS templates for automated review requests, including support for personalized text and dynamic image URLs.

Updated over 2 months ago

Who This Is For / When to Use

  • Account owners managing automated review collection.

  • Teams who want more control over SMS tone, branding, and follow-up behavior.

  • Businesses using recurring SMS review requests after check-in or service completion.

Accessing SMS Review Requests Settings

Navigate to:

Reputation → Settings → SMS Requests

This page controls when SMS review requests send, how often they retry, and which templates are used.

Configure When SMS Review Requests Are Sent

Use the SMS Review Requests panel to define timing and retry behavior.

You can configure:

  • When to send SMS after check-in (for example, Immediately).

  • Repeat behavior until the review link is clicked.

  • Maximum retries allowed per contact.

These settings apply to all recurring SMS review requests for the account.

Create a New SMS Template

From Manage Your SMS Templates, click Create New.

You can choose one of two options:

  • Create New from Scratch

  • Select from Pre-Built Templates

Use Pre-Built SMS Templates

When selecting Pre-Built Templates, you can browse Kyrios-provided examples designed for review requests and follow-ups.

Templates support:

  • Merge fields (for example, {{contact.first_name}})

  • Location personalization

  • Automatic review link insertion

Assign Templates to Recurring SMS Sends

Click Set SMS Templates to assign which template is used for:

  • Live (first send)

  • Retry 1, Retry 2, Retry 3, and additional retries

Each retry can use a different template or be left unassigned.

Build or Edit an SMS Template

The SMS Template Builder allows full customization of each message.

You can:

  • Set a Template Name

  • Enable or disable Request with Image

  • Upload an image or provide a Custom Image URL

  • Write the SMS message content with merge fields

  • Preview the final SMS before saving

Dynamic image URLs support personalization using merge fields.

Dynamic Image Support (Image URLs)

SMS templates support dynamic images using image URLs.

This allows you to:

  • Use personalized images per contact

  • Insert merge fields into image URLs

  • Use third-party dynamic image services (for example, NiftyImages)

Important notes:

  • Images are sent via URL, not as static attachments.

  • Merge fields in image URLs resolve at send time.

What You Can Do With SMS Templates

  • Create branded, reusable SMS review templates.

  • Personalize messages using contact and location data.

  • Assign different messaging for initial requests and follow-ups.

  • Preview SMS messages before they are sent.

  • Improve review completion rates with tailored follow-ups.

Common Issues and Fixes

SMS is sending but image does not appear

  • Confirm the image URL is publicly accessible.

  • Ensure merge fields used in the URL are valid.

Retries are not sending

  • Check that Maximum retries is greater than zero.

  • Confirm templates are assigned to each retry slot.

Merge fields are not populating

  • Verify the contact record contains the required data.

  • Confirm merge field syntax is correct (double curly braces).

FAQ

Can I use different SMS templates for each retry?

Yes. Each retry (Retry 1, Retry 2, etc.) can be assigned a different SMS template.

Are images required for SMS review requests?

No. Images are optional and controlled per template using the Request with Image toggle.

Can I use merge fields in both text and images?

Yes. Merge fields are supported in SMS message text and in image URLs.

Do SMS templates apply to email or WhatsApp requests?

No. SMS templates are used only for SMS review requests. Email and WhatsApp requests have separate template settings.

Where do review links come from?

Review links are automatically generated by Kyrios and inserted using the {{reputation.review_link}} merge field.

Did this answer your question?