Context
A sector where documents are never a detail
Sector
A player in the funeral services sector, handling sensitive case files, high volumes of incoming documents, and a strong need for operational reliability.
Documents
PDFs, scans, signed documents, quotes, purchase orders, and supporting materials — often received in heterogeneous formats and rarely standardised.
Fragmentation
Information scattered across email inboxes, document storage, the commercial CRM, and billing tools, with multiple manual re-entry points.
In funeral services, a client file is not simply a contact record and a commercial opportunity. It aggregates contractual documents, documents transmitted by email, scans retrieved in the field, billing items, sometimes content shared by multiple parties, and often urgent deadlines that require immediate action. In this context, a document is not just an attachment. It sits at the core of the business process.
The problem emerges as soon as these documents live in a fragmented environment. Useful information may be visible in a PDF but absent from the CRM. A document may be stored somewhere without being linked to the right case. An update may be made in a commercial tool without being reflected in the document history. The cumulative effect is well known: teams lose time, data degrades, and operational continuity depends on individuals who know where to look rather than on a system that knows what to do.
This is precisely the terrain on which the project was framed. The objective was not to create yet another storage space, nor to add decorative AI functionality. The goal was to transform a document-heavy environment into a genuinely operational CRM — one capable of absorbing incoming documents, structuring their content, and making them immediately useful for commercial and administrative tracking.
Challenge
Eliminating the friction created by manual entry, data dispersion, and lost context
Time-consuming manual entry
Every incoming document required a human to read it, interpret it, and then enter or verify the data across multiple business screens.
Disconnected tools
The CRM, document repository, and billing system did not always share the same level of information, creating gaps in commercial and administrative tracking.
Missing or incomplete documents
When a document was missing, the team had to dig through emails, shared folders, or exports — with a real risk of losing context in the process.
The first challenge was very concrete: too much time was disappearing into re-entry. When a document arrived, it had to be opened, read, matched to a case, and its key information extracted and re-typed into the CRM or management tool. This kind of operation seems simple at small scale. It becomes costly as soon as it repeats dozens of times a week, especially in a sector where urgency and precision must coexist.
The second challenge was structural. The tools did not always speak the same language. A contact might exist in the CRM, a document in a shared folder, and billing information in Sellsy — each block of truth becoming partial. When an organisation lives with multiple versions of the same information, it suffers not only from inefficiency. It suffers from a loss of confidence in its own system.
The third challenge, often underestimated, concerned documents disappearing in the mass. A document that exists but is not linked to the right case is practically a lost document. The team must then go back through emails, exports, local scans, or shared directories. This document hunt slows everything down, exhausts teams, and increases the risk of error at the most sensitive moments.
Solution
An AI-augmented CRM chain designed to read, verify, and synchronise
01
Multimodal OCR powered by Gemini
Documents are processed by an AI engine capable of extracting text, recognising form structure, identifying key fields, and returning data that the CRM can act on.
02
Business validation before record creation
Extracted data is not injected blindly. A control step allows teams to confirm the data, correct any ambiguity, and secure the creation or update of business records.
03
Automatic synchronisation to Sellsy
Once validated, structured information feeds Sellsy to maintain a coherent commercial history — without re-entry and without breaks between the field and the CRM.
04
Intelligent document routing
Each document is filed in the right context, linked to the right case, and surfaced at the right moment in the interface — eliminating manual searches and duplicates.
The implemented response is grounded first in a multimodal OCR engine powered by Gemini. The challenge is not simply to convert an image into text, but to reconstruct an actionable understanding of the document. This means recognising the nature of the document, identifying important zones, extracting structured fields, and preparing data ready to enter a business workflow. This approach handles real documents — imperfect, varied, and sometimes incomplete — which is exactly the kind of material teams encounter daily.
Next, the system introduces a validation layer before any automatic creation. This is a decisive point. In a serious CRM, automation only has value if it reduces cognitive load without surrendering control. Extracted data can therefore be verified, completed, or corrected before feeding business objects. The AI prepares the work, humans retain control over sensitive cases, and the system learns from genuinely useful patterns.
Once that step is passed, synchronisation to Sellsy becomes the natural extension of the flow. Validated information can update the commercial CRM without going through a manual re-entry phase. This immediately changes the quality of tracking. Teams no longer work with a system lagging behind the documentary reality. They work with data that follows the document almost in real time, in a structured and reusable format.
Finally, the project addresses a topic often neglected in AI deployments: document routing. A good OCR system is not enough if the document ends up in the wrong place. Each document must be linked to the right case, the right client, and the right point in the cycle. It is this articulation between reading, validation, synchronisation, and filing that transforms a collection of automations into a truly operational CRM agent.
Results
Less time lost, greater reliability, virtually no re-entry on the covered workflow
Reduced time
Faster processing of incoming documents
The journey from received document to actionable data is dramatically shorter, as the team no longer starts from scratch each time a file is opened.
Reliable data
Higher data quality in the CRM
Structured extraction, validation, and synchronisation limit the gaps between what was read, what was confirmed, and what is actually recorded.
0 re-entry
Manual entry eliminated on the covered workflow
For correctly recognised and validated documents, teams no longer copy information field by field into the CRM and billing system.
The first visible result is the reduction in processing time. When a team no longer has to read an entire document to re-type its content into multiple tools, a case advances faster and with less cognitive fatigue. This gain is not limited to a few minutes saved. It changes the speed of transition between receipt, qualification, and exploitation of the data.
The second result concerns information quality. By structuring extraction, enforcing validation, and synchronising to Sellsy from clarified data, the CRM gains coherence. Duplicates decrease, fields are better normalised, and teams regain confidence in what they consult. This improvement in precision is fundamental, because a CRM is only useful if it is considered reliable by the people who use it every day.
The third result is the elimination of manual re-entry on the automated scope. For correctly recognised and validated documents, information flows without being copied field by field. This is a key point for industrialisation. An organisation can accept human validation. It cannot sustainably accept transforming every incoming document into a repetitive administrative task.
Technical lessons
What this project confirms about building a serious AI CRM agent
A useful OCR is a workflow, not just a model
The real value does not appear at the point of raw extraction. It appears when the AI inserts itself into a complete journey — from document receipt through to business system update.
The canonical data model must be defined before synchronisation
Without a stable data model, CRM synchronisation produces noise. You must first decide which field is authoritative, which identifier links objects, and how to handle partial cases.
Confidence must be visible
A reliable extraction system is not one that claims to know everything. It is one that exposes zones of uncertainty, facilitates human validation, and keeps a trace of corrections.
Document routing is as important as extraction
Reading a document without knowing where to file it solves only half the problem. The other half is associating it with the right case, the right client, and the right point in the process.
Industrialisation requires observability
To improve a CRM agent over time, you must track failures, corrections, the most sensitive document types, and the fields that generate the most friction.
The main lesson is straightforward: an AI CRM agent is not a chatbot plugged into a database. It is a system that understands flows, respects business constraints, handles ambiguous cases, and integrates into a real environment composed of emails, documents, validation rules, and external synchronisations.
This case also shows that AI does not replace process design. It makes it more powerful, provided the framing is clean. When the data model, validation rules, and filing logic are clear, OCR and automation produce genuine value. If those foundations are blurry, AI primarily accelerates the disorder.
CTA
Is your CRM overloaded with PDFs, scans, and manual re-entry?
We design CRM agents capable of reading your documents, structuring your data, securing business validation, and synchronising information into your existing tools. If your team is losing time between incoming documents and the CRM, this is probably something to address now.