Email, SMS, WhatsApp, voice and push through one console and one single key. Verification, campaigns, automation and a shared inbox on top. Delivery you can actually inspect.
No password to remember. We send a code to your email.
curl https://merdotconnect.com/v1/messages \
-H "Authorization: Bearer mdc_live_..." \
-d channel=whatsapp \
-d to=+91XXXXXXXXXX \
-d template=order_shippedChange channel to reach the same person somewhere else. Nothing else about the request moves.
Every message keeps this timeline. A failure lands here as a reason, not a status code.
Email, SMS, WhatsApp, voice and push through a single endpoint and a single key. Switching channel means changing one field.
Every message quotes its cost up front, and a message we refuse costs nothing at all. No monthly minimum, no platform fee.
Consent, suppression, approved templates and quiet hours are checked before a message is charged for, not written up in a help article.
Every message keeps its full event timeline. When something fails you get the reason, not a status code.
The same request shape, the same delivery reports and the same ledger, whichever channel you pick. Swap a channel by changing one field.
Transactional and bulk, on infrastructure we own
Send receipts, alerts and campaigns from your own domain. Authentication records are generated for you, and delivery is tracked to the inbox rather than guessed at.
Transactional, promotional and OTP across every operator
Registered sender headers, template mapping and per-operator delivery reports. Quiet hours and preference rules are enforced for you, not left to your code.
Templates, two-way conversations and rich media
Business-initiated templates plus a real conversation window, with media, buttons and a shared team inbox behind it.
Calls, verification and flows people can actually hear
Voice verification, call flows, click to call and number masking, built on the same routing and reporting as every other channel.
Carrier connectivity is the dependency. Adapter and console are on the roadmap.
Browser notifications, with nobody in between
Reach people who already visit your site, straight in the browser. No carrier, no approval and no per-message cost, which makes it the cheapest channel you have and the one most businesses under-use.
Web push is live. Notifications inside a native iOS or Android app need a separate connection, which is not built yet.
No sales call before you can try it, no contract before you can send your first message, and no minimum to hold you there afterwards.
Enter your email address and we send you a six digit code. There is no password to choose, forget or leak, because we never store one.
Verify a sending domain for email, or connect your WhatsApp number. The console generates the records you need and checks them live rather than telling you to come back later.
Call one endpoint or use the composer. Every message keeps its full event timeline, so a failure comes back as a reason rather than a status code.
Wire up a single endpoint and a single key. Adding WhatsApp later means changing one field, not onboarding another vendor, another dashboard and another invoice.
When a customer answers an SMS or a WhatsApp message, it becomes a conversation your team can pick up, assign and close, rather than vanishing into a number nobody watches.
Order updates on WhatsApp, reminders by SMS, invoices by email. Same audience, same consent record, same bill, without stitching three services together.
Sending is the easy part. What you actually need is who to send to, when, what happens on a reply, and proof of what landed.
One call sends a code and one call checks it. Order the channels and it falls through automatically when a message does not land.
Bulk sends over a list or a saved segment, with throttling, scheduling and a per-recipient result you can inspect.
Draw the journey once. Triggers, waits, branches and sends, running durably so a restart never loses somebody halfway.
Replies are conversations, not dead ends. Your team answers from one place, with the reply window tracked for them.
Contacts with your own attributes and per-channel consent, so the record of who agreed to what lives with the person.
Delivery, not vanity. Rates by channel, operator and template, with failures broken out instead of averaged away.
The channels and the rules that apply to them differ by industry. The API does not.
Order confirmations, dispatch and delivery updates on WhatsApp, abandoned-cart nudges by email, and one-time codes at checkout.
Transaction alerts and one-time codes that have to arrive, with failover to a second channel when the first does not deliver.
Appointment reminders and report-ready notices, with consent recorded per person and per channel rather than assumed.
Fee reminders, attendance notices and result announcements to parents, sent as a campaign over a saved segment.
Pickup, in-transit and delivery events fired straight from your system, with the rider's reply landing in a shared inbox.
Sign-in codes, billing notices and product announcements from one key, so adding a channel is a config change rather than a project.
Your team does not live in the API. The console carries the same capability: compose and send, build a journey, work the inbox, read the ledger and check a single message end to end.
One endpoint, one key, one response shape. Errors carry a stable code you can branch on instead of a string that changes when we reword it.
"color:#5ce0b0">curl https://api.merdotconnect.com/v1/messages \
"color:#c98cff">-H "Authorization: Bearer mdc_live_..." \
"color:#c98cff">-H "Content-Type: application/json" \
"color:#c98cff">-d '{
"channel": "email",
"to": "[email protected]",
"from": "[email protected]",
"subject": "Your invoice is ready",
"html": "<p>Invoice 4192 is attached.</p>"
}'Signed webhooks work today, in both directions, which is enough to wire up anything that can make an HTTP request. The named connectors below are being built on top of them.
Forms, orders and customer records from your own site
Order, fulfilment and refund events
Contact forms and store events
Import a list, or write results back to a sheet
Reach the tools we have not built for yet
Signed callbacks into any endpoint you own
Most platforms resell somebody else's email and mark it up. Ours runs on servers we operate in India, which is why the price is lower and the delivery data is real rather than relayed.
Registered templates, quiet hours, preference rules, consent and suppression are checked before a message is charged for, not left as a warning in a help article you were meant to read.
Every message quotes its cost up front and every rupee moves through a ledger you can read. No monthly minimum, no platform fee, no rounding in our favour.
Messages, contacts and delivery records sit on infrastructure we operate here, not in somebody else's region.
Signing keys and channel tokens are encrypted at rest with a key that never leaves the server, and are never shown again after you paste them.
Sign-in is a code sent to your address. There is no password database on this platform, because there are no passwords.
Opt-in and opt-out are stored per person, per channel, with a timestamp, so you can show how somebody agreed rather than assert it.
A bounced or unsubscribed address is checked before a message is priced. Refusing to send costs you nothing.
Every webhook carries a signature and a timestamp, so your endpoint can prove the call actually came from us.
Prepaid credit, per message, quoted before it sends. No monthly minimum and no platform fee. A message we suppress or reject never costs you anything.
Per-channel rates are set once carrier and platform agreements are signed, so the number you see is the number you pay. We would rather publish nothing than publish a price we have to walk back.
Create an account
Something not covered here? Write to [email protected] and a person will answer.
Email, WhatsApp and SMS are all live and sending today. Push is live too, straight from the browser, no carrier or approval needed. Voice is built into the console but has no carrier behind it yet, and every screen says so rather than pretending otherwise.
No. You add credit and each message draws down against it at a price quoted before it sends. If we suppress or refuse a message it costs nothing at all.
Because a password is a thing to steal. Signing in sends a code to your email address, which is the same thing a password reset would do anyway, with one fewer secret to keep.
You connect your own, through the standard sign-up flow inside the console. Your number, your quality rating and your templates stay yours, and you can take them elsewhere.
Yes, and for email you should. The console gives you the authentication records to publish and then checks them live, so you can see the moment the domain is genuinely ready rather than guessing.
It keeps its whole event timeline and the failure reason is stored with it. Hard failures add the address to your suppression list automatically so you do not pay to send at it again.
Yes. Test keys run the whole path, including compliance checks and webhooks, without touching a carrier or your balance.
Merdot, the same team behind Merdot Mail, Merdot Sites, Merdot Studio and Merdot AI. Email runs on infrastructure we already operate for those products, which is why we can price it the way we do.
Enter your email, take the code, and you are in the console. That is the whole sign-up.
Get started