Solutions · Collections
Collections and Payment Reminder Agents
Arabic voice agents that call your customers about what they owe, with each customer’s balance and due date already on the call. They record what the customer agrees to as structured data and pass the cases that need a person to your team.
- Outbound campaigns from a CSV
- Balance and due date on every call
- Calling hours you set
- Account numbers by keypad
- Promise to pay as an outcome
Use cases
A payment reminder voice agent for each stage of collections
Bill reminders
Call customers before or after a due date with the amount and date from your list, spoken in the dialect you choose for the agent.
Renewal reminders
Tell subscribers that a plan or policy is about to renew, and record whether they intend to continue.
Payment plans
Discuss the options your policy allows, record what the customer agrees to, and send anything outside the policy to your team.
Payment confirmation
Confirm that a payment has arrived, using the status your billing system returns through a tool during the call.
Balance inquiries
On inbound calls, the agent checks the account through your API and tells the caller what is due and by when.
Follow-ups
Run a new campaign for customers who missed a promised date, built from the outcomes recorded on earlier calls.
Collections journey
How automated debt reminder calls run
A reminder campaign on a flow agent, in the order you set it up.
- 01
Load the list
Upload a CSV of customers. Each extra column, such as name, balance or due date, becomes a variable the agent uses on that customer’s call.
- 02
Set when calls go out
Choose a start date and timezone, the daily calling hours and the allowed days. Set them to follow the rules that apply to you and your customers.
- 03
Confirm the account
The agent asks for an account number or the last digits of an ID on the keypad, and a tool checks it against your system before the balance is discussed.
- 04
Remind and listen
The agent states the amount and due date, answers questions from your knowledge base, and hears what the customer can do.
- 05
Record the result
A promise to pay, a dispute or a callback request is extracted as an outcome you defined, kept in call history and sent to your systems by webhook.
- 06
Hand off or follow up
Cases that need a person are transferred to your team’s number. Recipients who did not answer can be retried from the campaign.
Example call
A reminder call that ends in a promise to pay
An illustrative outbound call in Kuwaiti Arabic. The agent confirms the account by keypad through a tool connected to the lender’s system, then records the customer’s promise as a defined outcome.
Example · payment reminder
Examplecampaign: monthly-reminders · variables: name, balance, due_date
callerألو
hamsa agentمساء الخير، معاك المساعد الآلي من شركة النخيل للتمويل. أكلم الأخ فهد؟
callerإي نعم، تفضل
hamsa agentعشان أتأكد إنه حسابك، دخّل آخر أربعة أرقام من رقمك المدني على لوحة الأرقام.
dtmf: 4 digits captured · tool: accounts.verify · verified
hamsa agentشكرًا. حبيت أذكرك إن قسط هالشهر ٢٥٠ دينار، ومستحق يوم ١٥. تقدر تسدده قبل هالموعد؟
callerوالله هالشهر صعب شوي، أقدر أدفع يوم ٢٢
hamsa agentزين، أسجل لك إنك راح تسدد ٢٥٠ دينار يوم ٢٢. صح؟
callerإي، صح
outcome: promise_to_pay · amount: 250 · date: 22
hamsa agentتم التسجيل. شكرًا أخ فهد، ويعطيك العافية.
Specifications
Collections campaign settings at a glance
Keypad capture and transfers are flow agent features. Retries are started from the campaign, for recipients marked failed or no answer.
| Setting | Detail |
|---|---|
| Recipients | CSV upload; extra columns such as name, balance and due date become variables on each call |
| Scheduling | Send now, or at a set date and time with a timezone |
| Calling window | Daily start and end time and allowed days; calls outside the window are deferred, not skipped |
| Campaign controls | Pause, resume, cancel, and retry recipients who did not answer or whose call failed |
| Recipient status | Pending, queued, in progress, completed, failed, no answer |
| Keypad capture | 1 to 20 digits, with a termination key and a timeout of 1 to 30 seconds |
| Lookups and actions | Function tools to your HTTP APIs, or MCP tools; credentials kept as encrypted secrets |
| Outcomes | Your own JSON schema, shown in call history and sent by webhook |
Controls
Arabic collections automation on your terms
Calling hours you set
Every campaign has a daily window and allowed days, and calls that fall outside it wait for the next window. Configure it to follow the rules that apply to your business.
Access by role
Owners, admins and users get different permissions, and the user role cannot monitor live calls. Each project keeps its own agents, numbers, campaigns and call history.
Credentials out of prompts
Keys for your billing or core system are stored as encrypted project secrets and referenced by name.
A record of every call
Each call keeps its recording, transcript, AI summary and outcomes, so a disputed call can be checked rather than argued. Recordings are shared through signed URLs.
FAQ
Questions about AI collections agents
How does the agent know each customer’s balance?
+
Two ways. Values in your campaign CSV, such as balance and due date, become variables on that customer’s call. For figures that change, a function tool can fetch the current balance from your system during the call.
Can we control when collection calls are placed?
+
Yes. Every campaign has a daily start and end time and a set of allowed days, and can be scheduled for a date and timezone. Calls that fall outside the window are deferred to the next one, not skipped. Set these to match the calling rules that apply to your business and your customers.
How does the agent confirm it is speaking to the right person?
+
A flow agent can capture an account number or other digits on the keypad, and a tool checks them against your system before the balance is discussed. You decide what your verification process requires. Hamsa’s speaker identification feature is not meant for authentication.
How is a promise to pay recorded?
+
Through outcomes. You define the fields you want, such as whether the customer promised to pay, the amount and the date, as a JSON schema. After each call they are extracted from the conversation, shown in call history and sent to your systems by webhook.
What happens when a customer wants to speak to a person?
+
A flow agent can transfer the call to your team’s number, straight away or after telling the customer. A transfer to a phone number starts a new call, so the conversation history does not travel with it. The recording, transcript and outcomes stay in call history.
What about customers who do not answer?
+
Each recipient has a status: pending, queued, in progress, completed, failed or no answer. You can retry recipients marked failed or no answer, and pause, resume or cancel the campaign at any point.
How do we measure a collections campaign?
+
Recipient statuses show who was reached, and the outcomes you define give the result of each call. The agent dashboard adds call volume, duration, the share of calls forwarded to a person and escalation rate, and exports to Excel.
Keep reading
Hamsa Agents · Phone
AI Phone Agents
Inbound and outbound Arabic voice agents on your Twilio numbers or SIP trunk, with keypad input, transfers and campaigns.
Read →Solutions · Appointment booking
AI Appointment Booking Agents
Arabic voice agents that book, reschedule and cancel through your scheduling API, and run reminder campaigns inside your calling hours.
Read →Enterprise · Security
Security Compliance and Data Control
Isolated projects, roles, public and secret keys, encrypted secrets and HTTPS webhooks, with the language model set per agent and private deployment options.
Read →


