Skip to content
New KiwiTxt now works with Zapier

Text your customers the moment something happens

An order ships, a booking is made, a payment fails. KiwiTxt sends the SMS automatically. No one has to remember, and your customers never wonder what is going on.

  • Sends on its own
  • Customers can reply
  • No code needed
How it works

Set it up once. It texts for you from then on.

Pick the events that matter, write what each one should say, and KiwiTxt takes it from there.

1

Something happens

An order is placed or changes status, a booking is made, a payment clears or fails, in the software you already run.

  • New order placed
  • Order marked completed
  • Payment failed
2

KiwiTxt picks the message

Each event has its own message, filled in with the customer’s name, order number, total or link.

3

Your customer gets a text

It lands on their phone within seconds. No spam folder, no app to install. If they reply, you see it.

Good news Sam, order #4821 is on its way.
Use cases

Whatever happens in your business, a text can follow

The same idea everywhere: an event happens, the right person hears about it straight away.

Every order update, straight to their phone

Order emails can land in spam or never arrive. A text goes straight to their phone. Confirm the order, say when it ships, and chase a failed payment before the sale is lost.

  • Order placedThanks for your order, with the total and order number.
  • CompletedYour order is on its way.
  • Payment failedA link to try again, sent while they still want it.
WooCommerce
Two-way

When customers reply, the conversation comes to you

Automatic doesn’t mean one-way. Replies land in your KiwiTxt inbox, where anyone on your team can pick them up and answer from a browser.

  • Every reply in one inbox

    Threads by customer, newest first, from any computer or phone.

  • Your whole team, one number

    Staff log in with their own account; customers always text the same place.

  • Send one-off texts too

    Running late? A question about an order? Type it and send.

Built to be trusted

Built for texts that have to arrive

Triggered by events

Orders, status changes, bookings and payments send on their own. Choose exactly which ones.

Your words, filled in

Write each message once with tags like {first_name} and {order_number}. A live counter shows how many SMS parts it uses.

Replies come back

Customers text back like any message, and the reply shows in your inbox.

Never sent twice

Each event texts once. Re-saving an order or a retry after a network blip won’t double up.

Any number format

Numbers typed as “021 123 4567” or “(555) 123-4567” are converted to international format automatically.

Secure by default

Keys are stored encrypted, every request is authenticated, and the API is rate-limited.

WooCommerce

Run a WooCommerce store? Texts for every order, in two minutes.

Nothing to install. Paste one link into WooCommerce’s own webhook settings and tick the order statuses you want. From then on every new order and status change texts the customer, and every send is listed in your KiwiTxt portal.

Custom webhooks

Any app that sends a webhook can text your customers

Payments, bookings, form enquiries, your own system: create a custom webhook in your portal, paste its link into the app, and choose what each event says. No code, nothing to install.

  • Paste one link

    Works with Stripe, Calendly, Typeform, Make and anything else that can send JSON or form data. Zapier users get our Zapier app.

  • Click the fields you need

    Send a test from your app and its fields appear in the portal. Pick the phone number, then drop the name or amount into your message.

  • Only when it matters, only once

    Text only when a field matches (a payment succeeded, a booking was made), and never twice for the same event.

For developers

Your own software? One API call.

Building it yourself? Send from any system that can make an HTTPS request. Replies can be posted back to your own endpoint as webhooks.

  • Bearer-token auth

    One key per workspace, rotate it any time.

  • Safe to retry

    Send an Idempotency-Key and a retried request never texts twice.

  • Webhooks with retries

    Inbound replies are delivered to your URL and retried with back-off if it’s down.

send-sms.sh
# Text a customer when something happens
curl -X POST https://www.kiwitxt.com/wp-json/kiwitxt/v1/sms \
  -H "Authorization: Bearer ktx_live_..." \
  -H "Idempotency-Key: order-4821-completed" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+64211234567",
    "message": "Good news Sam, order #4821 is on its way."
  }'

# 202 Accepted
{
  "id": 1042,
  "to": "+64211234567",
  "status": "sent",
  "segments": 1
}
FAQ

Questions, answered

Getting started

How long does it take to set up?

Most businesses are texting the same day. Sign up, connect your first app (one click for WooCommerce and Stripe), switch on the messages you want and send yourself a test. There is nothing to host and no code to write.

Do I need a developer?

No. Every message comes ready to use and you edit the wording in your portal. Developers who want to build their own thing can use the REST API instead.

Do I need to change the software I use?

No. KiwiTxt connects to what you already run: WooCommerce with our free one-click plugin, your WordPress forms with our free forms plugin, Stripe with the KiwiTxt SMS app from Stripe’s App Marketplace, PayPal with your PayPal keys, HubSpot with a workflow webhook, thousands of apps through our Zapier app, a custom webhook for any other app (Calendly, Typeform, Make and more), or our API. Your team keeps working the way they do now.

Can I connect Calendly or my booking system?

If it can send a webhook, yes. Create a custom webhook in your portal, paste its link into the app, and pick which field holds the phone number. The app has to include the customer’s phone in what it sends.

Texting and replies

Can customers reply?

Yes. Replies arrive in your KiwiTxt inbox, where you and your team read and answer them from any browser. Replies can also start an automation through Zapier, or be posted to your own system.

Can my team see each other’s conversations?

That is up to you. Admins see every conversation in the workspace and hand them out; team members with the agent role see only the conversations assigned to them, which keeps customer messages private to the person handling them.

Can I text someone by hand?

Yes. The portal is a full two-way inbox: start a conversation with any mobile number, save contacts, tag them and search your history. Automatic texts and hand-written ones sit in the same thread.

How long can a text be?

A standard SMS holds 160 characters. Longer messages are split into parts and rejoined on the phone, and emoji or special characters reduce the space per part. The message editor in your portal shows the part count as you type, so you always know what a message uses.

Will a customer get the same text twice?

No. Each event texts once. If an order is re-saved or a request is retried, KiwiTxt recognises it and doesn’t send again.

What if a text can’t be sent?

Nothing is silently dropped. Landlines and events with no phone number are skipped, and your activity log lists every event as texted, skipped or failed, with the reason, so you can fix it.

Why SMS instead of email?

Order and booking emails regularly land in spam or promotions tabs, or never arrive at all. A text goes to the phone in the customer’s pocket and is usually read within minutes.

Which countries can I text?

KiwiTxt is built for international sending, and numbers are converted to international format automatically. Sender rules differ between countries. Some require a registered number before you can send, so we confirm what applies to you before you go live.

Pricing and account

What does it cost?

One plan at $19 USD a month, plus 9c USD per SMS segment, with a 14-day free trial. Every integration, your whole team and the API are included, and texts are charged on what you send. See pricing

Am I locked into a contract?

No. It is month to month, there is no setup fee, and you can cancel any time by email, including during the trial. Team members and contacts are unlimited.

Who owns the messages and contacts?

You do. We store and process them to run the service and for nothing else. Our privacy policy sets out what we hold, who helps us deliver it, and how to ask for a copy or deletion. Read the privacy policy

What about consent and opt-outs?

Text people who are expecting to hear from you: your customers about their own order, booking or payment. You are responsible for having their consent, and for honouring a request to stop. Add opt-out wording to any message that is marketing rather than a service update.

Stop hoping they read the email.

Let your customers know the moment something happens, automatically, every time.