Save marketing-ready SMS copy (and optional MMS assets) once, then reuse it in broadcasts and automations without retyping. SMS messages live under Messages → SMS Messages (/marketing-messages).
Why Save SMS Templates?
- Keep messaging on-brand: edited templates automatically update every automation step that references them (
send_marketing_messageaction). - Track character counts: LaunchSMS stores the calculated segment count so you know how many 160-character segments a send will consume.
- Attach MMS assets one time: uploads land in
storage/marketing-messagesand are pulled automatically when you reuse the template. - Generate copy with Nexus AI to jump-start campaigns.
Builder Layout
- Creation Form
- Message name (optional) helps you identify the template later.
- SMS body – required, max 1,600 characters. Live counters show characters + segments.
- SMS image – optional image upload (up to 5MB).
- Nexus AI modal – click “Use Nexus AI” to enter a prompt. The modal dispatches a Nexus AI request and returns suggested copy you can insert directly.
- Save posts to
marketing_messageswithsegment_count = ceil(length/160)so downstream reporting knows how many segments will bill.
- Saved Messages Table
- Shows title, truncated copy, segment count, image preview, last update, and edit/delete actions.
- Edits go through the same form. Deleting removes the optional image from storage and the DB row.
Using Templates in Automations & Broadcasts
- In the automation builder choose Send a Template SMS Message. The dropdown lists every saved marketing message for your company.
- When the step runs, the template text/image, resolves merge tags, and sends via Twilio. If the template is missing, the step fails with a descriptive error so you can fix the automation.
- Broadcasting tools (outside this excerpt) reuse the same
marketing_messagestable—one template fuels outbound campaigns and triggered follow-ups.
Data Model
| Column | Purpose |
|---|---|
user_id |
Company owner of the template. |
title |
Optional display name. Defaults to “Untitled” in the UI if blank. |
body |
SMS content (max 1,600 chars). |
image_path |
Optional path under the public disk. |
segment_count |
Cached segment calculation to display in UI and analytics. |
| Timestamps | Determine “Updated” column and let automations know when a template changed. |
Nexus AI Assistant
- Triggered via the modal’s “Generate with Nexus AI” button.
- On success, inserts the generated copy into the modal’s textarea so you can apply it to the main form.
- Error handling covers missing prompts, missing API keys, HTTP failures, and blank responses.
Best Practices
- Label clearly – include audience + intent (e.g., “HVAC Spring Tune-Up Reminder”) to avoid confusion when selecting templates in automations.
- Watch character count – once you cross 160 characters the segment count increases. Trim copy or split long flows to keep costs predictable.
- Test MMS assets – thumbnails in the table confirm upload success. Click the image to open it and verify cropping before sending.
- Reuse AI outputs wisely – treat Nexus AI as a draft. Edit for compliance (TCPA, opt-out language) before saving.
- Keep a cleanup cadence – delete outdated promotions so teams don’t accidentally reuse expired offers in automations.
- Remember merge tags – templates can include the same
@{{ }}tokens available in automations. Validate that every tag is supported by the trigger payload before launching.
With this workflow, marketing teams create SMS content once, let AI fill in blanks when needed, and hand automations/broadcasts a reliable library to pull from.