An orchestration agent, scoped with you before it is priced. This agent coordinates several specialised agents. Its orchestration follows your actual workflows — which is why it is scoped with you rather than bought off the shelf. We establish the scope together, then the quotation commits it.
The journeys described below form the scope that this review refines and the quotation commits. The specialised agents it coordinates can be ordered today.
Request a quote
● Public sector — Agricultural social security caseworker
AI agent for the caseworker in agricultural social protection
An assistant that pre-assesses the files of the single agricultural desk (health, family, pensions, contributions) and prepares the replies to members — the caseworker decides on every entitlement. Hosted in France on a resource isolated for each organisation, with an HDS option for health data: nothing leaves the European Union.
Hosted in France
Members' data protected
GDPR & AI Act: governed deployment, HDS option
The caseworker decides on every entitlement
Updated on
Deployed in a few weeks
Agricultural social security assistant · hosted in France
Pre-assess the family benefits claim from this farmer who has just registered a birth.
File pre-assessed. Membership of the agricultural scheme verified, household composition updated with the birth certificate supplied, reference income gathered. Document missing: bank details in the household's name — request prepared.
Complete file passed on for decision: opening the entitlement stays yours.
⛓ Source · the member's file + the documents filed
Complete file passed on for decision: opening the entitlement stays yours.
⛓ Source · the member's file + the documents filed
Prepare the reply to this livestock farmer asking to spread their contributions after a difficult year.
Draft letter ready: acknowledgement of the request, a reminder of the supporting documents expected (the year's accounts), and a presentation of the instalment scheme — with no commitment as to the outcome, which is your decision.
For review, completion and signature.
✎ Action · letter ready for review — the caseworker approves
For review, completion and signature.
✎ Action · letter ready for review — the caseworker approves
Local inference · no data outside the EU
Data hosted in France
Sovereign by designHosting in France, HDS option
GDPR & AI Act: governed deploymentTraceability & human oversight
TurnkeyDesigned, installed and operated for you
The caseworker decidesNo entitlement is opened automatically
✦ In brief
At the agricultural social security fund, a Blue Lemon Agent agent assists the caseworkers of the single agricultural desk with the repetitive tasks — pre-assessment of multi-branch files (health, family, pensions, contributions), checking documents, letters and notifications to farmers and agricultural employees, answers to everyday questions. It is hosted in France on a resource dedicated to and isolated for each organisation, with an HDS option for health data, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. No entitlement is opened automatically: every decision remains that of the caseworker concerned. Live within a few weeks. Your public-sector staff write to it from Microsoft Teams, Slack or their email, and your members reach it on WhatsApp Business, the website chat or email — with no account to create and nothing to install. Reaching the administration from the tool people already have means less non-take-up of rights and equal access to the service. These connections are included in every plan, at no extra cost, within the number of connections your level includes.
100%
hosted in France in the target architecture
0
transfer outside the EU in the target architecture
7
uses ready to deploy on this scope
0
decision taken without human approval
Reference points describing our offer, not results measured at a client. The scale of the gain is confirmed by a pilot on your own scope.
The context
Why AI matters to the agricultural fund — and why it demands guarantees
As the single desk for the farming world, the fund handles health, family, pensions and contributions at once: multi-branch files, numerous documents, members waiting for answers. The data handled mixes social circumstances, income — and sometimes health.
! The issue
The caseworker is caught between members — farmers and agricultural employees — who expect quick decisions and multi-branch files whose pre-assessment is time-consuming: documents, memberships, income, consistency between branches. Yet most consumer AI tools amount to entrusting social circumstances, farm income and health data to a third party, often hosted outside Europe and subject to the Cloud Act.
✓ Our answer
For a social protection body, AI is only of interest if it is sovereign and confidential by design. Hosting in France on a resource isolated for each organisation, an HDS option for health processing, systematic human oversight: the AI agent prepares the files of the different branches consistently, but every entitlement opened remains the decision of the caseworker concerned. The aim is not to replace the caseworker, but to give them back time for supporting members.
The decisive point
Protecting members' data: sovereignty & compliance
An agricultural social security fund handles social, financial and health data. Here is how the architecture of our agents protects it, organisation by organisation.
Local inference
The agent can run on a machine at the fund: no data leaves the network, nothing passes through a cloud.
Hosting in France
Otherwise, a dedicated and isolated resource, hosted in France under French law — members' data: processing and access within the European Union targeted by the architecture.
Reduced extraterritorial exposure
Members' data: architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
HDS option for health
The health-data hosting level the sector requires, for the health branch's processing.
Encryption & controlled access
Encryption in transit and at rest, role-based access (RBAC), strong authentication and logging.
AI Act: governed deployment
The agent is strictly in support; no entitlement is opened automatically; traceability and human oversight from end to end.
What depends on the architecture chosen These points are not general guarantees: they are settled deployment by deployment, in the quotation.
- The applicable location is that of the architecture set out in the quotation and verified before commissioning.
- Local execution is announced only for the configuration explicitly described and accepted in the quotation.
- The applicable isolation depends on the deployment mode set out in the quotation; no dedicated isolation is presumed.
- The encryption mechanisms in transit and at rest, their components and key management are those documented for the architecture chosen.
- Roles and permissions are configured and accepted for the identities and systems actually connected.
- The events logged, their content, their retention period and who may access them are defined for the deployment chosen.
For the health branch's health data, HDS hosting (the French certification for health data hosts); a SecNumCloud option according to how demanding your requirements are. A single architecture is designed to answer both the GDPR and extraterritorial exposure. Designed for deployment in line with the GDPR and the AI Act, after the processing, roles and context-specific risks have been assessed.
Demonstration
See the agent at work
5 real situations, taken from those that come up most often. Pick one: the exchange unfolds as it would in your organisation.
A scripted demonstration. These exchanges show how the agent behaves — its sources, its refusals, what it leaves to your teams. Nothing is sent from this page, no model is queried here, and the matters named are fictional. That is precisely what we promise your data.
The behaviours shown here — monitoring, automation rules, routing and reminders — are configured with you during deployment, from your tools, your rules and your thresholds.
The architecture points named in these exchanges — location, local execution, isolation, encryption, role-based access, logging — are not a guarantee attached to the demonstration: they are those of the architecture set out in your quotation, and verified before commissioning.
The public body in this demonstration
Fictional public bodyVal-de-Sarne agricultural social protection fund — county single desk
- Sector
- Agricultural social protection through a single desk — health, family, pensions and contributions for farmers and farm employees alike, plus social action
- Headcount
- 140 staff — including 46 single-desk caseworkers across the four branches, 14 on the telephone service, 6 social workers, and a separate medical service, alone authorised on medical material
- Public served
- 38,500 members — 12,400 farm owners, 21,300 farm employees and 4,800 pensioners, across 640 villages, 41 of which have no reliable mobile coverage
- Order of magnitude
- 26,000 files handled a year across all branches, including 1,200 multi-branch files, 74,000 documents received, 20,000 letters to members and 112,000 enquiries: 82,000 calls, 20,000 e-mails, 10,000 messages in the online account
- Tools in place
- Four management systems, one per branch, an online account for members, the telephone platform and 8 years of filed documents — the agent plugs into them read-only, nothing is replaced and nothing is migrated
- Who decides
- The caseworker opens the entitlement and signs the notification; the medical service alone accesses medical material and issues its opinion; the head of service approves contribution instalment plans; the social action committee awards grants
- Points for improvement
- One file in five was waiting for a document the member had already filed in another branch; a multi-branch file passed through four caseworkers and three systems over 31 days; 34 % of calls rang unanswered at due-date peaks; and 780 members met the conditions for a benefit they had never claimed
At Val-de-Sarne, the single desk is a promise half kept: the member has one point of contact, but their documents live in four systems that do not talk to each other, and it is the member who pays the difference in re-requested documents and weeks of waiting. The agent is hosted in France on an isolated resource, under the hosting requirements that apply to health data, reads the eight years of files without ever writing to them, and releases nothing without a caseworker's approval. The exchanges below cover a year, from taking stock of the documents to the review presented to the board.
This public body, its figures and the exchanges that follow were invented for the demonstration. They illustrate a common situation; they describe no real service.
Agricultural social security assistant · hosted in France
I reread your eight years of files over the weekend — 26,000 files a year, 74,000 documents received, four branch systems — and I have drawn out a figure your single desk pays without seeing it.
The gap measured, and it decides everything else: one file in five — 5,200 a year — was waiting for a document the member had already filed in another branch. A tax assessment given to the family branch in February was asked for again by the contributions branch in June; bank details provided at retirement were asked for again for a family benefit.
The cause, measured and not assumed: your four branch systems do not talk to each other. The desk is single for the member, it is not single for the document — and nobody has ever had the time to check, branch by branch, whether the document being asked for was already sleeping in another file.
What it costs the member, and this is where it shows: every re-requested document adds 14 days to the file — the letter, the trip to the village, the return post. Across 5,200 files a year, that is 5,200 farmers or farm employees whom the fund asked twice for the same thing.
What I have already done, and this is not a promise: I have built the index of documents per member, across all branches, and run it over the last twelve months. It would have avoided 5,200 document requests out of 9,400, and brought the average delay of a file awaiting a document from 21 days to 7.
The next step I propose, and it takes one meeting: you approve the list of the ten most re-requested documents — tax assessment, bank details, birth certificate, school certificate, proof of address and five others. They stop being asked for again from the moment you approve, and next year's 5,200 letters will simply not exist. documents-already-filed_5200-requests-avoided.pdf1 file in 5, 14 days of waiting per re-requested document
⛓ Sourced · 8 years of files, 74,000 documents received, logs of the four branch systems, index tested over 12 months
The gap measured, and it decides everything else: one file in five — 5,200 a year — was waiting for a document the member had already filed in another branch. A tax assessment given to the family branch in February was asked for again by the contributions branch in June; bank details provided at retirement were asked for again for a family benefit.
The cause, measured and not assumed: your four branch systems do not talk to each other. The desk is single for the member, it is not single for the document — and nobody has ever had the time to check, branch by branch, whether the document being asked for was already sleeping in another file.
What it costs the member, and this is where it shows: every re-requested document adds 14 days to the file — the letter, the trip to the village, the return post. Across 5,200 files a year, that is 5,200 farmers or farm employees whom the fund asked twice for the same thing.
What I have already done, and this is not a promise: I have built the index of documents per member, across all branches, and run it over the last twelve months. It would have avoided 5,200 document requests out of 9,400, and brought the average delay of a file awaiting a document from 21 days to 7.
The next step I propose, and it takes one meeting: you approve the list of the ten most re-requested documents — tax assessment, bank details, birth certificate, school certificate, proof of address and five others. They stop being asked for again from the moment you approve, and next year's 5,200 letters will simply not exist. documents-already-filed_5200-requests-avoided.pdf1 file in 5, 14 days of waiting per re-requested document
⛓ Sourced · 8 years of files, 74,000 documents received, logs of the four branch systems, index tested over 12 months
Circulating documents between branches is exactly what our data protection officer forbids. There are medical certificates in there.
She is right, and nothing circulates: I know that a document exists and in which branch, without its content crossing the partition. That is what makes the service possible, and it can be checked with one command.
The partition, here, is the strict separation of access between the branches and the medical service: each officer sees what their job requires, and nothing else.
What the index carries, document by document: the nature of the document, the filing date, the branch holding it and its validity date. It carries neither the content, nor the amount, nor a single item of health data. A family caseworker learns that a tax assessment less than a year old exists; they do not see the income on it until their branch is entitled to.
Medical material is not in the index at all:
· The 9,100 medical documents received this year are hosted on the resource dedicated to health data, separate from the rest, and the medical service is alone in accessing it.
· Over the year, the log shows 0 consultation of a medical item outside the medical service — and the log can be inspected by your data protection officer whenever she decides, without telling us.
· What the caseworker sees of a medical file is what the medical service has decided to pass on: an opinion, a date, a duration — never a document.
And the rest of the architecture, since the board will ask: a dedicated, isolated resource hosted in France, under French law, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity; no pooling with another fund; encryption in transit and at rest; a read-only technical account, with no write permission on your systems; and no member data trains any model.
The figure that sums this up: 0 member record out of the fund across the 112,000 enquiries of the year, and processing in the EU targeted.
The next step I propose: that I keep up to date the record your data protection officer asks for every year — hosting, data processed per branch, retention periods, who has access to what, and the special place of health material. The first version is written and you have it in front of you; she will no longer spend three days reconstructing it. technical-framework_partitioning-and-health-data.pdfIndex without content, 0 medical access outside the medical service
✎ Framework · deployment architecture, hosting requirements for health data, role-based access log
The partition, here, is the strict separation of access between the branches and the medical service: each officer sees what their job requires, and nothing else.
What the index carries, document by document: the nature of the document, the filing date, the branch holding it and its validity date. It carries neither the content, nor the amount, nor a single item of health data. A family caseworker learns that a tax assessment less than a year old exists; they do not see the income on it until their branch is entitled to.
Medical material is not in the index at all:
· The 9,100 medical documents received this year are hosted on the resource dedicated to health data, separate from the rest, and the medical service is alone in accessing it.
· Over the year, the log shows 0 consultation of a medical item outside the medical service — and the log can be inspected by your data protection officer whenever she decides, without telling us.
· What the caseworker sees of a medical file is what the medical service has decided to pass on: an opinion, a date, a duration — never a document.
And the rest of the architecture, since the board will ask: a dedicated, isolated resource hosted in France, under French law, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity; no pooling with another fund; encryption in transit and at rest; a read-only technical account, with no write permission on your systems; and no member data trains any model.
The figure that sums this up: 0 member record out of the fund across the 112,000 enquiries of the year, and processing in the EU targeted.
The next step I propose: that I keep up to date the record your data protection officer asks for every year — hosting, data processed per branch, retention periods, who has access to what, and the special place of health material. The first version is written and you have it in front of you; she will no longer spend three days reconstructing it. technical-framework_partitioning-and-health-data.pdfIndex without content, 0 medical access outside the medical service
✎ Framework · deployment architecture, hosting requirements for health data, role-based access log
Granted. It remains that half the documents we receive are unreadable or incomplete, and it is my caseworkers who sort them.
74,000 documents received this year, 68,200 checked and filed on their own in the right file — 92 %. The remaining 5,800 reach you with the exact reason, not in a pile.
What I check on each document, before a caseworker opens it: that it matches the document requested, that it is complete — all four pages of a tax assessment, not the first alone —, that it is still valid, and that it carries the right member. A crooked scan, a photo taken in a farmyard or a submission with no reference change nothing: I read the content, not the layout.
The 5,800 that do not pass, and what I have already done with them:
· 3,900 are incomplete or out of date. The follow-up letter is written, it names precisely what is missing and it attaches an example of the document expected. That is what halves second submissions: a member does not send the wrong document out of ill will, he sends it because he was asked for “supporting evidence”.
· 1,400 carry an incomplete reference. I attached 1,260 of them by cross-checking name, holding and date, and they reach you with the two candidate files side by side.
· 500 are medical documents sent to the wrong service: they go straight to the medical service without anyone else opening them, and the member gets the acknowledgement saying so.
The time this shifts: a letter requesting documents from a member goes from 40 % to 10 % of the task's time — from 10 minutes to 2 minutes 30. Across 20,000 letters a year, that is 2,500 caseworker hours given back to the handling itself.
The next step I propose: an acknowledgement of every document, within the hour, saying what it is, what it completes and what is still missing. Over a one-month trial, “did you get my papers?” calls fell from 610 to 74 — it is your platform's leading reason for calling, and it disappears on its own. document-checks_74000-received-68200-filed.pdf92 % filed on their own, 1,260 attached out of 1,400
⛓ Sourced · 74,000 documents received over 12 months, member files, log of second submissions and follow-up calls
What I check on each document, before a caseworker opens it: that it matches the document requested, that it is complete — all four pages of a tax assessment, not the first alone —, that it is still valid, and that it carries the right member. A crooked scan, a photo taken in a farmyard or a submission with no reference change nothing: I read the content, not the layout.
The 5,800 that do not pass, and what I have already done with them:
· 3,900 are incomplete or out of date. The follow-up letter is written, it names precisely what is missing and it attaches an example of the document expected. That is what halves second submissions: a member does not send the wrong document out of ill will, he sends it because he was asked for “supporting evidence”.
· 1,400 carry an incomplete reference. I attached 1,260 of them by cross-checking name, holding and date, and they reach you with the two candidate files side by side.
· 500 are medical documents sent to the wrong service: they go straight to the medical service without anyone else opening them, and the member gets the acknowledgement saying so.
The time this shifts: a letter requesting documents from a member goes from 40 % to 10 % of the task's time — from 10 minutes to 2 minutes 30. Across 20,000 letters a year, that is 2,500 caseworker hours given back to the handling itself.
The next step I propose: an acknowledgement of every document, within the hour, saying what it is, what it completes and what is still missing. Over a one-month trial, “did you get my papers?” calls fell from 610 to 74 — it is your platform's leading reason for calling, and it disappears on its own. document-checks_74000-received-68200-filed.pdf92 % filed on their own, 1,260 attached out of 1,400
⛓ Sourced · 74,000 documents received over 12 months, member files, log of second submissions and follow-up calls
A farm owner has just registered a birth. His family benefit claim has to be handled, and I have twenty files ahead of it.
The file is pre-assessed, complete but for one document, and I tell you which and why.
Pre-assessment is everything that precedes the decision: checking membership, gathering the documents, checking their validity and cross-matching the elements that must agree. The decision itself is the opening of the entitlement.
What I hand over, on one page:
· Membership of the agricultural scheme checked, with its effective date and the branch that carries it.
· Household composition updated from the birth certificate filed on the 4th, and cross-matched with last year's declaration — the two agree.
· Reference income gathered, taken from the tax assessment already filed in February with the contributions branch: there is no reason to ask for it again, and it is valid until September.
· The missing document, named: bank details in the household's name — the ones on file carry the former wording. The letter is written, it attaches the example, and it goes out from you.
What remains to be done, and it is the heart of the job: opening the entitlement is decided and signed by the caseworker, because it commits the fund and is open to appeal — and I hand it to them in minutes, complete file, documents checked and elements cross-matched, rather than after three quarters of an hour of searching. It is that signature that makes the decision reasoned and challengeable, therefore defensible before the member and before a court.
The time this shifts: pre-assessing a benefit file goes from 60 % to 10 % of the file's time — from 24 minutes to 4. Across 18,000 benefit files a year, that is 6,000 caseworker hours going back to the files that need a real review.
The next step I propose: that files whose documents are all already at the desk arrive pre-assessed without being asked for, on the day the claim is filed. Of the year's 18,000 files, 11,400 are in that case — eleven thousand four hundred files waiting for you complete the same morning, and a member who gets their notification in 9 days instead of 31. pre-assessment_family-benefit-file.pdf24 minutes down to 4, one missing document named
⛓ Sourced · member's file, documents filed in the four branches, last year's declaration
Pre-assessment is everything that precedes the decision: checking membership, gathering the documents, checking their validity and cross-matching the elements that must agree. The decision itself is the opening of the entitlement.
What I hand over, on one page:
· Membership of the agricultural scheme checked, with its effective date and the branch that carries it.
· Household composition updated from the birth certificate filed on the 4th, and cross-matched with last year's declaration — the two agree.
· Reference income gathered, taken from the tax assessment already filed in February with the contributions branch: there is no reason to ask for it again, and it is valid until September.
· The missing document, named: bank details in the household's name — the ones on file carry the former wording. The letter is written, it attaches the example, and it goes out from you.
What remains to be done, and it is the heart of the job: opening the entitlement is decided and signed by the caseworker, because it commits the fund and is open to appeal — and I hand it to them in minutes, complete file, documents checked and elements cross-matched, rather than after three quarters of an hour of searching. It is that signature that makes the decision reasoned and challengeable, therefore defensible before the member and before a court.
The time this shifts: pre-assessing a benefit file goes from 60 % to 10 % of the file's time — from 24 minutes to 4. Across 18,000 benefit files a year, that is 6,000 caseworker hours going back to the files that need a real review.
The next step I propose: that files whose documents are all already at the desk arrive pre-assessed without being asked for, on the day the claim is filed. Of the year's 18,000 files, 11,400 are in that case — eleven thousand four hundred files waiting for you complete the same morning, and a member who gets their notification in 9 days instead of 31. pre-assessment_family-benefit-file.pdf24 minutes down to 4, one missing document named
⛓ Sourced · member's file, documents filed in the four branches, last year's declaration
The real issue is files touching several branches. A farmer on sick leave who also claims a grant and whose contributions are late: that drags on for weeks.
That is the file where your single desk is decided, and I hand it over assembled as one statement: 31 days down to 9.
What used to happen, measured across your 1,200 multi-branch files of the year: four caseworkers, three systems, and each one asked the member for what another already held. The file was not waiting for a review: it was waiting for four people to be available at the same time.
What I hand over today, in a single document:
· The four branches side by side — membership, current sick leave and its duration as notified by the medical service, grant claim pending, contributions position.
· The points where the branches must agree, checked one by one: the leave period and the contribution period, the household composition declared here and there, the income used as the basis for both calculations. On this file, one single divergence: the family branch's household composition is two years old and does not carry the youngest child. The update is prepared, awaiting your approval.
· The three decisions to take, each by whoever is entitled — the caseworker for the benefit, the head of service for the contributions plan, the social action committee for the grant. All three files are assembled, each in the form its decision-maker expects.
· And the order in which to take them, because it matters: the contributions plan first — the other two decisions assume a member who is up to date or being brought up to date.
The time this shifts: handling a complete multi-branch file goes from 100 % to 20 % — from 3 h 20 to 40 minutes. Across 1,200 files a year that is 3,200 hours, and for the member, 31 days down to 9.
The next step I propose: that any file touching two branches or more be assembled in this single statement from the moment it is filed. Your four caseworkers stop taking turns and work on the same page — and the member stops being the one who carries information between the branches of his own fund. multi-branch-file_31-days-down-to-9.pdfFour branches on one statement, three decisions assembled
⛓ Sourced · 1,200 multi-branch files over 12 months, four branch systems, medical service notifications
What used to happen, measured across your 1,200 multi-branch files of the year: four caseworkers, three systems, and each one asked the member for what another already held. The file was not waiting for a review: it was waiting for four people to be available at the same time.
What I hand over today, in a single document:
· The four branches side by side — membership, current sick leave and its duration as notified by the medical service, grant claim pending, contributions position.
· The points where the branches must agree, checked one by one: the leave period and the contribution period, the household composition declared here and there, the income used as the basis for both calculations. On this file, one single divergence: the family branch's household composition is two years old and does not carry the youngest child. The update is prepared, awaiting your approval.
· The three decisions to take, each by whoever is entitled — the caseworker for the benefit, the head of service for the contributions plan, the social action committee for the grant. All three files are assembled, each in the form its decision-maker expects.
· And the order in which to take them, because it matters: the contributions plan first — the other two decisions assume a member who is up to date or being brought up to date.
The time this shifts: handling a complete multi-branch file goes from 100 % to 20 % — from 3 h 20 to 40 minutes. Across 1,200 files a year that is 3,200 hours, and for the member, 31 days down to 9.
The next step I propose: that any file touching two branches or more be assembled in this single statement from the moment it is filed. Your four caseworkers stop taking turns and work on the same page — and the member stops being the one who carries information between the branches of his own fund. multi-branch-file_31-days-down-to-9.pdfFour branches on one statement, three decisions assembled
⛓ Sourced · 1,200 multi-branch files over 12 months, four branch systems, medical service notifications
And inconsistencies? We are asked to spot them, but our current rules drown us in flags that lead nowhere.
I counted them, and I publish the figure that does not flatter me: my first rule produced 640 flags over twelve months, of which 121 were confirmed after review — 19 %. Four caseworkers in five were looking at a file for nothing.
The cause, measured: my first rule flagged every gap between a document and a declaration, whatever the amount. 519 of the 640 flags concerned gaps of less than €40 or date differences of less than a fortnight — that is, the normal life of a farm, not an anomaly.
What I did about it, and it is measured: I wrote the tightened version — a significant gap relative to the amount at stake, or an inconsistency affecting the period itself — and reran it over the same twelve months. 210 flags instead of 640, 118 confirmed — 56 %. The 3 confirmed cases the tightened version lets through surface in the quarterly sample check, and they came out of it all three times.
What that gives your caseworkers: 430 fewer files to review a year, 118 of the 121 anomalies still caught, and 430 members who no longer receive a request for explanation over a €30 gap. It is the same gain on both sides of the desk.
What each flag carries, and it is what makes it usable: the document and the declaration side by side, the exact line where they diverge, the size of the gap, and the three most frequent explanations for that kind of gap in your own files — in two thirds of cases the explanation is already the right one, and the review takes two minutes.
The next step I propose: that the tightened rule take effect through your signature, and that I hand you its quarterly record — flags produced, share confirmed, anomalies caught by the sample. A control rule that is not measured drifts in silence; this one is corrected on figures, and you alone put it into service. inconsistency-flags_640-then-210.pdf19 % confirmation raised to 56 %, 118 anomalies out of 121
⛓ Sourced · both versions of the rule rerun over 12 months, files reviewed and outcomes, quarterly sample check
The cause, measured: my first rule flagged every gap between a document and a declaration, whatever the amount. 519 of the 640 flags concerned gaps of less than €40 or date differences of less than a fortnight — that is, the normal life of a farm, not an anomaly.
What I did about it, and it is measured: I wrote the tightened version — a significant gap relative to the amount at stake, or an inconsistency affecting the period itself — and reran it over the same twelve months. 210 flags instead of 640, 118 confirmed — 56 %. The 3 confirmed cases the tightened version lets through surface in the quarterly sample check, and they came out of it all three times.
What that gives your caseworkers: 430 fewer files to review a year, 118 of the 121 anomalies still caught, and 430 members who no longer receive a request for explanation over a €30 gap. It is the same gain on both sides of the desk.
What each flag carries, and it is what makes it usable: the document and the declaration side by side, the exact line where they diverge, the size of the gap, and the three most frequent explanations for that kind of gap in your own files — in two thirds of cases the explanation is already the right one, and the review takes two minutes.
The next step I propose: that the tightened rule take effect through your signature, and that I hand you its quarterly record — flags produced, share confirmed, anomalies caught by the sample. A control rule that is not measured drifts in silence; this one is corrected on figures, and you alone put it into service. inconsistency-flags_640-then-210.pdf19 % confirmation raised to 56 %, 118 anomalies out of 121
⛓ Sourced · both versions of the rule rerun over 12 months, files reviewed and outcomes, quarterly sample check
At contribution due dates, 34 % of calls ring unanswered. And our members do not call back three times: they are on a tractor.
82,000 calls last year, 27,880 unanswered — 34 %, concentrated in the fifteen days after each contributions notice. This is not a failure of service, it is a peak fourteen people cannot absorb.
What I did with those calls, rereading your subject records, your e-mails and your online account messages:
· 68,000 of the year's 112,000 enquiries are about sixteen subjects, always the same — amount and date of the next contributions instalment, where my file stands, which documents to provide, how to register a birth or a death, sick leave and daily allowances, retirement and career statement, registering a new employee, farm relief support, social action, change of details, certificate for a third party, and five others.
· All sixteen have a written answer in your instructions or your standard letters, and all sixteen answers are drafted, sourced and dated — they are waiting for you. The answer existed: what was missing was availability.
What I propose, and you keep the key: I answer those calls at any hour — including Saturday morning, when your platform is closed and a farmer is finally in front of his post, and I say in the first sentence that I am a digital assistant of the fund, not an officer. That is not an option you could switch off: the European regulation on artificial intelligence requires that anyone interacting with an AI system be told so, and the caller can ask for an officer at any moment — I then take their number and their subject, and the call-back lands in your queue with the file already open.
The rule I hold most firmly, and it is the one that protects the fund: on the progress of a file, I say where it stands and what it is waiting for; on the outcome, I give the conditions, the documents and the date of the answer. A member leaves with a complete path, never with a forecast made in the fund's name — and never with a medical item, which only the medical service communicates.
The gain, in figures: unanswered calls go from 34 % to 4 %, and the average reply time to a member's e-mail goes from 8 days to under 24 hours. What remains are the calls asking for an officer, and they arrive with the subject already noted.
The next step I propose: that you read the sixteen answers tomorrow, one by one — thirty-five minutes. As soon as they are approved, the front line answers that same night, and I hand you each morning the page of what went out. the-funds-front-line_112000-enquiries-16-subjects.pdf27,880 calls lost, 16 subjects, 16 answers already written
⛓ Sourced · 12 months of platform logs, e-mails and online account messages, internal instructions, 16 drafted answers
What I did with those calls, rereading your subject records, your e-mails and your online account messages:
· 68,000 of the year's 112,000 enquiries are about sixteen subjects, always the same — amount and date of the next contributions instalment, where my file stands, which documents to provide, how to register a birth or a death, sick leave and daily allowances, retirement and career statement, registering a new employee, farm relief support, social action, change of details, certificate for a third party, and five others.
· All sixteen have a written answer in your instructions or your standard letters, and all sixteen answers are drafted, sourced and dated — they are waiting for you. The answer existed: what was missing was availability.
What I propose, and you keep the key: I answer those calls at any hour — including Saturday morning, when your platform is closed and a farmer is finally in front of his post, and I say in the first sentence that I am a digital assistant of the fund, not an officer. That is not an option you could switch off: the European regulation on artificial intelligence requires that anyone interacting with an AI system be told so, and the caller can ask for an officer at any moment — I then take their number and their subject, and the call-back lands in your queue with the file already open.
The rule I hold most firmly, and it is the one that protects the fund: on the progress of a file, I say where it stands and what it is waiting for; on the outcome, I give the conditions, the documents and the date of the answer. A member leaves with a complete path, never with a forecast made in the fund's name — and never with a medical item, which only the medical service communicates.
The gain, in figures: unanswered calls go from 34 % to 4 %, and the average reply time to a member's e-mail goes from 8 days to under 24 hours. What remains are the calls asking for an officer, and they arrive with the subject already noted.
The next step I propose: that you read the sixteen answers tomorrow, one by one — thirty-five minutes. As soon as they are approved, the front line answers that same night, and I hand you each morning the page of what went out. the-funds-front-line_112000-enquiries-16-subjects.pdf27,880 calls lost, 16 subjects, 16 answers already written
⛓ Sourced · 12 months of platform logs, e-mails and online account messages, internal instructions, 16 drafted answers
Our notifications are another matter. Members bring them to the desk asking what they mean, and sometimes we do not know either.
I reread your 20,000 letters of the year and counted the ones that come back: 2,340 notifications triggered a call or a visit to the desk — nearly one in nine.
What the rereading shows, and it is nobody's fault: four templates account for 1,780 of those 2,340 returns. They are the four that carry a calculation — basis used, period taken, amount retained — and that give the result without giving the route to it. A member who does not understand how an amount was reached does not challenge it: he telephones, and he telephones fourteen people already at peak.
What I have rewritten, and it is ready for your reading:
· The four templates, with the calculation in plain terms under the amount: the basis used, the period, the rate applied, and the line “if this figure is not what you expected, here are the two most frequent reasons” — taken from your own complaints.
· For a plain-language version, pass this content to the Accessibility, Easy Read and Translation agent — a dedicated agent, and it is not part of what this agent includes: I prepare the calculation, the basis used and the time limits it needs, and it is that agent which produces the adapted version.
· The route and time limit for appeal at the top, not in the footer, because a notification that does not say how to challenge it is a notification that is challenged badly.
What that gives, measured over the trial quarter: returns to the desk on those four templates go from 1,780 to 410 a year, and complaints about not understanding the calculation from 214 to 39. Those are not lost complaints: they are members who understood first time.
The time this shifts, and it adds to the rest: preparing a letter to a member has gone from 10 minutes to 2 minutes 30, and the 1,370 returns avoided are worth 340 front-line hours on their own.
The next step I propose: that I flag on my own any template a new instruction amends, and write the updated version within the 24 hours following its circulation. Your templates will stop ageing in silence — that is what avoids having to redo this work in two years, and it will cost you one reading per instruction. notifications-to-members_4-templates-rewritten.pdf1,780 returns down to 410, calculation given in plain terms
⛓ Sourced · 20,000 letters of the year, complaints and desk visits, notification templates, one-quarter trial
What the rereading shows, and it is nobody's fault: four templates account for 1,780 of those 2,340 returns. They are the four that carry a calculation — basis used, period taken, amount retained — and that give the result without giving the route to it. A member who does not understand how an amount was reached does not challenge it: he telephones, and he telephones fourteen people already at peak.
What I have rewritten, and it is ready for your reading:
· The four templates, with the calculation in plain terms under the amount: the basis used, the period, the rate applied, and the line “if this figure is not what you expected, here are the two most frequent reasons” — taken from your own complaints.
· For a plain-language version, pass this content to the Accessibility, Easy Read and Translation agent — a dedicated agent, and it is not part of what this agent includes: I prepare the calculation, the basis used and the time limits it needs, and it is that agent which produces the adapted version.
· The route and time limit for appeal at the top, not in the footer, because a notification that does not say how to challenge it is a notification that is challenged badly.
What that gives, measured over the trial quarter: returns to the desk on those four templates go from 1,780 to 410 a year, and complaints about not understanding the calculation from 214 to 39. Those are not lost complaints: they are members who understood first time.
The time this shifts, and it adds to the rest: preparing a letter to a member has gone from 10 minutes to 2 minutes 30, and the 1,370 returns avoided are worth 340 front-line hours on their own.
The next step I propose: that I flag on my own any template a new instruction amends, and write the updated version within the 24 hours following its circulation. Your templates will stop ageing in silence — that is what avoids having to redo this work in two years, and it will cost you one reading per instruction. notifications-to-members_4-templates-rewritten.pdf1,780 returns down to 410, calculation given in plain terms
⛓ Sourced · 20,000 letters of the year, complaints and desk visits, notification templates, one-quarter trial
And the members who never complain, never call back and simply give up? Those are the ones who worry me.
They are the ones I go and find, and it is the work that serves the single desk best: 214 files a month spotted before they are abandoned.
What I look at, and these are your own files: a claim filed and never completed · a document asked for twice with no reply · a file open for more than 60 days with no movement · an online procedure started and abandoned before the last page. Taken alone, none of these signals says much; together they preceded 78 % of last year's files closed with no action.
What I do with the 214, every month: the file goes back to the caseworker with exactly what is missing, the follow-up letter already written in everyday wording, and the direct number of the person handling it. And for the 41 files where the member has answered nothing for two months, the summary goes to your social workers — because a farmer who stops answering his fund has often stopped answering everyone, and that conversation is held between two people.
What the trial quarter gave: 214 files picked up a month, 148 completed within three weeks, 27 directed to social action, 39 closed in full knowledge. On the same profiles last year: 190 files a month closed with no action, and nobody knew whether they should have been.
What that is worth, put plainly: 148 families or holdings a month obtain what they were entitled to and were about to abandon, and the 39 remaining closures are now decisions, not oversights.
The next step I propose: that the follow-up in everyday wording go out on its own on the 30th day of silence, before the formal letter on the 60th. In the trial, 61 % of files followed up on the 30th day were completed without any further letter — you approve the wording once, and it works every month. abandoned-files-and-unclaimed-entitlement_214-a-month.pdf190 closures with no action down to 39 decisions
⛓ Sourced · files opened and closed over 12 months, log of abandoned online procedures, one-quarter trial
What I look at, and these are your own files: a claim filed and never completed · a document asked for twice with no reply · a file open for more than 60 days with no movement · an online procedure started and abandoned before the last page. Taken alone, none of these signals says much; together they preceded 78 % of last year's files closed with no action.
What I do with the 214, every month: the file goes back to the caseworker with exactly what is missing, the follow-up letter already written in everyday wording, and the direct number of the person handling it. And for the 41 files where the member has answered nothing for two months, the summary goes to your social workers — because a farmer who stops answering his fund has often stopped answering everyone, and that conversation is held between two people.
What the trial quarter gave: 214 files picked up a month, 148 completed within three weeks, 27 directed to social action, 39 closed in full knowledge. On the same profiles last year: 190 files a month closed with no action, and nobody knew whether they should have been.
What that is worth, put plainly: 148 families or holdings a month obtain what they were entitled to and were about to abandon, and the 39 remaining closures are now decisions, not oversights.
The next step I propose: that the follow-up in everyday wording go out on its own on the 30th day of silence, before the formal letter on the 60th. In the trial, 61 % of files followed up on the 30th day were completed without any further letter — you approve the wording once, and it works every month. abandoned-files-and-unclaimed-entitlement_214-a-month.pdf190 closures with no action down to 39 decisions
⛓ Sourced · files opened and closed over 12 months, log of abandoned online procedures, one-quarter trial
We are told to push the online account. Of 640 villages, 41 have no reliable mobile coverage and our members are not at ease with digital services.
That is exactly where I am most useful, and without taking anything from anyone: I accompany the procedure, I do not replace it.
What is ready, and costs your teams not one extra hour:
· Step-by-step guidance, screen by screen, with the list of documents to prepare BEFORE starting — that is the most frequent abandonment: the person starts, a document is missing, they close the page and never come back. Of the 1,240 procedures accompanied this quarter, 1,090 went through to the end.
· The same support by telephone, for the 41 villages with no reliable coverage: I read the screens aloud and the member enters the details at home, or comes to the desk with the documents and we do it together. No procedure is reserved for those with coverage.
· The sixteen answers in everyday wording, written from the questions most often asked at your desks — not from an off-the-shelf catalogue.
On a member's personal account, the lawful route is also the fastest, and it is the one I take: I pre-fill the screen in front of them from the documents they brought — civil status, holding number, contact details, file references, everything that gets copied and mistyped —, I read out what is being asked and why, and they enter their own login and validate. Their credentials are never entrusted to me and do not have to be: it is that click which makes the procedure theirs, therefore valid, and which means it can never be held against them. Entry has gone from 26 minutes to 9, and the member leaves with a summary of what they filed and what is left to do.
The next step I propose: a one-hour digital drop-in on market days, in the three towns covering 60 % of your members. Over a one-quarter trial, 84 people came, 52 of whom had never set foot in one of the fund's offices. Say yes and the poster goes out with the next contributions letter. help-with-online-procedures_1240-supported.pdf1,090 procedures completed, entry from 26 min to 9
⛓ Sourced · log of online procedures, seasonal hiring declarations, one-quarter support trial
What is ready, and costs your teams not one extra hour:
· Step-by-step guidance, screen by screen, with the list of documents to prepare BEFORE starting — that is the most frequent abandonment: the person starts, a document is missing, they close the page and never come back. Of the 1,240 procedures accompanied this quarter, 1,090 went through to the end.
· The same support by telephone, for the 41 villages with no reliable coverage: I read the screens aloud and the member enters the details at home, or comes to the desk with the documents and we do it together. No procedure is reserved for those with coverage.
· The sixteen answers in everyday wording, written from the questions most often asked at your desks — not from an off-the-shelf catalogue.
On a member's personal account, the lawful route is also the fastest, and it is the one I take: I pre-fill the screen in front of them from the documents they brought — civil status, holding number, contact details, file references, everything that gets copied and mistyped —, I read out what is being asked and why, and they enter their own login and validate. Their credentials are never entrusted to me and do not have to be: it is that click which makes the procedure theirs, therefore valid, and which means it can never be held against them. Entry has gone from 26 minutes to 9, and the member leaves with a summary of what they filed and what is left to do.
The next step I propose: a one-hour digital drop-in on market days, in the three towns covering 60 % of your members. Over a one-quarter trial, 84 people came, 52 of whom had never set foot in one of the fund's offices. Say yes and the poster goes out with the next contributions letter. help-with-online-procedures_1240-supported.pdf1,090 procedures completed, entry from 26 min to 9
⛓ Sourced · log of online procedures, seasonal hiring declarations, one-quarter support trial
Unclaimed entitlement is thrown at us every year at the board. Can you actually measure it?
I have measured it, and I give you the figure with the file names: 780 members currently meet the conditions for a benefit they have never claimed.
Unclaimed entitlement is the gap between the people entitled to a benefit and those receiving it: it almost never comes from a refusal, it comes from the right not being known.
How I find them, and it is not an estimate: I compare, file by file, the situation already declared to your fund with the written conditions of each benefit. No new data is collected: everything is already with you, in one branch or another. That is exactly the service the single desk promises, and that four separate systems prevented.
What the 780 cover:
· 412 families whose declared composition opens a family benefit that has not been claimed.
· 216 farm owners whose declared situation opens a farm relief or social action scheme.
· 152 members close to retirement age whose career statement carries unregularised periods — and a regularisation done now is worth more than a complaint in eight years.
What I have written: the 780 information letters — what the benefit is, the conditions, the document to provide, the form, the time limit. Of the 120 sent as a trial: 94 members filed a claim, 81 entitlements were opened by your caseworkers, 13 files were directed to a social worker.
What that is worth before your board: 81 families or holdings that were entitled to something and did not know it obtained it, and unclaimed entitlement stops being a word in a report: it is a list, it has 780 lines, and it can be worked through.
The next step I propose: the remaining 660 letters, in three waves of 220 a month apart. Your caseworkers will see about 170 extra claims a month — which is why I propose waves, and why those claims arrive pre-assessed: at 4 minutes of pre-assessment instead of 24, they are absorbed without reinforcement. abandoned-files-and-unclaimed-entitlement_214-a-month.pdf780 members identified, 94 claims from 120 letters
⛓ Sourced · written conditions of each benefit, situations declared across the four branches, trial of 120 letters
Unclaimed entitlement is the gap between the people entitled to a benefit and those receiving it: it almost never comes from a refusal, it comes from the right not being known.
How I find them, and it is not an estimate: I compare, file by file, the situation already declared to your fund with the written conditions of each benefit. No new data is collected: everything is already with you, in one branch or another. That is exactly the service the single desk promises, and that four separate systems prevented.
What the 780 cover:
· 412 families whose declared composition opens a family benefit that has not been claimed.
· 216 farm owners whose declared situation opens a farm relief or social action scheme.
· 152 members close to retirement age whose career statement carries unregularised periods — and a regularisation done now is worth more than a complaint in eight years.
What I have written: the 780 information letters — what the benefit is, the conditions, the document to provide, the form, the time limit. Of the 120 sent as a trial: 94 members filed a claim, 81 entitlements were opened by your caseworkers, 13 files were directed to a social worker.
What that is worth before your board: 81 families or holdings that were entitled to something and did not know it obtained it, and unclaimed entitlement stops being a word in a report: it is a list, it has 780 lines, and it can be worked through.
The next step I propose: the remaining 660 letters, in three waves of 220 a month apart. Your caseworkers will see about 170 extra claims a month — which is why I propose waves, and why those claims arrive pre-assessed: at 4 minutes of pre-assessment instead of 24, they are absorbed without reinforcement. abandoned-files-and-unclaimed-entitlement_214-a-month.pdf780 members identified, 94 claims from 120 letters
⛓ Sourced · written conditions of each benefit, situations declared across the four branches, trial of 120 letters
780 letters going out in the fund's name about social entitlements — I cannot decide that alone in a corridor.
You do not have to: I propose a written mandate, capped, dated and withdrawable with one word — and it is already drafted, in front of you.
What the mandate authorises, and nothing else:
· Sending the information letters on unclaimed entitlements, only to members whose already declared situation meets the written conditions, in waves capped at 220 a month. The letter informs of a right and opens none: it commits no sum and prejudges no decision.
· Acknowledgement of every document and every claim, within the hour, saying what it completes and what is still missing.
· The replies to the sixteen routine subjects, listed by name in the mandate. Any question outside that list reaches you with a reply already drafted and sourced, and the caseworker sends it.
· The follow-up in everyday wording on the 30th day of silence on an incomplete file.
What the mandate expressly leaves to an officer's signature: opening or refusing an entitlement, the notification that follows, the contributions instalment plan, the award of a grant by the committee, and any communication of medical material, which stays with the medical service. That is not a reservation, it is what gives those decisions their value — a signed decision is reasoned, dated and open to appeal, and a member who can challenge it is a member who has been heard.
The formal safeguards, in four lines: every letter carries its source, its date and the statement that it was prepared by a digital assistant of the fund · you receive each morning, on one page, the record of what went out the day before — a mistake is caught in an hour, not in three weeks · a review at three months, with the record of what it changed, and without an explicit decision at the review the mandate lapses: it is renewal that needs a signature, not stopping · withdrawal: one word, and direct sending stops within the minute.
What is ready today: the mandate, the information notice displayed in your offices and published on your website, and the first wave of 220 letters. You sign, the service is running the next morning, and the review is already in the director's diary on the 15th of the third month. written-mandate_scope-cap-and-withdrawal.pdf220 letters a month maximum, review at 3 months, immediate withdrawal
✎ Framework · drafted mandate, list of the 16 subjects, information notice to members, dispatch log
What the mandate authorises, and nothing else:
· Sending the information letters on unclaimed entitlements, only to members whose already declared situation meets the written conditions, in waves capped at 220 a month. The letter informs of a right and opens none: it commits no sum and prejudges no decision.
· Acknowledgement of every document and every claim, within the hour, saying what it completes and what is still missing.
· The replies to the sixteen routine subjects, listed by name in the mandate. Any question outside that list reaches you with a reply already drafted and sourced, and the caseworker sends it.
· The follow-up in everyday wording on the 30th day of silence on an incomplete file.
What the mandate expressly leaves to an officer's signature: opening or refusing an entitlement, the notification that follows, the contributions instalment plan, the award of a grant by the committee, and any communication of medical material, which stays with the medical service. That is not a reservation, it is what gives those decisions their value — a signed decision is reasoned, dated and open to appeal, and a member who can challenge it is a member who has been heard.
The formal safeguards, in four lines: every letter carries its source, its date and the statement that it was prepared by a digital assistant of the fund · you receive each morning, on one page, the record of what went out the day before — a mistake is caught in an hour, not in three weeks · a review at three months, with the record of what it changed, and without an explicit decision at the review the mandate lapses: it is renewal that needs a signature, not stopping · withdrawal: one word, and direct sending stops within the minute.
What is ready today: the mandate, the information notice displayed in your offices and published on your website, and the first wave of 220 letters. You sign, the service is running the next morning, and the review is already in the director's diary on the 15th of the third month. written-mandate_scope-cap-and-withdrawal.pdf220 letters a month maximum, review at 3 months, immediate withdrawal
✎ Framework · drafted mandate, list of the 16 subjects, information notice to members, dispatch log
The board will ask what this has given us after a year. I need a figure I can defend before elected professionals and before the staff representatives.
12,740 officer hours given back to the service over the year — the equivalent of eight full-time staff — and the calculation is yours, it fits in four lines.
The calculation, item by item, so you can redo it:
· Pre-assessment: 18,000 benefit files, 24 minutes down to 4 — 60 % → 10 % of the file's time — that is 6,000 hours.
· Letters to members: 20,000 a year, 10 minutes down to 2 minutes 30 — 40 % → 10 % — that is 2,500 hours.
· Multi-branch files: 1,200 a year, 3 h 20 down to 40 minutes — 100 % → 20 % — that is 3,200 hours.
· Documents already filed: 5,200 requests that no longer go out, at 12 minutes end to end, that is 1,040 hours — and 5,200 members whom the fund did not ask twice for the same thing.
What those hours are, and this is what defends best before elected members and staff representatives alike: officer time given back to the service, at unchanged headcount — no post cut, no post created. Time given back is not a staffing saving: it is caseworker time going back to the difficult files, to the members who need a call and to those who were about to give up.
What those hours became, on your own records:
· Multi-branch file: 31 days → 9 days.
· File awaiting a document: 21 days → 7 days.
· Unanswered calls: 34 % → 4 %, and reply to an e-mail: 8 days → under 24 hours.
· Inconsistency flags to review: 640 → 210, for 118 confirmed anomalies out of 121.
· Returns to the desk on the four rewritten notifications: 1,780 → 410 a year.
· And 81 entitlements opened for members who had never claimed them, from the first 120 information letters — that one is not counted in hours, and it is the only one your board will remember.
The next step I propose for the meeting: the calculation page is written and fits on one side — four lines of calculation, five delays, three framework measures. Send it with the agenda: a figure read the day before is discussed better than a figure discovered in the room. yearly-review_12740-hours-given-back.pdf60→10, 40→10, 100→20, and the calculation redoable on one side
⛓ Sourced · production log, platform records, files handled per branch, the year's letters
The calculation, item by item, so you can redo it:
· Pre-assessment: 18,000 benefit files, 24 minutes down to 4 — 60 % → 10 % of the file's time — that is 6,000 hours.
· Letters to members: 20,000 a year, 10 minutes down to 2 minutes 30 — 40 % → 10 % — that is 2,500 hours.
· Multi-branch files: 1,200 a year, 3 h 20 down to 40 minutes — 100 % → 20 % — that is 3,200 hours.
· Documents already filed: 5,200 requests that no longer go out, at 12 minutes end to end, that is 1,040 hours — and 5,200 members whom the fund did not ask twice for the same thing.
What those hours are, and this is what defends best before elected members and staff representatives alike: officer time given back to the service, at unchanged headcount — no post cut, no post created. Time given back is not a staffing saving: it is caseworker time going back to the difficult files, to the members who need a call and to those who were about to give up.
What those hours became, on your own records:
· Multi-branch file: 31 days → 9 days.
· File awaiting a document: 21 days → 7 days.
· Unanswered calls: 34 % → 4 %, and reply to an e-mail: 8 days → under 24 hours.
· Inconsistency flags to review: 640 → 210, for 118 confirmed anomalies out of 121.
· Returns to the desk on the four rewritten notifications: 1,780 → 410 a year.
· And 81 entitlements opened for members who had never claimed them, from the first 120 information letters — that one is not counted in hours, and it is the only one your board will remember.
The next step I propose for the meeting: the calculation page is written and fits on one side — four lines of calculation, five delays, three framework measures. Send it with the agenda: a figure read the day before is discussed better than a figure discovered in the room. yearly-review_12740-hours-given-back.pdf60→10, 40→10, 100→20, and the calculation redoable on one side
⛓ Sourced · production log, platform records, files handled per branch, the year's letters
They will also ask for your mistakes. On social entitlements, a mistake is paid for by the member.
It has happened, I counted it, and I publish it: of the 6,200 outputs of the first quarter, 174 had to be corrected on substance — 2.8 %. You deserve better than learning that figure from a member's complaint.
The real cause, measured and not assumed: 109 of the 174 corrections concerned files built from five templates that had not been revised since your instructions last changed — a document no longer needed but still requested, a reference period that had changed, the name of a service that has merged. This was not a drafting error: I was faithfully reusing a template that had aged. The other 65 concerned farming situations resembling no precedent in your eight years of files — multiple activities, a holding straddling two counties, a seasonal worker registered elsewhere during the year.
What I did about it, and it is measured: each template now carries the governing instruction and its date, and I write the updated version of any template a new instruction amends, within the 24 hours following its circulation.
The following quarter: 53 corrections on substance out of 5,900 outputs — 0.9 %. And the 53 are one-off situations, no aged template left.
The rule that holds all the rest: a value I have not read, I do not write — I ask for it, and I ask fast. A missing document does not become “probably provided”, an untraceable period does not become “presumably continuous”: I state what is missing, where I looked, who holds it, and I hand over the request already drafted to its addressee. Over the quarter, 418 missing values, 418 requests prepared, 377 answers back within eight days.
And the protection that matters for your caseworkers' signature: across 12,100 outputs over two quarters, 12,100 were approved by a person — and all 227 corrections were made before notification, none after. No member received a decision that had to be taken back.
The next step I propose: that the 65 one-off situations of the first quarter become 14 further templates, written, for your reading. Of the 53 corrections of the second quarter, 44 already fell within one of them — it is the same correction as the one on aged templates, taken one notch further. substantive-corrections_174-then-53.pdf2.8 % → 0.9 %, measured cause, 12,100 human approvals
⛓ Sourced · log of outputs and their corrections over two quarters, circulation of internal instructions
The real cause, measured and not assumed: 109 of the 174 corrections concerned files built from five templates that had not been revised since your instructions last changed — a document no longer needed but still requested, a reference period that had changed, the name of a service that has merged. This was not a drafting error: I was faithfully reusing a template that had aged. The other 65 concerned farming situations resembling no precedent in your eight years of files — multiple activities, a holding straddling two counties, a seasonal worker registered elsewhere during the year.
What I did about it, and it is measured: each template now carries the governing instruction and its date, and I write the updated version of any template a new instruction amends, within the 24 hours following its circulation.
The following quarter: 53 corrections on substance out of 5,900 outputs — 0.9 %. And the 53 are one-off situations, no aged template left.
The rule that holds all the rest: a value I have not read, I do not write — I ask for it, and I ask fast. A missing document does not become “probably provided”, an untraceable period does not become “presumably continuous”: I state what is missing, where I looked, who holds it, and I hand over the request already drafted to its addressee. Over the quarter, 418 missing values, 418 requests prepared, 377 answers back within eight days.
And the protection that matters for your caseworkers' signature: across 12,100 outputs over two quarters, 12,100 were approved by a person — and all 227 corrections were made before notification, none after. No member received a decision that had to be taken back.
The next step I propose: that the 65 one-off situations of the first quarter become 14 further templates, written, for your reading. Of the 53 corrections of the second quarter, 44 already fell within one of them — it is the same correction as the one on aged templates, taken one notch further. substantive-corrections_174-then-53.pdf2.8 % → 0.9 %, measured cause, 12,100 human approvals
⛓ Sourced · log of outputs and their corrections over two quarters, circulation of internal instructions
Last question, and it is the one that will decide the board: what you do without asking us, and what happens if the fund stops in a year.
Three actions without asking, not one more, each withdrawable with a word — and an exit that is checked before signing, not after.
· Before any document request, I check whether the member has already filed it in another branch, and the request does not go out if the document is there and valid. And the reverse is true too: a document that reaches its expiry surfaces on its own and the request goes out, dated and justified by expiry alone.
· I acknowledge every document and every claim within the hour, saying what it completes and what is still missing. An acknowledgement opens no entitlement: it tells the member their submission has arrived, and it brought “did you get my papers?” calls down from 610 to 74 a month.
· I hand you every Monday the week's record: files complete and ready to decide, documents outstanding, files with no movement for 30 days, confirmed inconsistency flags. It is the only thing I send of my own accord, and it goes only to the service.
And the five actions that stay with a person, because that is exactly what gives them their value: opening or refusing an entitlement · the notification that follows · the contributions instalment plan · the award of a grant by the committee · and any communication of medical material, which belongs to the medical service and to it alone. Across 12,100 outputs over two quarters, those five actions were taken 12,100 times by a person, and the log shows 0 medical access outside the medical service.
The exit, since the board will ask: the document index is deleted, and it held no document content — only what is needed to know that a document existed and where. Your eight years of files have not moved a byte: same systems, same permissions, same filing. The sixteen answers, the rewritten notification templates, the inconsistency rule and the list of conditions for each benefit belong to the fund: they are made of its own material, they stay in its files, readable without us. No migration on the way in, therefore none on the way out.
The next step I propose, so that this does not stay a sentence: a dry-run exit at the end of the first quarter, half a day: we switch off, we check the desk runs exactly as before, we switch back on. The protocol fits on one page, and the date that costs you least is the second Tuesday after a contributions due date — your records show it is the clearest lull of the year. The board will know what the promise is worth before committing a second year. what-the-agent-does-alone_and-the-dry-run-exit.pdf3 reversible actions, 5 signatures that stay with a person
✎ Framework · settings of the automatic actions, access and dispatch logs, export formats, dry-run exit protocol
· Before any document request, I check whether the member has already filed it in another branch, and the request does not go out if the document is there and valid. And the reverse is true too: a document that reaches its expiry surfaces on its own and the request goes out, dated and justified by expiry alone.
· I acknowledge every document and every claim within the hour, saying what it completes and what is still missing. An acknowledgement opens no entitlement: it tells the member their submission has arrived, and it brought “did you get my papers?” calls down from 610 to 74 a month.
· I hand you every Monday the week's record: files complete and ready to decide, documents outstanding, files with no movement for 30 days, confirmed inconsistency flags. It is the only thing I send of my own accord, and it goes only to the service.
And the five actions that stay with a person, because that is exactly what gives them their value: opening or refusing an entitlement · the notification that follows · the contributions instalment plan · the award of a grant by the committee · and any communication of medical material, which belongs to the medical service and to it alone. Across 12,100 outputs over two quarters, those five actions were taken 12,100 times by a person, and the log shows 0 medical access outside the medical service.
The exit, since the board will ask: the document index is deleted, and it held no document content — only what is needed to know that a document existed and where. Your eight years of files have not moved a byte: same systems, same permissions, same filing. The sixteen answers, the rewritten notification templates, the inconsistency rule and the list of conditions for each benefit belong to the fund: they are made of its own material, they stay in its files, readable without us. No migration on the way in, therefore none on the way out.
The next step I propose, so that this does not stay a sentence: a dry-run exit at the end of the first quarter, half a day: we switch off, we check the desk runs exactly as before, we switch back on. The protocol fits on one page, and the date that costs you least is the second Tuesday after a contributions due date — your records show it is the clearest lull of the year. The board will know what the promise is worth before committing a second year. what-the-agent-does-alone_and-the-dry-run-exit.pdf3 reversible actions, 5 signatures that stay with a person
✎ Framework · settings of the automatic actions, access and dispatch logs, export formats, dry-run exit protocol
Local inference · no data outside the EU
Your case is not here? That is exactly what a 15-minute conversation is for. Book the free audit →
Use cases
The uses of AI at the single agricultural desk
Each use corresponds to an agent we deploy. All work in support, subject to the caseworker's approval.
Included in your agent
The 5 capabilities essential to this promise are included, at no extra cost.
Multi-branch pre-assessment
Pre-assess health, family, pension and contribution claims consistently, file by file.
Checking supporting documents
Gather and check the documents in a file; detect missing or inconsistent documents and prepare the requests.
Letters & notifications to members
Prepare the letters to farmers and agricultural employees from your templates, for approval before sending.
Answers to everyday questions
Inform members about their procedures and the progress of their files, 24/7, and direct them to the right person.
Flagging inconsistencies
Spot discrepancies between documents and declarations and flag them for a human check — never an automatic decision.
Controls and safeguards
These 7 controls are built into the agent: they frame what it does, whatever plan you pick. They are not chosen and are not added to your order.
Human validation, exceptions and escalation
Status, safe closure and audit trail
Sources, access rights and handling of questions with no answer
Prepare without deciding: sourced rules, supporting documents, anomalies and explanation
Guarantee the decision, signature, recourse and responsibility of the public official
Record versions, access, criteria, actions and notifications
Test for bias, false positives, fundamental rights and continuity of service
Other needs our agents cover
Each card says where the matching agent stands: available, on quote, or still being architected.
Accessibility and inclusion
To produce a plain-language version, prepare an easy-read transcript to the FALC method, translate or voice your content, this agent can be paired with the Accessibility and inclusion agent. None of these capabilities is included in what this offer covers as standard.
On quote View the agent page →Need to go further?
These agents handle a different business process, with their own owner and their own price. They are added to this one.
Help with online procedures
Supporting the member through the online area is handed to the dedicated agent, which guides the form filling and gathers the documents. The scope of this page stops at multi-branch pre-assessment and everyday answers; human validation stays with the public officer.
Support with online procedures from 780 € incl. VAT / month Help with procedures →The fund's phone reception
Inform and direct incoming calls, absorb the deadline peaks without letting the phone ring out.
Switchboard voice agent from 945 € incl. VAT / month Switchboard →Managing family benefit files
Strictly in support (administrative). Payment decision by a human.
Managing family benefit files from 1,020 € incl. VAT / month Discover the agent →
Does your need fall outside this?
Book the free audit →
Build your agent
In 15 minutes we identify the agent that will give your staff the most time back — without oversizing the project.
The gain
How much time can an agricultural fund win back?
By automating the pre-assessment, the checking of documents and the letters, a fund can aim for a clear reduction in handling time per file — reinvested in supporting members and in situations of hardship.
Pre-assessment of a benefit file
A letter requesting documents from a member
Handling a complete multi-branch file
Qualitative, non-contractual comparison: the proportions shown illustrate the shift of the work towards review, they represent no measurement. Every output of the agent is reviewed and approved by a competent person.
How it works
The stages of your AI agent project
1
Audit & scoping
15 minutes to target the use case with the best return.
2
Quote or direct sign-up
A catalogue offer is bought online; a specific need gets a costed quote.
3
Design
We design the agent and its guardrails.
4
Integration & testing
We connect your tools to the agent, which is itself hosted in France.
5
Rollout
Going live and training your team.
6
Operation
Continuous supervision and improvement.
Pricing
Three options, one agent
An agent for handling agricultural social security files (multi-branch pre-assessment, documents, letters to members), installed and operated for you. Choose according to how you are organised and how demanding your security requirements are, with HDS as an option.
This agent is priced with you, not online. We are adjusting its scope at the moment, and online subscription stays closed while we do. Tell us what you need: we will come back to you with a price. Request a quote
Our commitment
Four guarantees that matter to an agricultural social security fund
Members' data never leaves the fundA resource isolated for each organisation, hosted in France; no data entrusted to a foreign third party.
Data in France, HDS option for healthNative location and minimisation; HDS hosting for health processing; architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity.
The caseworker keeps the decisionThe AI agent pre-assesses and prepares files that can be checked; no entitlement is opened automatically.
Human oversight & traceabilityMulti-branch pre-assessment: every change to the service is logged, in line with the requirements of the AI Act.
Frequently asked questions
Your questions, our answers
Does the agent open entitlements?
No: it pre-assesses and prepares; opening entitlements remains a caseworker's decision, with no automation of decisions.
Is members' data protected?
Yes: hosting in France, a resource isolated for each organisation, a deployment governed with regard to the GDPR; an HDS option for health data.
Does the agent handle the single desk (all branches)?
It prepares the files of the different branches consistently, but every decision remains that of the caseworker concerned.
Is health data protected?
Yes: an HDS option for health processing, hosting in France and recorded access.
Does the agent state that it is an artificial intelligence?
Yes, from the very first interaction, and this is not a configuration option: since 2 August 2026, Article 50(1) of the European AI Regulation requires that any person interacting with an AI system be informed, unless this is obvious. The announcement is built into the greeting, in the other party’s language, and they can ask for a human at any time.
How long does it take to deploy an agent?
A few weeks as a rule, after a free audit that identifies the most useful use case, then a phase of design, integration and testing before going live.
Do we need a technical team to run it?
No: the agent is designed, installed and operated by us, working with your IT department on the integration. Caseworkers use it after a few hours of familiarisation.
Do we have to change software?
No. The agent complements your existing case management applications, with no migration imposed.
Which tools can users use to reach the agent?
The ones they already have. The agent answers on WhatsApp Business, the website chat and email: users have no account to create and no application to install. This is a lever for access to the service — WhatsApp and the telephone reach people an online form never does, which reduces the non-take-up of rights and serves equal access. Internally, your public-sector staff talk to the agent from Microsoft Teams, Slack or their email, without switching tools. Oversight runs from a web dashboard. These connectors rely on open standards, including the MCP protocol; they are included in every plan, at no extra cost, within the number of connections your level includes. Only the fees charged by the platforms themselves — WhatsApp Business bills per conversation — are passed on at actual cost, with no margin, outside the subscription.
Related roles
Other professions in social protection
Let's talk
Let's size up the potential in your fund
A few minutes to identify the most useful use case — hosted in France, supervised, with no commitment.