Assistants
AI assistants for staff who need an answer beside the record
An assistant is for a signed-in employee, not for an anonymous visitor. It sits next to the CRM, the policy library, or the operations screen and answers with the same permissions that person already has.
- Role-aware context
- In-product UI
- Citations
- Feedback
Assistant versus chatbot
A public chatbot has a tiny set of safe intents. An internal assistant can know more, because the user is authenticated and the damage of a bad answer is contained by role. Mixing the two in one prompt is how internal notes leak to customers. We keep them separate.
Useful placements
Beside a customer record (“summarise the last month”), inside a document tool (“what does our own policy say”), or in a finance handoff (“which fields are missing before this can be invoiced”). The assistant proposes. The screen the employee already trusts remains the place where data changes.
Help inside the tools staff use
The assistant does
- Answers from the systems that role may open
- Drafts a note in the record
- Shows its source
It does not
- Become a second CRM
- See records the person cannot see
- Replace the procedure
What changes an assistant
Where it sits
Inside the CRM, the desk tool, or a separate window changes what it is allowed to touch.
The role
A branch manager and a new hire should not receive the same depth.
The takeover
The person keeps the screen. The assistant does not file the final action alone.
What a staff assistant needs
- 01
The screen
The tool it sits inside.
- 02
The role
Who will use it on a normal day.
- 03
The sources
Systems that role may already open.
- 04
The action
Draft a note, or only answer. Say which.
Marks an assistant stays a draft
- 01
A person sends
The assistant prepares. The user decides what leaves the screen.
- 02
It uses the record
Drafts read the company system the user can already see.
- 03
Permissions match
The assistant cannot show a file the signed-in person cannot open.
- 04
Discard is easy
A wrong draft does not write itself into the system of record.
What we build
Role-aware context
The assistant retrieves only what that login may see.
In-product UI
A panel in the tool, not a separate novelty app people forget.
Citations
Links to the record, clause, or ticket used in the answer.
Feedback
A way for staff to mark a bad answer so the corpus or prompt can be fixed.
How an engagement runs
- 01
Pick the screen
One place in the working day, not a company-wide copilot launch.
- 02
Connect two sources
Enough to be useful, few enough to permission-test.
- 03
Review with the team that lives there
Their corrections become the evaluation set.
Related reading
Questions we hear
Can an assistant create CRM activities?
Yes, as a confirmed action. Silent writes are how duplicates and wrong owners appear.
Is this the same as RAG?
RAG is often the retrieval method inside an assistant. The assistant page is about the employee experience and the permissions around it.
Do you build desktop copilots?
We build assistants inside the products and data you own. We do not resell a generic desktop agent and call it a solution.