If your app already knows who owes what and when, it can trigger the reminder call itself. One API request per customer, with the agent ID, phone number and variables like name, amount and due date, makes an AI voice agent call, deliver the reminder in the customer's language, optionally send a payment link, and post the outcome back to your system. It is one of the most common developer requests we get: reminder calls triggered by the customer's own application. Here is how to build it. It is the AI payment reminder use case, driven by your code.
Get an API key: Create a free Edesy account — Rs 50 free credit, no demo needed.
The architecture
- Your billing system decides who needs a reminder today (e.g. due in 3 days, due today, 3 days overdue).
- Your app calls the Edesy Calls API once per customer.
- The AI agent calls and delivers the reminder, in Hindi, English or a regional language.
- Your callback URL receives the result when the call ends.
- Your app updates the record and stops reminding once payment is recorded.
The request
curl -X POST https://voice-agent.edesy.in/api/v1/calls \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"agentId": 123,
"phoneNumber": "9876543210",
"variables": {
"name": "Ramesh",
"amount": "4,500",
"due_date": "5 October",
"account_ref": "INV-2291"
},
"metadata": { "customer_id": "c_8812" },
"callbackUrl": "https://your-app.com/webhooks/reminder-call"
}'The variables fill the agent's script, for example {{name}}, {{amount}} and {{due_date}}. Full
field list: trigger-call API docs.
The agent's script
Namaste {{name}} ji, main {{company}} ki taraf se ek automated call kar rahi hoon. Aapke account {{account_ref}} ka {{amount}} rupaye ka payment {{due_date}} ko due hai. Kya aap tab tak payment kar payenge? Main aapko payment link SMS par bhej sakti hoon.
Define the fields the agent should extract after the call: outcome (will pay / already paid / needs time / dispute), promised date, and callback requested.
Handling the callback
When the call ends, your endpoint receives the call details, including duration, transcript and outcome; the extracted fields are saved with the call record. Typical handling:
| Outcome | What your app does |
|---|---|
| will_pay + date | Schedule a check on that date; no more calls until then |
| already_paid | Flag for reconciliation; stop reminders |
| needs_time | Create a task for your collections team |
| dispute | Route to support with the call summary |
| no-answer / busy | Retry later the same day, or next day |
Scheduling rules
- Three touches is common: 3 days before, on the due date, 3 days after.
- Call only inside a daytime window, and for lenders, within RBI's permitted hours (see RBI guidelines for AI collection calls).
- Stop as soon as payment is recorded. Nothing annoys customers more than a reminder after paying.
- Cap attempts per customer per cycle.
Why trigger from your app instead of uploading lists
- Always current. The call uses today's balance, not yesterday's export.
- No manual work. No CSVs, no daily uploads.
- Closed loop. Results update your records automatically.
If you prefer lists, bulk campaigns work too; see the 10,000-contact campaign playbook.
Cost
On Edesy, calls are billed per started minute at Rs 4-6 per minute depending on your prepaid top-up, and unanswered calls cost nothing. Most reminders finish within a minute.
Build it this week
Create a free account, generate an API key, and trigger your first call to your own number. For the lending-specific version, read EMI loan repayment reminder voicebots. Need help with the integration? Talk to us.