Communications
Every message attached to the account it was about.
Statements, invoices, receipts, reminders, payment confirmations and collection outreach on WhatsApp, SMS and email — sent from the financial record, recorded back onto it, and opening onto the account they are about.
WhatsApp.SMS.Email.Calls.
- WhatsApp, SMS and email delivery
- Phone calls logged against the account
- Invoices, statements and receipts
- Payment confirmations that name what was settled
- Scheduled reminders before, on and after due date
- Audiences computed at send time from standing
Part of one system
Members & accountsObligationsBillingPaymentsReconciliationCollectionsCommunicationsMember portalStandingEntitlementsReporting. See how they fit
A reminder sent to someone who has already paid costs more than the reminder you did not send.
Messaging is the part of receivables work that touches the relationship directly, and it is the part most likely to be run off stale data. A list exported on Monday, sent on Thursday, to members who paid on Tuesday.
In Zetu the audience for a run is computed at send time from standing — so accounts with a payment in review, a kept arrangement, an open dispute or a management exception fall out of it without anyone maintaining an exclusion list. That single property is worth more than any template editor.
What gets sent
Documents, notices and outreach.
Invoices
Generated from obligations, delivered on the channel the payer actually reads.
Statements
A period's obligations, settlements and balance, in something a member can follow.
Receipts
Sent when a payment reconciles — not when it arrives, which is a different moment.
Payment confirmations
Confirming what the money settled, so the payer can tell whether it went where they meant.
Reminders
Before due, on due, after grace. Audience computed at send time from standing.
Collection outreach
Composed for a specific account by the collector who owns it, and logged against it.
Account notices
Standing changes, entitlement withdrawals and restorations, arrangement installments falling due.
Demand letters
The formal end of the sequence. Approved by a person before it leaves.
- In audience41 accounts
Overdue, no hold, reachable
- Excluded — payment in review3 accounts
Unmatched money may settle them
- Excluded — arrangement kept2 accounts
Not delinquent while it holds
- Excluded — dispute open1 account
Routed elsewhere
- Cannot reach11 accounts
No contact on file
Where this is going
Conversations becoming part of the financial record.
A member replies to a WhatsApp reminder with three words: “I'll pay Friday.” That sentence is a financial event. It is a dated commitment for an amount, it should suppress escalation until Friday, and on Saturday it should either be closed by a reconciled payment or recorded as broken.
Today a collector reads that message and records the promise. The intent is that the conversation feeds the record directly, so the commitment is captured whether or not anybody had time to type it in.
Roadmap, not shipped
Automatic promise capture from replies is a direction, not a current capability. What works today is that a collector records the promise, it suppresses escalation, and the message thread sits on the account beside it. When it ships, this page will say so — and until then it will keep saying this.
The same reply also carries a second fact worth capturing: they read the message. For an organization whose reminders currently vanish into an unreachable phone number, that is not a small thing — eleven accounts in the example above have no contact on file at all, which is a collections problem disguised as a data-entry problem. See members & accounts.
Capabilities
What is in communications
- WhatsApp, SMS and email delivery
- Phone calls logged against the account
- Invoices, statements and receipts
- Payment confirmations that name what was settled
- Scheduled reminders before, on and after due date
- Audiences computed at send time from standing
- Automatic exclusion of holds, arrangements and disputes
- Per-member channel preferences
- Templates with account and obligation variables
- Approval required on outreach that carries judgment
- Every message threaded onto the account it concerns
- Delivery outcomes and unreachable-contact reporting
Where it leads
Every message has somewhere to go.
Reminder sent · account opened · obligation understood · payment made · payment reconciled · standing updated · entitlement restored. Each step writes to the record the next one reads, so none of it depends on anybody telling anybody else that something happened.
Sending notifications is commodity functionality. Giving them somewhere to lead is not.
Questions
Communications, in practice
Which channels are available?
WhatsApp, SMS and email are the channels the product is designed around, and phone calls are logged rather than placed. Which of them are live for your organization depends on the providers you connect — the integrations page states availability at the category level rather than promising specific connectors.
Do messages go out automatically?
Routine ones do: invoices, statements, receipts, payment confirmations and scheduled reminders. Anything with judgment in it — a first collections call, an escalation notice, a demand letter — is composed or approved by a person. That boundary is configurable, and it exists because an organization's reputation is easier to damage by message than by anything else in this product.
Will members get chased for money they have already paid?
That is the failure this design is built to avoid. Audiences are computed from standing rather than from a static list, so an account with a payment in review, an approved arrangement or an open dispute drops out of the reminder audience automatically. A message sent to someone who has paid does more damage than a message not sent at all.
Can a reply become part of the financial record?
That is where this is heading. When a member replies 'I will pay Friday', that is a promise to pay — a dated commitment that should suppress escalation and then either clear or break on the record. Today a collector records that promise from the conversation; the intent is that the conversation itself feeds it. It is on the roadmap, not shipped, and this page will say so until it is.
Keep reading
- CollectionsThe workflow communications serve.
- StandingWhat decides who is in an audience.
- Members & accountsContacts, channels and preferences.
- IntegrationsWhich channels can be connected.
- Why collection workflows need more than remindersThe limits of messaging alone.
- BillingWhat generates the documents.
Bring us one messy month.
Bring one month of obligations and one month of payments. We will show you what reconciles, what does not, and what that is costing you.