An AI agent that finishes the work
Nuncily runs on one mechanism: a loop that takes a request from first contact to a verified result, asking and checking as it goes, with a person brought in only when judgment is needed. Every product decision follows from this loop.
A diagram of the Nuncily execution loop: a request moves through eight steps — receive, understand, collect, clarify, validate, act, verify, complete — reaching a finished outcome. One path branches off to a person, representing the cases where judgment is required before the loop continues.
The loop, step by step
Receive
A request arrives on whatever channel the customer already uses — a WhatsApp message, an email, a form on your site, an event from another system. Nuncily reads it in context: what's being asked, and which process it belongs to.
Understand
Nuncily works out what outcome is actually being requested, not just what was said. A short message is enough context to identify the process, the customer, and what's needed next.
Collect
It asks for exactly what the process requires — nothing generic, nothing padded out. If a process needs three things, Nuncily asks for three things, clearly, once.
Clarify
When something's ambiguous — a wrong format, an unclear figure, a partial answer — Nuncily asks about it in the same conversation. No support ticket, no separate thread to lose context in.
Validate
What comes back gets checked against what the process actually requires, not just whether something arrived. Nuncily catches what's missing or inconsistent before it becomes a downstream problem.
Act
Nuncily updates the systems the request depends on — the record gets logged, the account gets updated, the filing gets prepared.
Verify
Before anything is marked complete, the outcome is checked against the request. This is what separates “sent” from “done.”
Complete
The business gets a finished process back — not another task sitting in someone's queue.
Escalate only when needed
When something needs judgment a system shouldn't make on its own, Nuncily hands it to a person — with the full conversation and everything collected so far attached, not a summary that's lost the context.
The loop, running
The same eight stages above, played out on three real request shapes. Pick one and follow what comes in, what Nuncily does with it, and what leaves.
Incoming
3- WhatsApp|Client
Hi — sending my Q2 records over
- WhatsApp|Client
Here's the first one
statement.pdf - WhatsApp|Client
Missed that — here you go
statement-june.pdf
Nuncily working
4- Engine|Nuncily
Outcome identified: Q2 record collection for one client.
- Engine|Nuncily
Checked against what the quarter requires. All three documents now cover the full period.
- System|Practice management
Documents filed against the client's Q2 record.
- Engine|Nuncily
Filed record re-read and checked before the outcome is called done.
Outgoing
3- WhatsApp|Nuncily
I need three things for Q2: bank statement, expense log, and last quarter's invoices.
- WhatsApp|Nuncily
The statement stops on 19 June, 11 days short of the quarter. Can you send the rest?
- WhatsApp|Nuncily
That's everything for Q2. Nothing further needed from you.
Stage
Loop complete
- 01Receive
- 02Understand
- 03Collect
- 04Clarify
- 05Validate
- 06Act
- 07Verify
- 08Complete
Connected systems
A client sends their quarterly records on WhatsApp. Nuncily asks for what's missing, checks what arrives, and files it.
Not a fixed script
A workflow diagram has to anticipate every branch in advance, and stalls when something falls outside it. Nuncily doesn't run a fixed script — each step responds to what actually came back, which is why it can handle the wrong-format document or the partial answer without stopping and waiting for someone to notice.
That's also why escalation isn't a failure state. It's what the loop does deliberately when a decision needs judgment a system shouldn't make on its own.
Where teams put it to work
Any process built from a request, a handful of exchanges, and a system that needs updating once everything checks out. These are the shapes it takes most often.
Questions about the platform
What is Nuncily?
Nuncily is an AI execution layer for business operations. It takes a request from the first message to a finished outcome: asking the customer for what's needed, checking what comes back, updating your systems, and bringing in a person only when judgment is required.
How is this different from a workflow builder or RPA?
A workflow builder or RPA bot follows a fixed script and stops when something falls outside it. Nuncily responds to what actually came back, so a wrong-format document or a partial answer gets handled in the same conversation instead of stalling the process.
Does it replace my team?
No. It takes the chasing, checking and re-asking off your team's plate. Decisions that need judgment go to a person, with the full conversation and everything collected so far attached.
Which channels does it use?
The platform is WhatsApp-first, with email set up where a business needs it. Custom builds can use whichever channels your customers already use. The channel is an interface; the process behind it is the product.
Can it work with the systems we already use?
Yes. Nuncily acts inside permissions you define on the systems a process depends on. Where a system needs a bespoke connection, our team builds it as part of a custom automation project.
What does it cost?
The Practice plan covers one workflow, set up for you, at a single monthly price in US dollars, pounds sterling or euros, with no setup or onboarding fee. Larger or bespoke work is scoped with you.
See where this applies to your process.
Bring us the process you'd hand over first. We'll walk the loop through it with you, step by step.
Loading available times…
Open the calendar in a new tab- A conversation about your process, not a slide deck.
- 30 minutes. We'll show the loop running on a process shaped like yours.
- No obligation, and your details stay with us.