SMS

Overview

EziLinks lets you send SMS directly from your account using your own credentials with an SMS provider (Kudosity, Twilio, ClickSend, MessageBird, or Bird). You sign up with the provider, paste your API credentials into EziLinks, and pay the provider directly at their wholesale rates. To track clicks on any links inside your SMS, create an EziLinks short link in the Links tab first, then paste the ezl.me/… URL into your message body — the recipient clicks land in your Link analytics like any other short link.

The main things you can do:

• Connect an SMS provider — bring your own credentials from Kudosity, Twilio, ClickSend, MessageBird, or Bird
• Send a single message to any contact from the SMS composer
• Send to a saved list in one go, with personalisation tokens like {{firstName}}
• Schedule a send for a later date/time in your local timezone
• Auto-send SMS on a Campaign event — when a Campaign conversion webhook (opt-in, purchase) fires with a mobile number in the payload, EziLinks can send a configured SMS to that contact automatically. Set up per Campaign in the Campaigns page.
• Manage contacts and lists — import from CSV, tag, opt-in / opt-out, segment
• Track delivery — see delivered / failed / queued status in real time via provider webhooks
• Manually opt contacts in and out from the Contacts tab — opted-out contacts are automatically excluded from all future list sends

How it works

When you click Send, EziLinks does the following behind the scenes:

1. Picks a provider — either the default provider on your account, or the one you selected on the composer
2. Sends the message body exactly as you typed it via the provider's API, using your connected credentials
3. Attaches a signed tracking token to the send so delivery reports from the provider can be matched back to the correct message row
4. Records the message in your history with a status of queued
5. Updates the status via a webhook when the provider reports back with sent, delivered, or failed

Automated SMS triggered by external webhooks (see the Campaigns feature) go through a separate flow — documented below in "Automated SMS on Campaign webhook events".

How clicks get tracked

EziLinks does not automatically shorten long URLs pasted into the SMS body. To attribute clicks back to a send, do this:

1. Create a short link in the Links tab for the destination you want to share
2. Copy the resulting ezl.me/… URL
3. Paste it into your SMS message body

When recipients click the short link it flows through the same tracking pipeline as any other EziLinks link — you see clicks, unique visitors, device/browser breakdown, and any UTM or pixel data configured on the link.

Paying for the SMS

EziLinks is BYO (Bring Your Own) provider. You pick a provider from the five supported ones (Kudosity, Twilio, ClickSend, MessageBird Legacy, or Bird Platform), sign up with them directly, and pay their per-message rates — typically 20–50% cheaper than SaaS-hosted SMS credit schemes. EziLinks never bills you for SMS traffic; only your provider does.

You can also connect multiple providers at once and pick a different one per send — useful when one is cheaper for AU/NZ and another for EU/US.

Connecting your first provider

Before you can send anything from your own account, you need to connect at least one SMS provider.

Sending a single message

The composer is the main SMS screen. Opens by default when you land on SMS.

1. Leave the Send to dropdown at "To one number (ad-hoc)" (the default)
2. Pick a saved contact from the — Pick a contact — dropdown, or use the country picker and number box alongside it for an ad-hoc send. Choose the country, type the number in local format (427 208 925), and EziLinks converts it to international format as you type — or paste a number that already starts with + and the country picker moves to match. A green tick shows the final number and whether it's a mobile or a landline; a red message tells you what's wrong if it isn't valid. Selecting a contact from the dropdown fills the number automatically; typing a different number clears the dropdown so it's obvious you're sending ad-hoc.
3. Under Send via provider, leave the default or pick a specific connected provider from the dropdown
4. Type your message. To include a trackable link, first create a short link in the Links tab, then copy the ezl.me/… URL and paste it into the body — recipient clicks will appear in that link's analytics
5. Watch the character/parts meter under the message box — each SMS "part" is 160 GSM characters (or 70 UCS-2 if you use emoji or non-Latin characters). Messages longer than one part are billed per part.
6. Click Send now

Worked pricing example

Say your provider charges $0.07 per part (roughly Kudosity's AU rate). Here's how the cost stacks up as the message gets longer:

Sending to a list

When you want to send the same SMS to a whole saved list in one go — a workshop reminder, a sale announcement, an appointment update — use the composer's list mode. This isn't a "campaign" in the marketing-automation sense; it's just a bulk send to everyone in the list.

From the composer:

1. Change the Send to dropdown from "To one number (ad-hoc)" to "To a list"
2. Give it a name in the SMS Name field — a short label so you can find this send later in History (e.g. "March newsletter" or "Workshop reminder 5 Apr")
3. Pick one or more saved lists from the multi-select (hold Cmd/Ctrl to pick more than one)
4. Write your message. Use personalisation tokens for anything that varies per contact: {{firstName}}, {{lastName}}, {{email}}, {{phone}} (plus any custom fields you imported on the contacts)
5. Optionally preview recipients — shows the count and highlights any opted-out contacts that will be skipped
6. Click Send now to fire it immediately, or use the Scheduled tab (see below) to queue it for later

Every message in the send is a separate row in your History tab, so you get per-recipient delivery reporting once the provider webhook fires the status updates.

Scheduling a list send for later

Use the Scheduled tab when you want an SMS to go to a list at a specific future date and time — a workshop reminder 24 hours before the event, an early-access announcement at 9am tomorrow, a Christmas offer on the 24th, and so on. Scheduling is list-only right now — ad-hoc single-number sends fire immediately from the Compose tab.

Step-by-step: schedule your first send

Managing scheduled sends

The Scheduled tab shows every queued send with a status column. Statuses you'll see:

• Scheduled — queued, waiting for the send time
• Sending — the scheduler picked it up and is dispatching messages
• Sent — all messages have been handed to the provider
• Cancelled — you cancelled it before it fired
• Failed — the scheduler couldn't send (usually a missing provider or list, or a provider error — check the Result column)
• Draft — saved but not yet activated (useful for prep-in-advance workflow)
• Paused — the send was mid-flight but paused (only appears for large sends caught mid-batch)

For every Scheduled send, you can:

• Edit — change the message body, target lists, provider, or send time up until it fires
• Cancel — the send won't happen; the row stays visible so you have an audit trail
• Delete — remove the row entirely

Filtering the Scheduled list

The filter bar at the top of the Scheduled tab has these fields:

• Label — contains-match on the label you gave the send
• When (range) — from/to dates on scheduled send time
• Lists — contains-match on the target list names
• Provider — contains-match on provider name (e.g. "kudosity")
• Status — dropdown of the statuses above
• Result — contains-match on the outcome text (e.g. "Sent 42/45" or a specific error)

Click Clear to reset all filters at once.

Common use cases

Automated SMS on Campaign webhook events

A Campaign SMS trigger auto-fires an SMS when an external tool (systeme.io, a payment gateway, an ecommerce platform, a CRM) POSTs to your Campaign's conversion webhook with a mobile number in the payload. This is a feature of the separate Campaigns page in the sidebar, not the SMS page. Typical use cases:

• A prospect fills in your funnel form — systeme.io POSTs the opt-in webhook — EziLinks sends a welcome SMS with a link to the first video
• A customer completes a checkout — the payment gateway POSTs the purchase webhook — EziLinks sends a thank-you SMS with a receipt link
• A booking is confirmed — the booking tool POSTs its confirmation webhook — EziLinks sends the venue address and any pre-appointment instructions

Triggers are configured per Campaign in the Campaigns page — not on the SMS page.

Setting one up

1. Go to Campaigns in the sidebar and open the Campaign you want to attach the trigger to
2. Find the conversion webhook you want to react to (e.g. opt-in, purchase). If you don't have one yet, add the webhook URL into your external tool first and wait for it to fire once so it appears in the list
3. Click + Set up SMS (or the equivalent SMS-automation control) on that webhook row
4. Give the trigger a label (for your own records, e.g. "Workshop welcome SMS")
5. Pick the SMS provider to send from
6. Optionally pick a list to add the contact to (useful when you want to run follow-up SMS sends to this same audience later)
7. Write the message body. Personalisation tokens like {{firstName}} pull from the webhook payload / newly-created contact
8. Save

Full Campaign trigger docs live under Campaigns.

Contacts and lists

Every phone number is stored in international E.164 format — prefixed with a + and a country code, like +61427208925. You don't have to type it that way: each phone field pairs a country picker with the number box, so you can enter 427 208 925 with Australia selected, or 415 555 0100 with United States selected, and EziLinks converts it. Anything you type starting with + is understood on its own and sets the country for you.

There is no assumed country. A number that isn't valid for the country you've chosen is rejected with a message saying so, rather than being quietly turned into a number that doesn't exist.

Adding a contact manually

For one-off additions, go to SMS > Contacts and click + Add contact. The form has five fields:

• Phone * — the only required field, and the only one with a country picker beside it. Pick the country and type the local number, or type a + number and the picker follows. The line underneath shows the international number you're about to save, or why it was rejected.
• First name, Last name, Email — all optional. First and last name become the {{firstName}} and {{lastName}} merge tags.
• Consent source — how this person came to be on your list. Options are Manual entry (the default), Web form, Imported list, and Opted in via reply.

The same form is reused for editing: click Edit on any contact row to change their details or correct the consent source. Each contact row carries four other actions:

• 💬 SMS — send a one-off message to just this person. Disabled once they've opted out.
• Validate — checks the number against your connected provider's lookup and reports the line type and carrier. Only shown until a contact has been validated once; needs a connected provider or it returns "Validation unavailable".
• Opt in / Opt out — flips their subscription status by hand, for when someone asks to be removed by phone or email rather than by replying STOP.
• Del — deletes the contact entirely, including their membership of every list.

Importing contacts

The fastest way is CSV paste:

1. Go to SMS > Contacts
2. Click 📄 Import CSV
3. Optionally use Add all to list (optional) to drop every imported contact straight into an existing list. Leave it blank to import them without any list membership — you can add them to lists later from the Lists tab.
4. Check Country for local-format numbers. It starts on your account default and only applies to rows written in local format; rows starting with + keep their own country regardless.
5. Paste your CSV into the CSV data textarea. First row is the header. Recognised column names: phone (required), firstName, lastName, email. Snake-case (first_name, last_name) also works. Any extra columns are stored as custom fields on the contact and become available as merge tags in the SMS body.
6. Click Import. Rows already in + format are taken as-is. Rows in local format are read against the country you picked above — so 0427208925 with Australia selected becomes +61427208925. Rows that can't be parsed, or that aren't valid for the chosen country, are skipped rather than guessed at.
7. You'll get a toast with the imported / skipped count. If anything was skipped it also names the first offending number and the reason — usually a local-format row belonging to a different country than the one selected.

phone,firstName,lastName,email
+61427208925,Jane,Doe,jane@example.com
+14155550100,Ana,Reyes,ana@example.com
0427208925,Bob,Smith,bob@example.com

Building and managing lists

A list is just a named group of contacts. Sends and scheduled sends target lists, not individual contacts, so at least one list is needed before you can send to more than one person.

Go to SMS > Lists and click + New list. A list needs a List name *; the Description is optional and for your own reference. Click Create.

Each list row then gives you four actions:

• 💬 SMS — jumps to the Compose tab with this list pre-selected. Greyed out while the list is empty.
• Members — opens the membership manager (below).
• ↓ Export CSV — downloads the list's contacts with their membership info.
• Delete — removes the list. The contacts themselves are not deleted, only their membership.

Adding and removing list members

Click Members on a list to open the Manage list window. It has two halves:

• Current members (top) — everyone currently on the list, with a Filter members… box for long lists. Each row has a Remove button that takes them off this list without deleting the contact.
• Add contacts to this list (bottom) — every contact in your account, with a Search all contacts… box. Contacts already on the list are shaded and can't be ticked. Tick as many as you want, then click Add selected.

Changes apply immediately — there is no separate save step. Click Close when you're done.

Opt-outs and STOP handling

The workflow today:

1. Log into your SMS provider's dashboard periodically (Kudosity, Twilio, etc.) — the inbound / SMS log will show any replies from your recipients
2. Find every reply containing STOP, UNSUBSCRIBE, OPT OUT, or similar
3. In EziLinks, go to SMS → Contacts, find the matching contact by phone number, and click Opt out
4. The contact is now excluded from every future list send from your account

Once inbound SMS is added to EziLinks, this will happen automatically. For now, the manual step is required to stay compliant.

Alternative: include an opt-out link in the message

Rather than relying on STOP replies (which need manual handling until inbound ships), a common workaround is to include a short link in your SMS pointing to an opt-out landing page you host yourself. When the recipient clicks it, your form submits their number back through a webhook (or you review it manually) and you mark them opted-out in EziLinks. This works around the missing inbound step entirely.

You can also manually opt a contact in or out from their contact detail page. Opted-out contacts stay in your database (you can still see their history) but are excluded from all future list sends.

Delivery reports

Every message you send flows through these statuses:

• queued — accepted by the provider, waiting to be handed to the mobile carrier
• sending — handed off, in transit
• sent — carrier has confirmed receipt (not the same as reaching the handset)
• delivered — the recipient's handset has confirmed delivery
• failed — carrier rejected or timed out (recipient handset off, invalid number, blocked, etc.)

Status updates come via webhooks from your provider. Providers vary in how quickly they report delivery — some within seconds, others up to 48 hours (especially for internationally roaming recipients).

Choosing a provider

Each provider has strengths in different regions and use cases. Here's a quick comparison:

All five providers support inbound SMS on their side, but EziLinks does not yet consume it — STOP handling is manual today, see the Opt-outs and STOP handling section above.

Rule of thumb

• Sending mostly to Australia or New Zealand → Kudosity first, ClickSend as a fallback
• Sending to USA or Canada → Twilio (mandatory 10DLC registration for US)
• Sending to UK, EU, India, SE Asia → MessageBird Legacy if you have an older account, otherwise Bird Platform API
• Sending globally and want one bill → Twilio or Bird, but expect to pay more per part

Per-provider setup guides

Click through for detailed step-by-step credentials, sender ID setup, error codes, and gotchas:

Compliance essentials

SMS is one of the most heavily regulated channels in marketing. A few essentials that apply almost everywhere:

• Consent — the recipient must have consented to receive marketing SMS from you. Consent can be express (they signed up for texts) or inferred (they're an existing customer within a reasonable timeframe). Keep records.
• Identify the sender — your sender ID or the message body must make it clear who is sending. EZILINKS as an alphanumeric sender does this well.
• Provide an opt-out — every marketing SMS must include a way to stop. Because EziLinks does not yet receive inbound SMS, you must either (a) monitor your provider's inbox for STOP replies and manually opt those contacts out inside EziLinks, or (b) include a short link in every message pointing to your own opt-out landing page.
• Send within allowed hours — most markets ban marketing SMS outside business hours (Australia: 9am-9pm local time; US: 8am-9pm; UK: 8am-9pm).
• Register your senders — many markets now require carrier pre-registration for alphanumeric senders or brand names.

What does it cost?

Two costs to think about:

• EziLinks subscription — SMS is included on the Pro Toolkit and Agency plans; not available on Free
• Per-message provider cost — paid directly to your SMS provider at their per-message rate. This varies wildly by destination country and by provider. Rule of thumb: AU messages are $0.03–$0.10 each, US is $0.008–$0.03, UK/EU is €0.02–€0.08.

Multi-part messages (over 160 GSM characters or 70 UCS-2) are billed per part. Keep messages concise to keep costs down.