We use optional, privacy-safe analytics to understand which pages help visitors. Nothing optional runs until you choose. Privacy policy

Skip to content
SendiMessage
Start Pilot
Use case

Add iMessage and SMS customer support to your platform

Keep people posted as their request moves forward.

Support platformPOST /send-messageSendiMessageCustomerReplyreceive webhookSupport conversation

The business problem

Customers chase updates when they're left in the dark.

Integration workflow

  1. A ticket status changes
  2. Your helpdesk calls the API
  3. Customer is notified
  4. Replies route back via webhook

Recommended line setup

One support line per brand.

example message“Your support request has been updated.”
POST https://api.sendimessage.com/v1/send-message
bash
curl -X POST "https://api.sendimessage.com/v1/send-message" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $SENDIMESSAGE_API_KEY" \
  -H "X-API-Secret: $SENDIMESSAGE_API_SECRET" \
  -d '{"number":"+15551234567","content":"Your support request has been updated.","line_handle":"8eb3ecaf-6487-485d-b01c-b18bdcb57180"}'
201 Created (real response shape)
json
{
  "status": "QUEUED",
  "message_handle": "4e828182-a640-483f-bfe9-17ffcaa51d48",
  "from": "+15555550100",
  "to": "+14155550123",
  "group_id": null,
  "content": "Your support request has been updated.",
  "media_url": null,
  "service": null,
  "is_outbound": true,
  "error_message": null,
  "date_created": "2026-08-21T09:07:34+00:00",
  "date_updated": "2026-08-21T09:07:34+00:00",
  "date_sent": null
}

Why a managed line instead of running this yourself

A support conversation isn't a single message — it's an outbound update, a reply, sometimes several rounds back and forth, and it has to land in the right ticket every time. SendiMessage operates the line and does the messaging plumbing: replies are threaded into conversations instead of arriving as disconnected texts, delivery events tell you whether an update actually reached the customer, and — where SMS fallback is configured — a customer without iMessage still gets the update. Your support platform keeps owning the ticket; SendiMessage is the transport underneath it.

Frequently asked

Does this integrate natively with Zendesk, Intercom, or our helpdesk?

Not as a marketplace app today — the integration is a standard webhook-and-API pattern: your helpdesk's automation calls POST /send-message, and SendiMessage's receive webhook delivers replies back to your handler, which writes them into the ticket. Dedicated Zendesk and Intercom implementation guides cover the exact trigger mechanics for each platform.

How are a customer's replies grouped?

By conversation — one thread per line and counterpart. Your handler reads the thread (or just the latest reply) and appends it to the correct ticket, matched by the customer's number.

What if the customer doesn't have iMessage?

Where SMS fallback is configured on the line, the update is delivered as SMS instead, automatically. The channel actually used is recorded on the message, never assumed.

How do we know an update actually reached the customer?

Every outbound message has a status history — queued, sent, delivered, or error — available over the API and pushed to your webhook endpoint, so a failed delivery is visible instead of silent.

Ready to set this up?