Recipient simulator
"Who receives what?" shows you the list and the reason for each inclusion, without sending anything.
You define which events in your operation deserve an alert and who should get it. Pacunex sends it through the right channel — and lets you see who will get it before switching it on.
Simulate before sending · nothing goes out until you switch it on.
A payment came in, a promise expired, a case escalated. The data is in the platform, but the person who had to act finds out two days later — or never. And whoever tells them is someone who remembered to look.
Alerts that depend on someone remembering to check a screen.
Or the opposite extreme: so much automated email that the team already ignores it.
Rules nobody dares touch for fear of spamming customers.
From your operation's event catalog you pick the one you care about: a payment received, an expired promise, an escalated case.
You state who receives it and through which channel: email, WhatsApp or inside the system.
Before switching on, the simulator lists the recipients and the reason each one is in or out. Without sending a single message.
You edit the template to your tone and brand, in a visual editor. The rule runs from there.
An engine that, for each event in your business, decides who should find out and through which channel. What makes it usable is not that it sends: it is that you can see who will get it before switching it on.
"Who receives what?" shows you the list and the reason for each inclusion, without sending anything.
Email, WhatsApp or in-app alert. Each rule picks how it goes out.
A visual editor so the alert speaks like your company, not like a system.
Each organization defines its own on top of a shared base that does not break.
The alert can carry the generated receipt attached, ready to forward.
When many things happen at once, it groups the alerts into one instead of firing twenty.
The channel is picked per rule, depending on who you are talking to.
Honest projections — Pacunex is in open beta.
The payment is registered and the PDF receipt goes out to the customer without anyone building it by hand.
A case escalates and the owner gets the alert right then, not in Monday's meeting.
You simulate first, see exactly who would get it, adjust, and only then switch on.
Guided implementation, special beta conditions and a direct voice in the roadmap.
Yes, and it is the module's most useful feature. The "Who receives what?" simulator lists the recipients and the reason each one is in or out, without sending a single message.
Yes. Templates are edited in a visual editor, and each company has its own on top of a shared base. You can adjust tone, content and branding.
That is exactly the problem it avoids. When many events happen at once, it groups them into a single alert instead of firing one per event. And you switch each rule on yourself, after simulating it.
The events of your operation: payments received, expired promises, escalated cases, among others. There is a catalog to choose from, and it grows with what your company needs.
No. The AI agent queries what it needs each turn via database, REST API or MCP and does not copy your database. Chat sessions and operational logs are stored encrypted in our infrastructure, isolated per company.
Let's chat on WhatsApp, review which events in your operation deserve an alert and build the first rules with you.