On duty ·
Someone should be keeping track of all this. Someone is.
OnDuty reads the systems you already run and works out what actually needs you today.
The part nobody has a system for
Every company runs on thingsnobody has time to write down.Who complained twice.What you promised in March.Which quiet deal was the big one.It lives in people’s heads,and people go home.
Not another place to put things. A place they mean something.
Six words. Everything the Brain holds is one of them, in the database and on the screen.
- 01
Entities
the things
- 02
Memory
what it kept
- 03
Signals
something happened
- 04
Insights
a pattern, defended
- 05
Decisions
what should happen
- 06
Actions
what executes
The same six words, as one thing.
- Entity
Marcela Rivas
One record, from a phone number in WhatsApp, an address in Gmail and a contact in HubSpot
- Signal
Third message about order 4471
WhatsApp, 02:14
- Memory, observed
“It has to be there before Friday.”
Her words, WhatsApp, 14 August
- Memory, inferred
Cares more about the date than the price
Inferred from three conversations. Not something she said, and never quoted back to her as if she had.
- Insight
Asked the same thing three times and got a first answer each time
Evidence: three messages in nine days, two support cases nobody closed, one order still open. Rule: repeated contact on an unresolved thread.
- Decision
Read the earlier threads before replying
Proposed. Nothing has executed and nothing will until a person answers, and then only if a policy permits it.
An insight with no evidence behind it is refused at the moment it is created. That is a line in the code, not a value in a deck.
It starts from what you already have.
No migration. Connect a system and the Brain reads it, in the six words above.
- WhatsAppE M S
- GmailE M
- HubSpotE · S
- Google DriveE M
- Google Calendar· · S
- WebchatE M S
One customerEntities · Memory · Signals
The other half of the name
At 02:14 a customer wrote infor the third time.Nobody was awake.The message was read. The account was found.The two earlier complaints nobody closedwere found with it.A reply was written, and then held,because sending it needed a person.You were that person, at 08:30,and it took you ninety seconds.
On duty ·
An agent proposes. It never executes.
Between the two sits a decision engine that answers to your rules rather than to the model.
- 01Agentproposes · holds no credentials
- 02Decision enginepermit · hold · deny · your rules, not the model
- 03Executepermit → Connector
- 04A personhold
- 05Nothing happensdeny
If the engine is slow or unreachable, nothing happens. That is the correct amount of nothing.
One model. Eight ways to look at it.
Today
in order, and nothing else
Cards
one moment per card
Graph
who is tied to what
Memory
observed, then inferred
Insights
the pattern, with its evidence
Decisions
and the one button
Ask
your words, your systems
Agents
the hands, not the head
Start on one system and one person.
Grow when it has earned it. Governance is on at every tier, because an agent that is safe to leave running is not an upsell.
Reading the current prices.
Questions people actually ask.
How is this different from a chatbot?
A chatbot answers the message in front of it and forgets. The Brain holds the customer, the history, the documents and the deal at once, and an agent is one of the things it can use. The agent is the hands, not the product.
What stops it doing something stupid?
Agents cannot execute. They propose, and a separate engine permits, holds or denies against rules you write. If that engine is slow or unreachable the action does not happen. Failing closed is the default, not a setting.
Can I see why it thinks something?
Yes, and it is not a feature we could drop if we wanted to. An insight with no evidence is refused at creation, so every conclusion carries what produced it and what it was built from.
Where does our data go?
Into your workspace and nowhere else. Connectors are read-only and credentials are encrypted with a key held outside the database. On the top plan agents run on your own machines, so conversation content never leaves your network.
We already have a CRM.
Good. The Brain reads it. It does not replace the systems you run on; it is the layer that finally makes them agree with each other about who a customer is.
What does it look like on day one?
Empty, honestly, and then not. Connect one system, let it read, and look at what it already knew about the people you have been talking to for two years.
Put it down.
Connect one system and look at what it already knows. If that first morning does not feel lighter than the last one, nothing else on this page matters.