Duesly

Duesly is for a business with customers who pay it on a cycle and who currently chases them by hand. Veloria Home uses it for customers who pay their annual maintenance contract in monthly or quarterly instalments.

You add each customer once: name, WhatsApp number, amount and how often. Duesly raises each payment when the cycle comes around, reminds the customer on WhatsApp, follows up if it isn't paid, and stops asking after two follow-ups.

It's an app inside Campaigns, so it needs the Growth or Enterprise plan, and every message it sends obeys your sending rules. Setting it up and every action in it are for admins; members can read it.

Setting it up #

The four tabs #

The header shows Duesly's state: Collecting, Setup needed or Paused, with Pause reminders (or Resume) beside it.

Today #

• Collection snapshot: Outstanding (still expected), Overdue (need a decision), Due this week, and Collected this month. The line above it gives the number of active customers and their monthly value.
• Needs your attention lists overdue payments with Record paid, and Send follow-up (or Send reminder) while the chase allows another message.
• Coming up lists the next payments and what will happen next.
• The card at the bottom shows the collection mode, with Change collection settings.

Adding a customer #

Customers → Add customer:

Every customer you add also becomes a contact, so their conversations sit in one place. If that link fails, the customer is still saved and reminders still go out; the row says Not linked to a contact — retry.

The customer list has All, Active, Paused and Cancelled views and a search. Each row has:

• the edit button;
• Pause (No new payments will be raised for them) or Activate;
• remove, which cancels their open payments and stops the reminders. Everything they already paid is kept.

There's no bulk import, in the console or the API. To add many customers from code, create them one at a time with the Duesly API.

Billing cycles #

Calendar cycles are calendar-correct. A customer billed on the 31st is billed on 28 February, not the 3rd of March; rolling into the next month would slide every later cycle forward.

Set Day of the month if you want the preferred day to come back after a short month: with it set to 31, March is billed on the 31st again. Left empty, each payment follows the previous one, so after February the customer stays on the 28th.

Payments are raised two cycles ahead, so you can see each customer's next payment date.

How you get paid #

This is the decision everything else follows from. Choose under Settings → 1. How customers pay.

Option A: your own UPI or QR #

Your customer pays you directly; nothing passes through Amomic-AI. There is no automatic follow-up in this mode. Instead, Payments lists every unpaid payment with a one-tap Paid and a Follow up you send when you know the money hasn't arrived.

Why manual mode has no auto follow-up #

This is deliberate. A UPI transfer into your bank leaves no signal Duesly can read, so it can't know a payment happened. An automatic follow-up in this mode would routinely chase people who have already paid, and being chased for money you've already sent is one of the fastest ways to lose a customer's trust.

Automatic follow-ups exist only where a gateway can say whether the money arrived. Follow up automatically is switched off and can't be turned on in UPI mode.

Option B: connect Razorpay #

Each reminder carries a hosted Razorpay payment link. When it's paid:

• the payment closes itself;
• the remaining follow-ups are cancelled;
• a receipt goes out, if you turned receipts on;
• the link is cancelled so nobody can pay twice.

Because the gateway reports payments, the follow-ups can run on their own.

Connecting Razorpay #

Choose Connect Razorpay, then enter:

The keys are checked with Razorpay before they're saved, so a typo fails straight away. Once connected, the panel reads Connected as your key id, with Disconnect.

Razorpay webhook #

One step happens in Razorpay's dashboard, and it's the step people miss.

Without it, a paid link doesn't close its payment: the money arrives and Duesly keeps chasing. Until the secret is set, the connection shows Webhook not set up.

Choosing the messages #

Under Settings → 2. What customers receive:

Customer preview shows the chosen template filled with example values, and Payment value shows what fills a Payment link or UPI placeholder. Create or generate opens the template composer if you need a new template; it still needs Meta's approval.

By default the placeholders run in this order, most essential first, so a shorter template loses the least important detail:

The reminder ladder #

Three messages, then it stops.

  Upcoming ──(due date)──▶ Reminder ──(+1 day)──▶ Follow-up ──(+1 day)──▶ Second
  follow-up ──(+1 day)──▶ Stopped chasing

  At any point:  paid ──▶ Paid      (follow-ups cancelled, link cancelled)
                 waived ──▶ Waived  (your decision)

• One reminder, on the due date, or up to 14 days earlier.
• At most two follow-ups, one a day, with Razorpay and Follow up automatically on.
• Then the payment is marked Stopped chasing and left for you.

Stopped chasing doesn't mean the customer refused. It means Duesly has stopped asking. The payment stays on Payments for you to handle in person: a call, a conversation, a waiver.

A Paid late? button appears on these payments, but recording a payment on one fails today: only open payments can be marked paid. If a customer pays after the chase ended, keep the reference in your own records for now.

You can also step in early. On Payments, Remind now sends the reminder for an upcoming payment straight away, and Follow up sends the next follow-up. Follow up is disabled once a reminder and two follow-ups have gone out.

Payments #

The Payment register has Overdue, Open, Upcoming and Paid views. Each row shows the customer and due date, the amount and period, the status with dots for how many of the three messages have gone out, the next step, and the payment link. See the message that went out opens the campaign the reminder was sent in, with its per-recipient outcome.

Recording a payment #

Paid (on Payments) or Record paid (on Today) opens Record payment from the customer. Used constantly in UPI mode, and now and then with Razorpay for cash, a bank transfer or a cheque.

Mark as paid stops all further reminders for that payment, and cancels its payment link so nobody pays twice.

Waive stops collecting a payment on purpose: Duesly stops every reminder for this payment and it is never counted as collected. From the console the reason recorded is Waived from the console; the Duesly API accepts your own.

Troubleshooting #

From your own code #

Customers, payments and recording payments are all on the API, and payment.paid and payment.declined webhooks fire as they happen. See Duesly API.