Sent - Unified Messaging API for SMS, WhatsApp & RCS
One API. Every channel.
sent.message("Your code is 4291");
Send SMS, WhatsApp, and RCS from a single integration. Sent handles routing, compliance, and content transformation so you ship faster.
$npm install @sentdm/sentdm
sent.message("Your code is 4291");
Infrastructure, not just an API.
Replace provider fragmentation with a single integration layer.
Abstraction Layer
Your app calls Sent. Sent handles providers, carriers, and per-channel quirks.
DELIVERY PATH (CONTACT)
![]()
Daniel A.+1 (914) 1...
Verified
![]()
WhatsApp
Message Lifecycle Visibility
Track every message you send, from request to confirmed delivery.
![]()
Received
![]()
Queued
![]()
Sent
![]()
Delivered
ID: msg_827391...
Delivered
Provider responded 200 OK
08:21:14
Fallback not required (WA active)
08:21:15
User read message
08:22:29
The problem with legacy messaging
You want to ship features. Instead, you're managing pipes.
Fragmented Providers
Separate APIs for each aggregator, channel, and carrier. More integrations, more maintenance.
Compliance Overhead
10DLC, WhatsApp templates, opt-out rules—each channel has its own requirements.
Content Transformation
Rich media on WhatsApp, plain text fallback on SMS. You build the logic.
Cost Inefficiency
Without channel-aware routing, you default to SMS rates for every message.
How it works
Routing and delivery, handled for you.
Contact Object
Each user is stored as a delivery profile with channel preferences and availability.
![]()
Daniel A.+1 (914) 123...
Preferences
Last contacted via WhatsApp · 2 days ago
Channel Availability Check
Sent detects which channels can reach each contact before sending.
Channel Scan: +1 (914) 123-0001
WhatsApp
Active
SMS
Available
RCS
N/A
Direct delivery supported
Unified Templates
Define one message. Sent transforms it for each channel automatically.
Hi {{name}},
your order {{order_id}}
is ready for pickup.
![]()
Hi Jane, your order #9921 is ready...
![]()
Sent: Hi Jane, your order #9921 is ready for pickup.
![]()
Automatic Fallbacks
When delivery fails, Sent routes to the next available channel. No extra code.
WhatsApp delivery failed (timeout 3s)
System ActionFallback triggered: sending SMS copy...
Template Rendering
One template fans out into channel-specific payloads.
Compliance, handled.
Sent is a registered carrier with direct interconnects. Regulatory requirements are built in.
Certifications & Memberships
NECA OCN126L
FCC RegistrationRegistered
IPESRegistered IPES Provider
SecuritySOC 2 Type II
GDPRCompliant
Lower messaging costs
Channel-aware routing sends messages via the most cost-effective available channel. Typical savings: 30–60%.
Global reach
Send to recipients worldwide. Sent handles local carrier requirements and regulatory headers.
Ship faster
One integration replaces six. Spend time on your product, not messaging plumbing.
Pricing
Pay as you go
$0.015/ contact / month
Monthly per-contact pricing. Carrier fees passed through at cost.
Start building