Phone service agent

Answers calls, queries your ERP while it talks and replies with real data in about two seconds. What it cannot resolve, it does not make up: it takes a message or transfers the call to a person.

Replies with real ERP data in about two seconds
Read-only tools: the model never touches the ERP
Messages and transfer to a person when needed

Download datasheet Let's talk

PDF · A4 · one page

Read the engineering article: “Two seconds to answer” →

How it handles a call

1
Incoming call
The agent picks up and greets.
2
Listens
In Spanish and Galician, including dictated references.
3
Identifies
The company by its phone number, without exposing it to the model.
4
Queries the ERP
Typed, read-only tools.
5
Replies
With the real figure, in about two seconds.

What it resolves on the call

Product stock

From the dictated reference; when in doubt, it asks.

Order status

Lines, availability, carrier and expected delivery.

Customer orders

Only those of the calling company.

Message taking

Delivered to the recipient by email.

Transfer to a person

When the caller asks or the case requires it.

Proof of concept · industrial distributor

1.75 s

until the agent starts speaking (median)

2.47 s

to deliver the figure queried in the ERP (median)

70 ms

per Odoo query, round trip (median)

137

automated tests on the agent and the ERP

Measured on Odoo 18 with fictitious data, without the phone leg. Next phase: PBX connection and outbound qualification campaigns.

Where a person decides

The model never touches the ERP: it calls closed, read-only tools. If the system doesn't respond, it says so and offers an alternative. The call ends with the answer, a message to its recipient or a transfer to a person.