Merdot Connect
Email is live. SMS and WhatsApp are in certification.

One API for every way you reach someone

Email, SMS, WhatsApp, voice and RCS through a single console and a single key. Verification, campaigns and automation on top. Delivery you can see, priced in paise.

No password to remember. We send a code to your email.

A team at work in a modern office
Live
Email
In certification
SMS
In certification
WhatsApp
In build
Voice
In build
RCS
5
Channels, one API
1
Console for the whole team
Paise
The unit we bill in
India
Where your data sits
Channels

Five ways in. One way to work.

The same request shape, the same delivery reports and the same ledger, whichever channel you pick. Swap a channel by changing one field.

Email

Transactional and bulk, on infrastructure we own

Live

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.

  • Your own sending domain, verified end to end
  • Authentication records generated and checked live
  • Opens, clicks, bounces and complaints
  • Suppression handled before you are charged
  • Templates with variables, previewed before send

SMS

Transactional, promotional and OTP across every operator

In certification

Registered sender headers, template mapping and per-operator delivery reports. Quiet hours and preference rules are enforced for you, not left to your code.

  • Registered headers and templates, managed in the console
  • Operator-level delivery reports
  • Quiet hours and preference rules enforced automatically
  • Unicode and long-message handling done properly
  • Per-operator routing with failover

Telecom registration is filed and awaiting approval. The platform side is ready.

WhatsApp

Templates, two-way conversations and rich media

In certification

Business-initiated templates plus a real conversation window, with media, buttons and a shared team inbox behind it.

  • Template manager with live approval state
  • The 24-hour conversation window, tracked for you
  • Media, buttons and list messages
  • Inbound replies land in a shared inbox
  • Opt-in and opt-out rules per number

Business verification is complete. A registered number and partner status are the remaining steps.

Voice

Calls, verification and flows people can actually hear

In build

Voice verification, call flows, click to call and number masking, built on the same routing and reporting as every other channel.

  • Voice verification as an OTP fallback
  • Visual call flows
  • Click to call and number masking
  • Recording with consent handling
  • Per-minute reporting in the same ledger

Carrier connectivity is the dependency. Adapter and console are on the roadmap.

RCS

Branded, verified rich messaging on Android

In build

Your logo, your name and rich cards inside the default messaging app, with the same templates and reporting as the rest of the platform.

  • Verified sender with your brand
  • Rich cards, carousels and suggested replies
  • Read receipts and typing indicators
  • Automatic fallback to SMS
  • One template set across both

Depends on verified-sender registration, which follows the SMS route.

Who it is for

Built for the whole team

For engineering

One integration, not five

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.

  • Idempotency and retries
  • Signed webhooks
  • A test mode that truly costs nothing
For support

Every reply in one place

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.

  • Shared team inbox
  • Assignment and notes
  • Full history per contact
For business

Reach people where they read

Order updates on WhatsApp, reminders by SMS, invoices by email. Same audience, same consent record, same bill, without stitching three services together.

  • No monthly minimum
  • Prepaid, per message
  • GST invoices
Platform

Everything around the send

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.

Verification

One call sends a code and one call checks it. Order the channels and it falls through automatically when a message does not land.

  • Channel failover
  • Attempt limits
  • Codes never stored in the clear

Campaigns

Bulk sends over a list or a saved segment, with throttling, scheduling and a per-recipient result you can inspect.

  • Segments at send time
  • Rate shaping
  • Per-recipient outcome

Automation

Draw the journey once. Triggers, waits, branches and sends, running durably so a restart never loses somebody halfway.

  • Visual builder
  • Durable runs
  • Split testing

Shared inbox

Replies are conversations, not dead ends. Your team answers from one place, with the reply window tracked for them.

  • Agent assignment
  • Canned replies
  • Window countdown

Audiences

Contacts with your own attributes and per-channel consent, so the record of who agreed to what lives with the person.

  • Custom attributes
  • Consent proof
  • Import and sync

Analytics

Delivery, not vanity. Rates by channel, operator and template, with failures broken out instead of averaged away.

  • Per-operator breakdown
  • Failure reasons
  • Exports
Developers

Boring on purpose

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.

  • Idempotency keys
    Retry a request without sending twice.
  • Signed webhooks
    Every callback carries a signature and a timestamp.
  • Live delivery log
    Search every message and read its whole timeline.
  • A real test mode
    Test keys never touch a carrier or your wallet.
"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>"
  }'
We own the pipe

Email runs on our own infrastructure

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.

Compliance is built in

The rules are enforced, not documented

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.

No mystery pricing

You see the price before you send

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.

Pricing

Pay for what leaves

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.

Rate card in progress

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
A team reviewing delivery analytics together

Send your first message

Enter your email, take the code, and you are in the console. That is the whole sign-up.

Get started