Community moderation: your rules, applied continuously
A living community posts at all hours, including while your team sleeps. Your agent applies the code of conduct you wrote, flags the content that deserves examination while citing the rule concerned, and ranks by urgency. Hosted in France: your members' content stays with you. Removal, warnings and sanctions remain human decisions — because they engage your liability as a publisher and your members' rights.
Updated on
Four posts are flagged, each with the rule concerned and the passage that triggers it — abusive language, unauthorised commercial promotion, a third party's personal contact details.
Nothing has been removed: the flags are waiting for your decision.
🔗 Sourced · every flag cites the rule
The context may justify it: that is for you to judge, and your decision will inform how this case is handled in future.
✎ Support · judging the context is human
A Blue Lemon Agent moderation agent applies your posting code of conduct to the content received, continuously, and flags what deserves examination while citing the rule concerned and the passage that triggers it. It removes nothing, warns no one and sanctions no one: those decisions engage your liability as a publisher and your members' rights. It runs on local inference or is hosted in France: your members' content is entrusted to no one, architecture designed to reduce exposure to extraterritorial legislation, location alone not being enough to guarantee immunity. Your teams write to it from Microsoft Teams, Slack or their email, and your members reach it on WhatsApp Business, your website chat or email — with no account to create and nothing to install. These connections are included in every plan, at no extra cost, within the number of connections your level includes. The same code of conduct applies to the comments received on your Facebook pages, your Instagram professional accounts and your LinkedIn pages, and to the reviews left on your Google Business Profile or on Trustpilot — third-party platforms whose interfaces and rules change without notice: nothing is published in your name without your approval, and any fees they charge are passed on at actual cost, with no margin, outside the subscription. Trustpilot cannot be ordered directly: that connection requires your own Trustpilot for Business account with access to the API module, your Business Unit ID and the matching rights; it is priced on quote, after a feasibility study, with Trustpilot's own costs at your charge.
These figures describe our offer, not results measured at a client. How large the gain is on your volume of posts is confirmed by a pilot.
What does an AI agent bring to moderating your community?
A community posts continuously, including outside your team's hours. A permanent first look, grounded in your code of conduct, means your moderators arrive in the morning to a queue that is already sorted.
! The issue
Moderating well means two things that are hard to hold together: a continuous presence and a consistent application of the same rules. The agent brings both — it examines every post against your code of conduct, at any hour, and grounds every flag in the rule concerned, so your moderators arrive to a queue that is ranked and documented.
✓ Our answer
You write the rules, the agent applies them and gives its reasons. Every flag cites the rule and the passage that triggers it, which makes the decision quick and, above all, defensible to the member concerned. Local inference or an isolated resource hosted in France: your community's content feeds no third-party model, and no removal is automated.
The content your members post: sovereignty & compliance
The content your members post belongs to them and falls under your liability as a publisher. Here is how the architecture of our agents protects it.
Local inference
The agent can run on a machine belonging to your organisation: no member's post leaves the network, no content passes through a public cloud.
Hosting in France
Otherwise, a dedicated and isolated resource hosted in France, under French law — your posting rules and the content received: processing and access within the European Union targeted by the architecture.
Reduced extraterritorial exposure
For the content your members post, the architecture aims to reduce exposure to the Cloud Act and FISA 702; being located in France or in the European Union does not, on its own, guarantee immunity.
Isolated resource
No pooling: an environment strictly dedicated to your community and its code of conduct.
Every flag cites its rule
No flag without a reference to the rule in your code of conduct and the passage concerned; encryption, role-based access and logging of examinations.
AI Act: governed deployment
The agent is strictly in support; no removal, no warning and no sanction is automated; 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.
- 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.
See the agent at work
4 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.
· A message publishes the phone number and address of a person who has not written in the thread. I have hidden it pending review — it is the only thing I hide.
· Thirty-nine messages were removed over three months on a ground that does not exist in your published rules.
· The same message was reported twelve times by eleven different members and has stayed online for 40 hours.
· Seven messages written in a regional language were flagged automatically by your filter. None raised any problem. morning-watch_4-flags.pdf4 flags · 1 hidden message
⛓ Source · moderation queue, published rules, removals log, member reports
What the message does: it publishes a phone number and a postal address belonging to a person who has never written in this thread.
Why I hide that one and nothing else: the two members arguing chose to write here. The person whose address is published chose nothing — they are not party to the conversation, they probably do not know they appear in it, and every minute counts.
What "hidden" means: the message is no longer visible, it is not deleted, its author is told, and a moderator decides within four hours. If the decision is to restore it, it is restored.
What I do not hide, and the list is short: an insult, a criticism of the company, a remark I would find violent, a message reported twenty times. None of those involves a non-consenting third party.
Over twelve months: 9 hidings, 8 upheld, 1 restored. The restored one published a business address that was already public. 9-hidings_12-months.pdf8 upheld · 1 restored · the only exception
⛓ Source · message of 08/08, discussion thread, hidings history
Routing follows what escalates: a third party's personal data hidden and escalated immediately; a repeated report to the on-call moderator from 3 distinct reports, not from a high number; a removal on a ground outside the rules to the community lead, grouped; a filter false positive to whoever tunes the filter, with the messages concerned.
With a chase: 4 h on a hiding, 4 h on a repeated report, 7 days on the rest. Then a monthly summary: by ground and by rule invoked, never by member and never by moderator.
Three guarantees, and they hold. Removal, warning and sanction stay human decisions — they engage your publisher's liability and your members' rights, and that is exactly what makes them defensible. I hand them back to you in seconds rather than hours: every flag arrives with the published rule it puts in question and the exact passage that triggers it. I see only the spaces you have opened to me, access by role, traced, withdrawable in one word. And any message whose classification is uncertain goes to a moderator: doubt escalates, it does not settle itself.
✎ Framework · one exception to non-hiding, written and bounded
What I record: 39 messages removed over three months on the ground "off topic". Your published rules contain six prohibitions, and "off topic" is not among them.
What that produces: a member whose message is removed reads the rules, does not find the ground, and concludes it was arbitrary. Eleven of the 39 wrote to contest, and there was nothing to point to.
What I do not say: that the removals were unjustified. A space devoted to a subject may legitimately set aside what does not belong — but that must be written beforehand, not invoked afterwards.
What I propose: add the rule, or stop removing on that ground. Both stand up; what does not is the gap between practice and the posted text.
What I also looked at: across the quarter's 214 removals, 171 invoke one of the six published rules and 43 invoke something else — "off topic" 39 times, and four one-off grounds.
What I bring you so it can be written: the 39 messages removed as off topic, grouped by what they had in common — three families cover them all — and your six published rules as a wording template. The rule itself is written at your end: a community rule defines what people agree to hear, and the community has to recognise itself in it. 214-removals_43-outside-rules.pdf171 grounded in a rule · 11 contestations
⛓ Source · 214 removals this quarter, 6 published rules, contestations
What I record: seven messages written in a regional language were flagged automatically. None contains anything breaching your rules. The filter does not recognise the language and treats the unknown as suspect.
What it produces, and what is never measured: the members concerned see their messages delayed. Three of them have stopped writing in that language; two have stopped writing.
Why it is hard to see: over-moderation produces no complaint. People leave. The dashboard shows fewer reports and fewer incidents — it looks like an improvement.
What I propose: the seven messages, the language identified, and a systematic human review before any delay for languages the filter does not recognise — rather than an automatic flag.
What I costed on both sides of the trade-off: widening the filter to that language would bring the 7 delayed messages to zero and, replayed over the past quarter, would have let through 4 messages your moderators removed. The tuning is yours — choosing between two errors means choosing which one you prefer to make — and you do it on two figures instead of an impression. 7-messages_regional-language.pdf0 real problems · 5 members went quiet
⛓ Source · 7 flagged messages, filter log, activity of the members concerned
What "continuously" means here: 18,400 posts this month, each examined against all 14 rules, including between 23:00 and 07:00 when your team reads nothing. Average time to examine: 11 seconds, against 40 hours for the post flagged twelve times we discussed.
What the examination produces, post by post: 18,062 with no action — no rule engaged; 287 placed in the review queue with the rule quoted and the exact passage that triggered it; 51 moved to the head of the queue because they engage two rules at once or target a named person.
Quoting the rule is not a courtesy, it is what makes moderation sustainable: a moderator who receives "rule 7 — remarks aimed at an identifiable person, passage highlighted" decides in 20 seconds. Without it, they reread the whole thread. Across the 287, decision time fell from 4 minutes to 40 seconds.
What applying your code revealed about the code itself: 39 removals in three months rested on a ground that is not in it — disguised advertising. Your moderators were right on the substance and had nothing to cite. I have drafted a rule 15, in the form of the other fourteen, and run it over the last three months: it would have caught 44 posts, including the 39 already removed and 5 more you had not seen. You publish it or you do not; until it is published it does not apply — a rule that lives in my settings rather than in your code is a rule nobody can challenge.
The figure that does not flatter me: 62 of the 287 review referrals were dismissed by your moderators, or 21.6%. Fifty-five concerned rule 3 — abuse —, triggered by quotations: a member reporting another's words in order to denounce them. Rule 3 now accounts for quoted passages: 9 dismissed across the following 240 referrals.
✎ Framework · your code of conduct applied, rule by rule, continuously
What I record: twelve reports by eleven distinct members, between Saturday 2 p.m. and Monday 6 a.m. The message has been online for 40 hours. The moderation queue is only worked on weekdays.
What I sort on, and why not on volume: twelve reports can come from a disagreement; a single one can concern a serious message. Ranking by volume would surface controversies and bury the urgent ones — over your quarter it would have put six lively threads at the top and ranked the message that sat online for 40 hours forty-first by urgency.
What I do instead: I escalate from three reports by distinct members — a low threshold is enough to pull a message out of the queue — and I escalate immediately, whatever the number, any message containing a third party's personal data.
What that does to your queue: across 640 reports this quarter, 84 messages reach three distinct reports. That is a workable queue, and it does not contain the other 556.
What I also propose: a weekend on-call rota, or explicitly accepting that nothing is handled from Friday evening to Monday. Both stand up; the implicit does not. 640-reports_84-escalated.pdfThreshold of 3 distinct members · 40 weekend hours
⛓ Source · 640 reports this quarter, working hours, moderation queue
What I do before a message reaches the queue: I classify it by nature — explicit violence, sexual content, harassment, threat — and the moderator sees the nature before the content. They choose the moment.
Why that matters: a moderator opening a queue without knowing what it holds receives everything unprepared. That is not a comfort, it is what separates sustainable work from work that wears people out.
What I also do: I never present the same content twice. A message already handled and re-reported by another member arrives with its earlier decision, without the content being displayed again. Over the quarter that avoided 217 re-displays.
What I spare them, and what I cannot spare them: I spare them the surprise, the repetition and the sorting — nature announced before the content, earlier decision recalled, 217 re-displays avoided over the quarter. What remains is the reading itself: content not read by a human is content removed or left by a machine, and it is your publisher's name that would sit at the bottom of that decision.
What I do not measure: how long a moderator spends on a message. Some deserve stopping over. 217-re-displays-avoided.pdf4 natures announced · no time measured
✎ Framework · nature announced before content · no content displayed twice
What is kept: the removed message, the rule invoked, the decision and who took it, the date, and the contestation where there was one.
Why the message itself: because a moderation decision gets contested. A message deleted with no copy makes the contestation impossible to examine — and hands the argument to whoever claims the removal was abusive.
What is not kept: no moderation history attached to a member, no behaviour score, no watch list, and no data about members beyond what the conversation contains.
Why "no history attached to a member": it would serve to handle a message according to its author. A member whose three messages were removed two years ago would be moderated more harshly today, on a message that may raise no problem at all.
What that does not prevent: a moderator who recognises repeated behaviour can act — they do so knowingly, and their decision carries their name. That is very different from a system that silently weights. what-remains_of-a-removal.pdf5 items kept · 4 never attached to a member
✎ Framework · no per-member history, no behaviour score
What is kept, besides removals: hidings and their outcome, reports and the threshold reached, filter false positives, and grounds invoked outside the published rules.
Why the false positives: it is the only indicator that measures over-moderation. Moderation that is too broad produces no complaint — people leave, the dashboard improves, and nobody sees anything.
What is not kept: no per-member history, no statistics per moderator, no individual handling time, and no third-party personal data extracted from a hidden message.
Why "no statistics per moderator": a moderator measured by volume works fast. Yet the decisions that count are those where one has to stop, and they are rare — counting time spent makes them expensive.
What the monthly summary contains: removal grounds by rule, removals outside the published rules, filter false positives, and handling times by time band. Four indicators about the arrangement. what-is-kept.pdf9 items kept · 4 never produced
✎ Framework · retention periods to be set by the company
Your case is not here? That is exactly what a 15-minute conversation is for. Book the free audit →
What does the agent actually do?
One agent, several everyday moderation acts. All these uses work in support, subject to your approval.
Applying your code of conduct
Examines every post against the rules you wrote, continuously.
Reasoned flags
Cites the rule concerned and the passage that triggers it, for a quick and defensible decision.
Ranking by urgency
Puts at the top what calls for immediate examination, according to your own priorities.
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.
Community management
For running and posting on your Facebook pages, Instagram accounts and LinkedIn pages, a dedicated agent takes over.
Community management from 610 € excl. VAT / month Community management →Replying to customer reviews
For reviews left on your Google Business Profile and on Trustpilot, a dedicated agent prepares the replies.
Customer review reply agent from 522 € excl. VAT / month Customer reviews →In 15 minutes we identify the most relevant agent — without oversizing the project.
How much peace of mind can a moderation team gain?
By providing a permanent, reasoned first look, continuous watching gives way to a decision on a queue that is already sorted. How large the gain is depends on your volume and remains to be confirmed by a pilot.
The stages of your AI agent project
Audit & scoping
15 minutes to target the use case with the best return.
Quote or direct sign-up
A catalogue offer is bought online; a specific need gets a costed quote.
Design
We design the agent and its guardrails.
Integration & testing
We connect your tools to the agent, which is itself hosted in France.
Rollout
Going live and training your team.
Operation
Continuous supervision and improvement.
One package, one agent
A moderation agent (code of conduct, reasoned flags, ranking), installed and operated for you.
Setup + controlled subscription
- Installation, configuration and training for your teams
- Operation, human oversight, updates and support
- Sovereign hosting in France, a dedicated and isolated resource
All inclusive, no setup fee
- Setup included (installation, configuration, training)
- Operation, human oversight, updates and support
- Sovereign hosting in France, managed end to end
On site, you own it
- Hardware installed on your premises (you own it)
- French / European AI models run locally
- Secure remote maintenance (Pro support included)
Four guarantees that matter to your community
Related resources
Your questions, our answers
Does the agent remove content?
What rules does the agent draw on?
How do I justify a decision to a member?
Does the agent cover nights and weekends?
Is our members' content protected?
How long does it take to deploy this agent?
Which tools can people use to talk to the agent?
Does the agent also moderate Facebook, Instagram and LinkedIn comments, and online reviews?
Other agents for your online presence
Let's size up the potential in your moderation
15 minutes to frame your code of conduct and your channels — hosted in France, supervised, with no commitment.