Skip to content
BM Automation
A hand chooses an eggplant folder from several work folders on a desk.

AI agent for VSE & SME

BM helps you choose recurring work that the team can really trust.

A precise mission.
With your current tools.

First AI agent, what mission?

Compare missions

Six missions
to decide.

Four conditions to choose.

Open a mission to see its output and limits.

Illustrative scenarios, without calculated score or gain.

Customer requestsFrequency: Every daySources: Email + CRMResponsible: ADVRisk: Customer engagement

To explore

Prepare the right question.

Tracking requests
Teaching example

Request to specify

Address and deadline not specified

At what address and for what date?

Draft prepared, not sent.

Source
Email received + authorized customer file
Responsible
ADV
Read the perimeter and its stops

The AI can interpret the received text. A fixed rule is enough for a simple email transfer.

Starters
Authorized emails and up-to-date customer file.
Prepare
Need summary, missing information and next question.
Run
Create a monitoring sheet according to the approved rules; prepare the response.
Stop and confide
Ambiguous request or commercial commitment: the ADV qualifies and validates.
Quote trackingFrequency: Every weekSources: Quote + CRM statusesResponsible: CommercialRisk: Customer relations

Configure first

Start with CRM.

Quote tracking
Teaching example

An internal reminder

Response status to check

Task to configure

Check quote response

Recall proposed, not created.

Source
Quote + last known exchange
Responsible
Commercial
Read the perimeter and its stops

An agent becomes a lead if the context of the exchanges must be reconstructed. He does not decide on a discount.

Starters
Date of sending, due date and last known exchange.
Prepare
List of unanswered quotes, after checking the status.
Run
An internal reminder may be enough. Customer shipment remains limited to the agreed conditions.
Stop and confide
Response received, postponed to negotiation or disagreement: return to sales.
Collection of documentsFrequency: Every weekSources: Expected list + folderResponsible: AdministrationRisk: Personal data

To explore

Locate the missing document.

Collecting coins
Teaching example

The file to complete

Presence does not constitute validation

Purchase order
Received, to check
Certification requested
Missing

To request: the certificate.

Additional request prepared, not sent.

Source
Expected list + received file
Responsible
Administration
Read the perimeter and its stops

The presence of a file does not prove its validity. One form is sufficient if all documents follow a simple format.

Starters
List of required documents, files received and access rights.
Prepare
Documents compared to the list, missing items reported without inventing their content.
Run
Classify the documents and prepare the request for only the missing elements.
Stop and confide
Sensitive, illegible or doubtful document: the administration takes over the file.
Invoice remindersFrequency: Every weekSources: Invoices + paymentsResponsible: AccountingRisk: Recent dispute or payment

Not eligible as is

Check payment first.

Monitoring unpaid debts
Teaching example

Stalled follow-up

Unknown settlement

No customer shipments

Internal action prepared: check the latest regulations.

Customer reminder not prepared, not sent.

Source
Overdue invoice; regulations not updated
Responsible
Accounting
Read the perimeter and its stops

Making payment records accessible can make the workflow testable. It does not grant general permission to collect debts.

Starters
In this scenario, the payment status is not updated.
Prepare
Variances to check and accounting checklist.
Run
No customer reminders until the payment situation is confirmed.
Stop and confide
Recent payment, credit note, dispute: accounting decides what happens next.
Internal responseFrequency: A few times a yearSources: Conflicting documentsResponsible: Not designatedRisk: Wrong answer

Not eligible as is

Arbitrate the reference.

Answers and exceptions
Teaching example

Response suspended

No reference rule confirmed

Document AValidation required.

Document BSending without validation.

Response not produced.

Source
Two contradictory procedures
Responsible
To be designated
Read the perimeter and its stops

Clarifying and tidying up the procedure may be enough. If requests become recurring, a sourced response may be studied.

Starters
Several versions of a procedure, without authentic document.
Prepare
Open questions and sources to be arbitrated by a manager.
Run
No response presented as a company policy.
Stop and confide
Absent or contradictory source: return to an identified person.
Appointment confirmationsFrequency: Every daySources: Agenda + stable rulesResponsible: HomeRisk: Double booking

Configure first

Set up the calendar first.

Appointment confirmations
Teaching example

Native confirmation

Availability to recheck

Illustrative niche

Tuesday9 a.m. to 9:30 a.m.

Confirmation in the reservation tool

To configure; none appointment confirmed.

Source
Agenda + reservation rules
Responsible
Home
Read the perimeter and its stops

An agent discusses when the request requires interpretation or several business verifications.

Starters
Reference agenda, duration and up-to-date availability.
Prepare
Compatible slots and useful information available.
Run
Confirm within the validated scope, after a new availability check.
Stop and confide
Resource conflict, modified need or missing data: return to reception.

Source unavailable, manager absent, risk uncontrolled: we reframe.

A mission,
limits.

An email without an address: the question is prepared, the commitment awaits.

Educational example · email received

“Can you step in tomorrow?” ”
Address of interventionMissing

Question prepared, not sent“What address?” ”

No commitment.

No confirmed slot, no promised price.

Validation in TPE
LeaderValidates the question to the customer.
Takeover in SME
Intervention managerReceives the exception and validates the rest.

In this case, the intervention manager takes over. Each mission appoints its own manager.

Measure the
work your team can take over.

The result is judged after verification and review by the team.

Reported on comparable situations
BeforeVolume, full time, omissions.
TestTime with supervision, corrections, exceptions taken up by the team.

Continue, adjust or stop. The gains remain to be established.

Let's start from a
real mission.

An example, its sources, its manager: enough to begin to qualify your need.

Scope your first assignment

BM designs support around your process and tools.

Before choosing.

An agent for a rare task?

Not necessarily. An occasional task, simple to handle by hand, may not justify the connections and supervision of an AI agent. A clear instruction, documentary research or occasional conversational assistance may be sufficient. Frequency must be observed in your activity, without automatically converting every minute into financial savings.

What can he perform?

Only explicitly agreed actions: for example creating an internal file, filing a document or sending a message under approved conditions. Access, recipients and stopping situations are defined before the test. A prepared action proves neither its execution nor its reception. Commitments, disputes and sensitive decisions remain with an authorized person.

Should I change software?

BM starts from your tools and your process. The connection possibilities and available rights are checked before choosing a solution. A native setup or classic automation may be preferable. While a custom layer is useful, its role is to support work between tools, with outputs that your team can pick up.

Are these customer cases?

No. The six situations and their conclusions are illustrations of choice, not customer results or scientific recommendations. They demonstrate no time savings, ROI or level of reliability. A VSE/SME case is verified on its own data and with its team. Actual conditions may lead to another decision.