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
Delivery operations

Operational messaging for the team, not just the customer

The same API that reaches customers reaches your own operation: drivers get route changes, on-call staff get exception pages, shift leads get the morning manifest. Internal operational messaging is often the fastest win — no consent complexity, immediate value.

Try the interactive demo

The communication problems

  • Route changes reaching drivers after they've left
  • Exception handling that depends on someone watching a dashboard
  • Shift and manifest updates buried in group chats
  • On-call paging through consumer apps with no audit trail

Recommended workflows

Driver notifications
Route assignments and changes straight from dispatch.
Exception paging
Failed deliveries and SLA breaches page the right person.
Shift alerts
Manifests and schedule changes to the right crew.
System alerts
Pipeline failures and backlog warnings to on-call staff.
Route B-12 updated: 3 stops added after Cherry St.EXCEPTION: stop 14 failed — customer unreachable. Call dispatch.Tomorrow's manifest is ready: 47 stops, van 3.

Architecture

How it fits together: Ops systems, then Event rules, then SendiMessage API, then Team member, then Ops record.
  1. Ops systemsDispatch, monitoring, scheduling
  2. Event rulesWhat pages, what informs, what waits
  3. SendiMessage APIPOST /send-message to staff numbers
  4. Team memberNotification + acknowledgement reply
  5. Ops recordAcknowledgements tracked via webhook

The API request

send message
curl -sS https://api.sendimessage.com/v1/send-message \
  -H "X-API-Key: $SENDIMESSAGE_KEY" \
  -H "X-API-Secret: $SENDIMESSAGE_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "number": "+15555550123",
    "content": "EXCEPTION: stop 14 failed - customer unreachable. Reply ACK.",
    "status_callback": "https://your-endpoint.example.com/status?route=B-12&stop=14&severity=warning"
  }'
# → {
#   "status": "QUEUED",
#   "message_handle": "4e828182-a640-483f-bfe9-17ffcaa51d48",
#   "to": "+14155550123",
#   "service": null,
#   "is_outbound": true,
#   "error_message": null,
#   "date_sent": null
# }

Channel behavior and replies

Internal messaging usually standardizes on SMS for uniform delivery across staff devices. iMessage delivery is available on supported messaging lines and destinations. Recipients without iMessage receive SMS when fallback is configured — never assume universal iMessage availability.

ACK replies close the loop: the webhook records who acknowledged which exception and when — an audit trail consumer chat apps can't give you.

Line setup, availability, and pricing

One internal operations line, separate from customer-facing lines.

Line availability varies by country and channel. Run a preliminary availability check, and the team confirms final availability during onboarding review. Check preliminary availability →

Pricing is per active line, billed monthly, with usage per your agreement — confirmed for your countries and volume during managed onboarding. How pricing works →

Frequently asked questions

Is staff messaging simpler to onboard?
Usually — internal operational messaging to your own team has a straightforward consent model, making it a common first workflow before customer messaging.
Can alerts page based on severity?
Your rules decide what sends: the API is the same; severity logic lives in your event handler or monitoring stack.

Ready to build this?

Request the setup, or book an integration review and the team will map it to your systems.

Book an Integration Review