Anthelixa’s workers

Our workers know how to say no.

What a worker never does, and what it does instead

  1. Pay an invoice: never. It reads your accounts, it never touches them: the payment stays with you.
  2. Send an email on your behalf: never. It prepares the draft, a human sends it.
  3. Create a quote without your approval: never. It prepares the card: the quote is created only after your approval.
  4. Change its own rules: never. Only a human changes its job description.
  5. Erase a line from the log: never. Every change stays there: the log accepts additions only.

Everything else, they prepare. You decide.

Not out of politeness: by design. These limits do not depend on what the model is asked: they are written into the platform and into the storage.

The limits specific to your business, for their part, are written into the job description that we write with you, and the worker rereads them in every work cycle.

What they do

The workers, role by role.

Each worker is a role that we build or adjust with you, on your rules. We start from a standard job description: it is faster, and cheaper, than starting from scratch.

Search

It answers your questions about your emails and your documents, attachments and scans included.

What you receive

Example, fictitious data

What it prepares

  1. Your question
  2. It reads emails, attachments, scans
  3. The answer, with its sources

What you decide

What you do with its answer: each piece of information carries a reference, and one click opens the email or the document it comes from.

What it never does
Change, file, move or delete an email or a document: it works read-only.

Request a call backSee Anthelixa’s search

Mail

It sorts the administrative inbox and passes each document to the right person.

What you receive

Example, fictitious data

What it prepares

  1. The administrative inbox
  2. Each document recognised: invoice, notice, reminder
  3. Passed to the right person

What you decide

Anything that fits no category: it flags it to you, and you decide.

What it never does
Reply to anyone outside on your behalf.

Request a call backSee its job description, Mail

Invoicing

It prepares your quotes and your invoices in Pennylane: a quote is created there only after your approval, on a card that shows the customer, the lines and the totals.

What you receive

Example, fictitious data

What it prepares

  1. Your sales proposal
  2. The quote, prepared
  3. The card: customer, lines, totals

What you decide

Your approval on the card, before the quote is created; then the invoice, which you finalise and send in Pennylane.

What it never does
Finalise or send an invoice: the one it prepares stays a draft, without a number.

Request a call back

Incoming invoices

On the invoices received as attachments in your Gmail inbox, it records the supplier, the date, the number and the amount; each doubt becomes a task, with a single question.

What you receive

Example, fictitious data

What it prepares

  1. Invoices received as attachments, in Gmail
  2. Supplier, date, number, amount recorded
  3. Each doubt: one task, a single question

What you decide

You settle each doubt by answering the question in its task.

What it never does
Write to Pennylane or send an email.

Request a call back

Pre-payment control

It spots the new supplier, holds back duplicates, and holds back the invoice after a change of bank details.

What you receive

Example, fictitious data

What it prepares

  1. The invoice, before it is paid
  2. Three checks: supplier, bank details, duplicate
  3. Checked, or held back with the supporting document

What you decide

You decide on each invoice held back; a change of bank details is first checked with the supplier, on a number already known.

What it never does
Pay: the payment stays with you.

Request a call backSee its job description, Pre-payment control

Project tracking

It matches each invoice against its accepted quote and keeps track of what is left to pay, work package by work package.

What you receive

Example, fictitious data

What it prepares

  1. The accepted quotes, package by package
  2. Each invoice matched against its quote
  3. What is left to pay on the package, up to date

What you decide

You approve each matched invoice, which reaches you with its quote and what is left to pay on the package.

What it never does
Approve an invoice: approval stays with you.

Request a call backSee its job description, Project tracking

SEO

It records the pages of your website, their speed and your positions on the searches you track, then proposes its corrections, which you approve.

What you receive

Example, fictitious data

What it prepares

  1. Your pages, their speed, your positions
  2. Its corrections, numbered
  3. A merge request, which you review

What you decide

The corrections to apply, then the merge: it can neither merge nor publish.

What it never does
Publish a correction on your website.

Request a call back

These roles are not a fixed catalogue. The Diagnostic says what to hand over, and what to keep: we look with you at where work is waiting, and what part of it a worker can take on.

A job description

No face. A job description.

A worker has neither a first name nor a smile. It has a job description: what it does, what it never does, who it hands over to.

Every job description we write has a “what it never does” section, which the worker rereads in every work cycle.

And it cannot rewrite it: only a human changes a worker’s job description.

Imagine your worker

Answer one question at a time: with each answer, your worker’s job description is written before your eyes. You leave with it: printed, or attached to your call-back request.

Question 1 of 4Which task takes up most of your time?
  • 80 characters at most.

Question 2 of 4Where does the work come in?

Several answers possible.

Question 3 of 4Who decides in the end?
  • A role rather than a name: 40 characters at most.

Question 4 of 4What it must never do

Several answers possible.

The job description is written in your browser, with JavaScript. Without it, request a call back: we will write it with you.

Your answers stay in your browser: nothing is sent until you request a call back.

How they work

Workers that prepare, people who decide

In the morning, the decisions are waiting, each with what the worker has prepared.

  • A job description

    Each worker has its own: what it does, what it never does, who it hands over to.

  • Rules written in French

    The rules live in the job description, in French: you change them yourself, without any development.

  • Approval before anything is sent

    Anything that would leave your company, an email for example, the worker prepares as a draft, and a human sends it.

  • A log that cannot be rewritten

    The log records who changed what, and when, as well as every time a worker or a search reads your mailboxes; it can be exported in full.

  • Models installed on our server, in France

    The platform runs on a server we operate ourselves, in France. An external model is only called with your written agreement.

  • An answer, with its sources

    When a worker answers you in a conversation, each piece of information carries a reference: one click opens the email or the document it comes from.

A conversation with the Search worker. Claire Dumas asks it which quotes are still awaiting an answer. It answers in three lines: Atelier Bréval is awaiting approval of its quote D-2611, the roller shutters for the Manoir site; Sorel Emballages sent a reminder on 06/10 about its quote for cardboard boxes; the painting quote for the Manoir site, forwarded by Marc Rivière on 29/09, is still awaiting its answer. Each line refers to its source, listed below: two PDFs and an email. In the margin, a note on what it really does: read-only; it reads emails, attachments and Files; change, file, move, delete: no; no missions.
Example, fictitious data

Building them

A recruitment, not an installation

A worker joins you like a colleague: a job description, a trial period without sending anything, approval in one click, then being made permanent for standard cases.

  1. Weeks 1 and 2

    Baseline measurement

    We write its job description with your teams: what it does, what it never does, when it hands over.

  2. Weeks 3 and 4

    Trial period

    It works on your real files without sending anything. Your team compares with what it did itself.

  3. Week 5

    Supervised

    It acts, and its actions go through one-click approval, entrusted to the person you have designated.

  4. Week 6

    Made permanent

    It handles standard cases on its own, within your rules. Everything else is escalated, with its file ready.

You see what it does before it does it

The method, week by week

What stays yours

With or without us, it is yours

Your job descriptions, your rules and your log remain yours: we hand them over to you in an open format, whether or not you continue.

What sets us apart

We run what we recommend

  • A consultancy leaves a report

    We run what we recommend, and we measure the result in your company.

  • Software automates within its own scope

    The worker works between the tools and the people, where time gets lost.

  • A hastily connected agent acts with no framework

    Ours has a job description, a trial period and a record that cannot be rewritten.

We complement business software, we do not replace it

To start

How you buy it

Diagnostic
Fixed feeFully deducted if you install a worker within the following month.
Building a worker
Fixed fee, set at the end of the DiagnosticFrom the job description to being made permanent.
Subscription
Monthly, per worker, depending on volume and complexityThe platform is included: you pay for the work, not the tool.
Commitment
Twelve monthsAt the end of the term, you renew or you stop. Your job descriptions, your rules and your log remain yours: we hand them over to you in an open format, whether or not you continue.

Every price is set before we start. Never on time spent.

Request a call back