Loading
Billing & Collections Agent
Every past-due invoice,worked.
It reads balances from your billing system, runs a per-account sequence in your tone and inside the rules you operate under, and makes paying the easiest thing on the customer's list.
The problem
The past-due list is stillthe past-due list.
Chasing is the job nobody wants
It is uncomfortable, repetitive, and always the first thing dropped when the week gets busy. So the list grows.
Most of it is not refusal
A card expired. An invoice went to the wrong inbox. A reminder was missed. These get paid the moment somebody asks properly.
Paying is harder than it needs to be
The customer has to find the invoice, find the portal, find the card. Every extra step is another week.
How it works
01
It reads the ledger
Balances and ageing from your billing system, refreshed on your schedule.
02
It reaches out
On your cadence, in your tone, on the channel that account actually responds to.
03
It makes paying easy
A link to the payment path you already run, or the payment taken in the conversation.
04
It flags the exceptions
Disputes, hardship, and anything that needs a person go to your team with the history.
What you get
The whole job done,not a demo of it.
Inside the rules you operate under
Contact hours, frequency limits, required disclosures, and the wording you have approved. Configured per jurisdiction, and it does not improvise around them.
Your tone, not a collections script
These are customers you want to keep. The sequence reads like a business reminding a customer, because that is what it is.
A sequence per account, not per list
Amount, how overdue, payment history, and channel preference all shape what it sends and when it stops.
Stops the moment it should
A payment, a promise to pay, a dispute, or a request to stop ends the sequence immediately and tells your team why.
Disputes go to a person
It does not argue about whether the balance is right. Anything contested is handed over with the full history attached.
Every contact logged
What was sent, when, on what channel, and what came back. The audit trail is the point, not a by-product.
In action
A past-due account, worked.
Pick a reply or type your own. Watch where it stops.
Live
Past due · sequence running within your rules
$0 collected today
- Unit 212$1,240 · 6dstep 2 of 4Paid via PayPal
- Unit 118$1,425 · 3dstep 1 of 4Promise to pay · Fri
- Unit 306$595 · 11dstep 3 of 4Paid via PayPal
- Unit C-114$169 · 2dstep 1 of 4Reminder sent
- Unit lot 42$1,150 · 19dstep 4 of 4Escalated · dispute
Card details never pass through Stomeji · Sample workspace, figures illustrative
Specifics
Where it runs.
Against the ledger you already keep, on the channels the account already uses.
- Channels
- Voice, SMS, WhatsApp, email
- Hours
- Your permitted contact windows
- Source of truth
- Your billing system or accounting ledger
- Payment
- Your existing payment path, or hosted checkout
- Stop rules
- Payment, promise, dispute, or opt-out
- Logging
- Full contact history on the account
Is this a debt collector?
No. It is first-party contact from you to your own customer about your own invoice. It does not buy debt and it does not act for a third party.
How do you keep it inside the rules?
Contact hours, frequency caps, and required wording are configuration, not suggestions. Where you operate under a specific regime, that regime's limits are set before it sends anything.
What if the customer says the balance is wrong?
The sequence stops and a person picks it up. It will not argue the amount or restart the cadence on a disputed account.
Will this damage the relationship?
That is why the tone is yours and the stop rules are strict. Most past-due balances are an oversight, and a clear reminder with an easy payment link reads as a service.