Use case
Have a conversation, not just a broadcast.
Receive replies, thread them, and respond — all over the same API.
Why teams switch
- Customers reply to SMS and those replies vanish into a phone nobody checks.
- Support and CRM tools need inbound messages in real time.
How SMSKit fits
Inbound SMS are threaded into conversations, available via the inbox, polling (since cursor), and the sms:received webhook. Auto-route replies back through the right device. STOP/opt-out handling built in.
Acme Support
+254 712 345 678
Example python
# Receive inbound SMS at your webhook
# POST from SMSKit -> your endpoint, event: "sms:received"
# { "event": "sms:received", "from": "+254712345678", "to": "+254700000000", "content": "YES" }