Your first week
What to expect while the memory fills in, and what to correct early.
Suvi's memory is empty on day one. The first fortnight is spent filling it, and what you do during that period determines the quality of everything after.
Days 1 to 2: connection
You connect WhatsApp, mail and calendar. Suvi reads recent history once to build initial context. Nothing goes out. No labels change, no drafts are sent.
You will see it start referring to people and companies by name. That is the knowledge graph populating.
Days 3 to 7: watch the drafts
Suvi begins drafting replies and briefs for your review. Read them, and correct the ones that are wrong. Fifteen minutes a day here is the highest-leverage time you will spend on the product.
Corrections are not discarded. Telling Suvi that a client prefers terse replies, or that a name it matched is the wrong person, writes to memory and changes future drafts.
This is where rollouts fail
Not because the software breaks. Because the fifteen minutes a day does not happen, and Suvi enters week two confidently wrong about things nobody corrected.
What to correct first
In rough order of impact:
- Wrong people. Two contacts merged into one, or one split into two.
- Stale facts. A price, a role or a status that changed, which Suvi picked up from an old message.
- Tone. If the drafts do not sound like you, say so directly. "Too formal with Ravi" is a usable instruction.
- Priority. Who counts as urgent. Suvi interrupts for VIPs and same-day deadlines, so it needs to know who is a VIP.
Week 2 onward
Briefs go live twice daily. Recurring work moves to workflows. You decide, per action, what Suvi may do without asking.
Most owners widen approval for internal recipients within a month and never widen it for clients. That is the right instinct.