Do I need to write code to send SMS from my ERP?

Not necessarily. You can call the REST API directly, or point an existing ERP workflow or webhook at a no-code ingress URL that maps your fields to a message.

Which ERP systems work with it?

Any ERP that can make an outbound HTTP request or fire a workflow webhook can send messages — the gateway speaks plain REST, so it is not tied to a specific vendor.

Can the ERP receive delivery status and replies?

Yes. Each send returns a message ID for delivery tracking, and inbound replies are pushed back to your system as HMAC-signed webhooks.

SMS For ERP

Send SMS from your ERP via REST API

Your ERP already knows when an order ships, an invoice is due, or a delivery is on its way. A self-hosted gateway lets it text the customer about it — one REST call, sent from your own SIM and number, with replies pushed straight back.

Your ERP already has the trigger

Every meaningful customer event lives in your ERP: a sales order is confirmed, stock is dispatched, a payment clears, a service is scheduled. The hard part was never knowing when to message someone — it was getting the message out without bolting on an expensive messaging contract. A gateway you host closes that gap. When the event fires, your ERP posts the recipient and the text, and the paired phone sends it within seconds.

One REST call, or no code at all

If your ERP can make an outbound HTTP request, sending is a single authenticated POST — recipient and message body, nothing more. If you would rather not touch code, point an existing ERP workflow or notification webhook at a no-code ingress URL instead. The ingress maps the fields your ERP already sends into a ready-to-deliver message, so business users can wire up alerts without a developer. Either way, the full request and response shapes are documented in the REST API reference.

What teams send from the ERP

Order & dispatch alerts — confirmations, packing and shipped notifications with tracking details.
Invoice & payment reminders — due-date nudges and receipt confirmations from your accounting module.
Delivery windows — "out for delivery today" and reschedule prompts from logistics.
Service & appointment reminders — automatic prompts that cut no-shows.

Replies come back into your workflow

Outbound alone is half a channel. When a customer answers — "yes, reschedule" or "wrong address" — that reply is captured and pushed to your endpoint as an HMAC-signed webhook, so your ERP, CRM or helpdesk can act on it automatically. See the inbound webhook guide for the payload shape and signature check.

Why self-hosted

Because messages go out through your own SIM, you keep your number, avoid per-message aggregator markup, and never share a shortcode with strangers. The gateway runs on hardware you control, and API keys issued at pairing can be rotated whenever you need. To connect your first workflow, start with the quickstart.

Scan to install

Wire your ERP to SMS in five minutes

Install the Android app, pair your phone, grab your API key, and fire your first alert.

Read the quickstart → Get it on Google Play

Automated SMS notifications · Two-way SMS for your CRM · Android SMS gateway · REST API reference