An AI assistant inside your CRM is most useful for work that is repetitive, text-heavy and easy to check: researching a customer before a call, summarising a document someone attached, drafting a first reply, turning meeting notes into tasks, and updating many records at once with a preview. It is least useful for judgement, delicate conversations, and anything you could not undo. Small teams that get real time back start with the first list and keep people firmly in charge of the second.
Start from the record, not a blank chat
The single biggest difference between a useful assistant and a novelty is context. A prompt like “where do we stand with this company?” is only good when the assistant starts from the company in front of you, with its open deals and tasks. Open the record first, then ask.
Good prompts have three parts: the record or file to use, the output you want (five bullets, a draft under 120 words, tasks with due dates) and the check you want (“show me the preview”, “flag anything unusual”). The playbook has copy-ready prompts for each of the jobs small teams repeat every week.
Turn your best prompt into a team command
Every team has one person who writes the best follow-ups or the sharpest call notes. A team command packages how they do it, so a new hire gets the same quality on day one and nobody has to remember the exact wording. Find the prompt people already reuse, rewrite it to work on any record, fix the output format, give it an obvious name, and review the results after two weeks.
Agents only for real routines
A command is a well-written question. An agent is a routine: instructions, a short list of tools, and a fixed shape of answer, which can be chained with actions such as creating a task or a note. Build one only when the same multi-step job happens every week, you can write the steps down without “it depends”, and someone owns the results.
Guardrails that keep it useful
The teams that get the most from AI are the ones that made it easy to check. Four habits cover most of the risk:
- The assistant only sees and changes what the person asking could.
- Anything in bulk shows a preview and waits for a yes.
- A person sends every customer message; drafts are not decisions.
- Dates and amounts in summaries are checked against the source.
Roll it out over 30 days
Add one kind of work each week: asking on records, then drafting and summarising, then team commands, then bulk work and a single agent. On day 30, keep what saved time, change what drifted and drop what nobody used. Measure the business result, not usage: time to first follow-up, open deals with no next step, time spent preparing calls, and records missing key fields.
The full playbook adds the prompt library, a command worksheet, the guardrail checklist, the 30-day tracker and the measurement table.