harnyUse case
Memory for sales and account teams
A sales assistant reads email, call notes and CRM updates about the same account. Memory for account teams has to hold the budget as it stands today, what it was before, and who said so on which date.
What you are building
An assistant that prepares a call or answers a question about an account: the budget, the timeline, who decided what. It reads what the team already wrote down.
Why memory decides whether it works
- Values change. A budget quoted in March and revised in July is two facts. Search returns both and leaves the agent to guess.
- Notes live in many places. Email, calls and CRM notes describe one account in different words.
- A quoted number needs its date. An answer that says 40k without saying when it changed gets repeated after it stops being true.
What Harny provides
- Backdatable ingestion: backfill the history with its original timestamps.
- Current-state recall: the recall returns what is true now, what it replaced and where each value came from.
- As-of recall:
queryTimestampleaves out evidence newer than the moment you ask about. - A record of what the agent did, kept for the next request.
Getting there
- Send each email, call note and CRM update to
POST https://api.harny.ai/v1/memory/ingestwith the time it happened. - Ask
POST https://api.harny.ai/v1/memory/recallabout the account when the call is prepared. - Use
queryTimestampto read the account as it stood on an earlier date. - Send the agent's own actions as data points so the next request sees them.
Frequently asked questions
Which value does recall return when two notes disagree?
The most recent value for the same fact, with the date it changed. The earlier value stays in the history.
Can I ask what we knew on a past date?
Yes. Send queryTimestamp and evidence newer than that moment is left out.
Go on. Get Harny.
The first 500 monthly-active end users are free for good. Create an app key and make your first call in minutes.