The collaborator's report
- Customer recognised by their number
- File 2481 reread in your software
- Answer sent, payment link attached
- Reminder set for 23 September
A message comes in. The collaborator does the rest.
It recognises your customer, rereads their record in your software, answers, and asks you about anything outside its mandate.
Hi, what's the status of my file 2481?
Your customer
Your file 2481 is confirmed for 24 September. There is €180.00 left to pay: here is your link.Pay €180.00
One turn, step by step
Every message starts the same turn again. Pick a step: the phone replays it.
- Hi, what's the status of my file 2481?
What it knows, what it reads
Two families that never mix: what you have taught it, and what your software says right now.
A question from your customer
Knowledge
Frozen at the last collection
Your website, your texts, your questions and answers: collected, indexed, searched in its own words.
Live data
Reread just now
Your business objects, reread by a call to your software at the moment it answers.
Its answer From your software
Your order 10482 is being prepared; delivery expected on 16 September.
It answers alone, and you test it
It is born autonomous: reading on, writing off, it answers alone. You test its replies in the sandbox, and step it back down a stage whenever you want to review.
It drafts, you read, you send. Nothing goes out without you.
Writing into your softwareOffIt is not a stage: it switches on separately, operation by operation.
The sandbox
The same collaborator, on your real data: only the output is held back. A rehearsal, not a simulation.
Reference cases
Exchanges you freeze and it replays. Without a passing case, it neither moves up a stage nor writes.
The figures
Answers proposed, sent as they were, taken over. Sandbox runs do not count.
Moving down, always
At any moment, with no condition. The kill switch is one click away.
Where it speaks, and at what stage
WhatsApp for the moment, email for attachments and records. One thread per customer, whichever way they came.
The collaborator carries the default stage.
Each channel can refine it: alone on WhatsApp, it proposes on email.
On a thread, you take over, then you hand it back.
The collaboratorIt answers alone
WhatsAppLike the collaborator
Thread · Customer 2479You have taken over
EmailIt proposes
It takes the initiative too
Your software reports an event, the collaborator starts the conversation. Before anything is sent, Nodium checks five things, in this order.
This step sends nothing: it decides. A refusal gives all its reasons, and a price we do not know is called unknown, never free.
Event received from your softwareOrder 10482 shipped
order.shipped- The contactRecognised by their number
- Their consentGiven
- A template approved by Meta“Order shipped”
- The channelWhatsApp, in service
- The costEstimated before sending
It may write
The console, to take over
Four areas, nothing more. You see what it settled alone, and you step in front of it in one move.
Today
Done alone
- File 2481: answer and payment link
- Order 10482: tracking sent
- Appointment on the 18th: reminder kept
In progress
- Mission: get the receipt for file 2466
- Reminder tomorrow, 9:00 am
For you
Grant a €30 goodwill gesture on file 2481?
Outside the mandate: above €20
Try it on your own software.
Connecting happens from a screen. Writing stays off until you switch it on.