Campaigns & collections

Reach the whole list. Know what happened to every single person. 

Send an approved WhatsApp template, or set an AI agent calling each person for a real conversation. Either way you get an outcome per recipient — and a platform that refuses to send the things you shouldn't.

50,000

recipients per campaign

300

AI calls per day

23

documented refusal reasons

1 + 2

reminder, then two follow-ups

WhatsApp broadcast

One approved template, personalised for thousands.

Pick a template Meta has approved, map your values into it, and send. Each message is personalised per recipient, and each one reports back — delivered, read, held for a reason, or failed and retryable.

  • Personalisation tokens like the customer's own name and order
  • A missing value skips that person rather than sending a sentence with a hole in it
  • Delivery and read rates, grouped failures, and CSV export
  • Pause mid-flight and resume without anyone getting it twice
Festive offer · template0 / 4,812
Anita R.Read
Vikram S.Delivered
Meera J.Not sent · opted out
Rahul K.Delivered
Sana P.Failed · retryable
AI call batches

It calls all of them, and actually talks.

Not a recorded message. The agent rings each person, introduces your business, says it's a virtual assistant, and holds a conversation — answering questions from your knowledge base and opening a ticket if they want a person.

  • Answer rates, talk time and attempt counts per recipient
  • Callers who say 'not now' can pick a time — and the agent books it
  • Unanswered calls get exactly one automatic retry inside your window
  • Calling hours enforced: 10:00 to 19:00, never a 9 p.m. dial

Whether a given number should be called is your decision — the platform enforces the operational guards, not your do-not-call policy.

Renewal batch · 1,240 contactsCalling…
Renewed on the call
Asked for a call back Friday 4 PM
No answer · one retry scheduled
Audiences

Your list, cleaned before it costs you anything.

Pick contacts, select tags, or upload a CSV — parsed on the server, with phone, name and email columns detected for you. Then everything unsendable is stripped out and you confirm the real number before a single message leaves.

  • Up to 50,000 recipients in one campaign
  • Tags match on all-must-match, so a broad selection can't surprise you
  • Numbers normalised to E.164 — ambiguous ones are rejected, never guessed
  • Invalid numbers, duplicates and opt-outs removed before launch
contactstagsCSV upload
Uploaded rows5,400
Invalid numbers removed−188
Duplicates merged−241
Opted out−159
Will receive4,812

The count you confirm is the count that sends.

Sending rules

The rules that stop you becoming the reason people block you.

Every campaign runs through the same gate, and the gate refuses rather than half-sending. If something blocks a launch you're told exactly what and how to fix it.

  • Opt-outs removed at build time and re-checked immediately before each send
  • One message per person per day, four per rolling week across all campaigns
  • Quiet hours: messages 09:00–21:00, calls 10:00–19:00, queued not dropped
  • You state the lawful basis before launch, and it's recorded against your name

A customer who sends STOP to one of your numbers is suppressed on all of them, across every campaign, automatically.

Opted out — never sent
Already had 4 this week — held
It's 21:40 — queued for 09:00
Missing {{name}} — skipped, not sent blank
Lawful basis attested — logged

23 documented refusal reasons. None of them silent.

After it sends

You'll know what happened to all 4,812 of them.

Not an aggregate percentage — a row per person, with the reason.

Outcome for every recipient

Delivered, read, not sent with the reason, or failed — searchable, filterable, exportable to CSV.

Retry only what's worth retrying

Requeues genuine provider errors. Never re-attempts someone excluded by a rule.

Frozen after launch

Name, audience, message and consent record can't be edited once sending starts. Only the schedule moves.

A consent audit trail

Who attested, when, to how many people, with a checksum of the exact list. Provable months later.

Duesly — an app inside Campaigns

Get paid on time, without becoming the person who nags.

Add a customer, an amount and a cycle. Duesly raises each due date, sends the reminder on WhatsApp with a payment link, and stops after two follow-ups — because a third one costs you the customer, not the invoice.

  • Weekly, monthly, quarterly, half-yearly, yearly or a custom interval — month-ends handled correctly
  • Razorpay links that close themselves the moment they're paid, cancelling the remaining follow-ups
  • Or plain UPI and a QR code, if you have no gateway at all
  • Partial payments, waivers with a reason, and a dashboard of what's outstanding
Payment links UPI / QR Payments API Webhooks on paid

One reminder, at most two follow-ups, one a day. There is no setting, plan or API call that raises it — that ceiling is the point of the product.

Sunrise Tuition · Sept cycle42 customers · ₹1,00,800 due
₹2,400 due today · monthly planReminder
Razorpay link sent — one tapLink
Paid ₹2,400 · UTR 4471902Settled
Follow-ups cancelled automaticallyDone

Send your first campaign this week.

Connect a WhatsApp number, upload a list, and watch every outcome land — on the free plan, before you pay anything.