Ask, remind, and collect — from the same contact record.
Survey sends the CSAT question after the interaction, collection chases the receivable before it ages, and broadcast delivers the announcement to a segmented audience. All three read the same contacts and write back to them.
Three modules that ask customers something and follow up on the answer: surveys to measure satisfaction, collection to recover receivables, and broadcast to deliver messages at volume.
All three use the same channel connectors, so a survey can arrive by WhatsApp and a payment reminder by SMS without a second integration project.
- 3Workloads on one contact base: survey, collection, broadcast
- 1Answer per respondent, tied to the interaction it rates
- 100%Messages sent through the same WhatsApp and email connectors
The score arrives attached to the interaction it rates.
A survey is triggered by the event — a closed ticket, an ended call, a completed visit — and the answer is stored against that event, not in a separate spreadsheet. CSAT settings decide when to ask and when to stay quiet.
- Trigger from the event: ticket closed, call ended, visit completed
- One question or a short set, with the response tied to the record
- Results per team, per agent, and per period without a manual export
Reminders that escalate on a schedule, not on a mood.
Receivables are bucketed by age, assigned to a collector, and reminded on a schedule that the team can read. Field visits and promises to pay are recorded against the account, and compliance rules decide when a reminder must not be sent.
- Buckets by ageing with assignment per collector
- Scheduled reminders through WhatsApp, SMS, and email
- Field visit notes and promise-to-pay dates on the account
| # | Subjek | SLA |
|---|---|---|
| 1841 | Gagal login aplikasi | 2 jam |
| 1842 | Permintaan reset kata sandi | Selesai |
| 1843 | Invoice belum diterima | Hari ini |
One announcement, a segmented audience, a delivery report.
Audiences are built from contact segments, and the message goes out through a channel template with its approval state where the channel requires one. Delivery and read reports show what actually arrived instead of what was intended.
- Audience from contact segments, not a pasted number list
- Channel templates with approval state tracked
- Delivery and read reports per campaign
What this module group covers
Survey builder
Question set per event, with CSAT and NPS scoring.
Response reporting
Per team, per agent, per period.
Collection buckets
Ageing buckets, assignment, and reminder schedules.
Field collection
Visit notes, promise to pay, and compliance rules.
Broadcast audiences
Segments from the contact base with template approval.
Delivery reporting
Sent, delivered, read, and failed per campaign.
How the three fit together
What triggers the ask: resolution, payment, announcement.
Segments, exclusions, and who must not be contacted.
Message and channel; approval where the channel requires it.
Response rate, score, and the reasons behind the low ones.
Questions about asking customers
Will we spam people?
Exclusions are explicit: do-not-contact entries, channel approval states, and per-campaign audience definition.
Can a survey be triggered by a WhatsApp conversation?
Yes. The trigger is the event, and the channel is chosen by the survey configuration.
Does collection work with our invoice system?
Receivables can be imported through the data manager and kept in sync by schedule.
Where are the answers stored?
Against the interaction record in the same database as the rest of the suite.
Run a campaign with measurable results.
Bring the audience list and the message intent. We help with segmentation, template wording, and the reporting you need afterwards.