B2B SaaS · voice agent
Fymera One
A voice agent that answers the phone for a business and does the work while the caller is still on the line: it checks the calendar, books the appointment, saves the contact. It already answers real calls, on real numbers.

Questo ha un accesso riservato e vieta di farsi incorniciare: è la difesa che impedisce a chiunque di mettere un modulo di login dentro una pagina non sua.
cat ./context.md
Fymera product · 2026
./role --ours
Product, in-house architecture and development
Before and after
how it was
Inbound calls are the channel nobody manages to scale: whoever answers is a person, and when nobody is there the call is lost. An answering machine takes a message to listen to tomorrow, and generic voice assistants know nothing about the company they are supposed to represent.
what we built
A multi-tenant platform in which each company has its own agents, its own numbers and its own knowledge base. The dedicated number sits alongside the existing phone system; the agent answers with what the company has written in the portal, acts during the call and leaves a recording and a transcript of every call.
$ ls ./components
How it is built
-
01
Said on the left, done on the right
While the caller speaks, the agent checks the connected calendar, writes the appointment and saves the contact. In the portal each action appears next to the sentence that triggered it, and the operations are switched on one at a time.
-
02
It can be interrupted
The voice travels from the phone system to the model without a transcript in between. If the caller starts speaking again, the agent stops mid-sentence and knows how far it was heard: the next answer does not take for granted what never reached the ear.
-
03
It does not improvise
Opening hours, address, price list, what can be booked: the company writes them in the portal in everyday Italian. When a request goes beyond that, the agent takes the contact details and the reason for the call, and the call-back starts already knowing what the person wanted.
-
04
Isolation enforced by the database
That each company sees only its own conversations does not depend on the discipline of whoever writes the queries: PostgreSQL refuses, row by row, and tests deliberately try to break it.
$ ./results --after
How it turned out
[ok] It already answers real calls, with recording and transcript in the portal
[ok] The dedicated number sits alongside the existing phone system, without replacing it
[ok] The website chatbot, with the same knowledge base, is in development
// services involved
$ ls ./other-cases
Got a similar project?
Thirty minutes on video to work out whether it is worth doing, and what it really costs. If we are not the right people, we will say so.