Confirmation after a photo
A short reply lets staff know their photo of a document reached the pipeline.
Home › Integrations › Telegram & WhatsApp
Telegram and WhatsApp as intake and review channels
Staff photograph a receipt and send it to a bot, and anything that fails validation lands in a review channel for a person to fix or approve. The same chat carries pause, resume and status commands with a built-in safety limit.
Channel, not a ledgerTelegram and WhatsApp carry documents and messages; the record of what happened lives in your accounting or CRM system.
Intake Staff photo sent to a botExceptions Posted to a review channelRun control Pause, resume, status commandsSafety limit Stops past 40 letters or €20,000
Photostaff photographs a receipt or document
Botimage goes straight into the pipeline
Checkpipeline validates the extracted fields
Reviewexceptions posted to a review channel
Controlpause, resume and status from the chat
What lands in Telegram & WhatsApp
Exception message to review
Anything that fails validation is posted to a review channel with what needs a decision.
Pause and resume commands
A person can pause or resume a run, or ask for its status, directly from the chat.
Status of the current run
The chat reports what a run is doing so no one has to open the ledger to check.
Stop alert on a safety limit
A run stops and alerts the group before it would send more than 40 letters or chase more than €20,000.
Where it gets awkward
Every system has edges. These are the ones that shape the build — better known before the pilot than during it.
No audit trail of its own
A chat is not a ledger. Every document that comes through is written to the client's accounting or CRM system, so the record of what happened lives there, not in chat history.
Message retention is not ours to set
Retention and deletion of messages are controlled by the platform and the group, not by the pipeline. Anything that matters is copied into a system of record before it can be lost.
People can leave the group
If someone leaves a review channel, they stop seeing new exceptions. Pause, resume and status commands and the safety limit protect a run either way.
Is a custom pipeline worth it here?
Worth building
- Staff need the fastest way to capture a document, with no app to install.
- Exceptions need to reach a person immediately instead of sitting in a queue.
- A run needs to be stoppable by anyone on the team, from their phone.
Native tools are enough
- You need message history to serve as an audit trail or accounting record.
- Your team already works inside the accounting or CRM system all day.
The task behind this
Solution
Invoices and receipts posted into your accounting system automatically
Supplier invoices and staff-photographed receipts posted straight into Merit Aktiva, Xero, QuickBooks and more, with exceptions sent to a review queue.
→How the stream is built
Processed in the EU. The original files and extracted data stay in your own systems; a data-processing agreement is available on request — see security and data handling.
From audit to autopilot
Step 1
Audit
We map one document or enquiry stream end-to-end, count volumes and name the systems it touches. You get a written scope and a fixed pilot price.
Free · 3 working daysStep 2
Pilot
One stream goes live on your real documents. Acceptance is measured, not felt: straight-through rate, minutes per document, exceptions.
About two weeks · fixed priceStep 3
Rollout
The remaining streams follow the proven pattern. Monthly report, support, and changes as your systems change.
Stream by streamFrequently asked questions
Is Telegram or WhatsApp where our documents are actually stored?
No. They are the intake and review channel. Every document that passes through is written to your accounting or CRM system, which stays the system of record.
What happens when a document fails validation?
It is posted to a review channel with the fields that need a decision, and a person fixes or approves it there before it goes into your accounting system.
Can we stop a run from our phones?
Yes. In our accounting-firm project, reminder runs are controlled from a Telegram group with pause, resume and status commands, so anyone with access to the chat can intervene.
What stops a run from going too far?
A built-in safety limit. In that same project, a run stops and alerts the group before it would send more than 40 letters or chase more than €20,000.
Does this work with WhatsApp as well as Telegram?
Yes. Both are used the same way: as a channel for staff to send documents in, and for the pipeline to post exceptions and run status out.
Using Telegram & WhatsApp? Start with the audit
Three working days, one document stream mapped end to end, a fixed pilot price on paper. No commitment.
Get a free automation audit