02.01
What an AI CRM Manager does, and what it never does
Write the one-page job description for your AI CRM Manager so every later setting has a clear boundary.
Video walkthrough
- Why a CRM full of contacts still leaks deals: replies nobody answered, leads nobody called
- The five jobs Grok can do well with CRM data
- The four things it never does: send, decide consent, give advice, invent facts
- Reading the job description out loud and signing it
What you're building
A one-page job description for an AI assistant that reads your CRM data and hands you a short, reasoned work list every morning. It reviews. It ranks. It drafts. You send, call and decide.
Every chapter after this one turns a line of this job description into a working setting: the Grok profile, the data connection, the prompts, and the guardrails.
Why it matters
Most CRMs do not lose deals because of missing features. They lose them in three quiet ways: a contact replies and nobody answers, a new lead never gets a first call, and a date in the notes (a lease ending, a school year finishing) passes without anyone noticing. A person can find these by reading every record. Almost nobody has time to.
An AI model is good at reading hundreds of records and notes and explaining what it saw. It is not accountable for consent, licensing or the relationship. Writing the boundary down first keeps it useful and keeps you out of trouble.
What you need
- 15 minutes
- Your CRM name (HighLevel, Follow Up Boss, or another)
- A rough count of your contacts and how many are active leads
- A notes app or a document to save the signed job description
Time and cost
- Time
- 15 minutes
- Cost
- $0
Step by step
List the five jobs you will hand over
Copy the job description template below. Keep the five jobs as written unless one does not apply to you:
Job What it produces Chapter Find neglected opportunities A ranked list with a reason for every contact 02.07 Organize leads and write follow-up tasks Task rows you paste or enter in your CRM 02.08 Summarize conversations An 80-word CRM note per conversation 02.08 Write the daily prioritized list Up to 10 to 25 people for today, with draft openers 02.09 Flag data problems Duplicates, missing phones and emails, stages that contradict notes 02.07 Check: Your copy lists five jobs (or fewer, with a reason for each one you removed).
Write the four things it never does
- It never sends. No texts, emails, calls, voicemail drops or workflow enrollments. Drafts only.
- It never decides consent. Opt-out and consent fields come from your CRM and win every time. If they are missing, the answer is no text.
- It never gives legal, tax, lending or credit advice, and never sorts or targets anyone by a protected characteristic under the Fair Housing Act.
- It never invents facts. Every claim cites a Contact ID and a field. Missing data is written as "unknown".
Check: The four rules are in your document word for word, or stricter.
Decide how the assistant will see your data
Pick one starting point now. You can move up later.
Option Best for Risk CSV export uploaded to Grok Everyone starting out Lowest: you choose the columns, nothing can write back Official connector or MCP server Teams whose CRM and AI tool both support it Medium: depends on the scopes you approve Your own read-only API integration Technical users or a hired developer Medium: depends on key handling Chapter 02.05 compares them in detail. Start with the CSV. It teaches you what good output looks like before you connect anything live.
Check: Your job description names one data option.
Set the measure you will check in 30 days
Pick numbers you can count from the CRM, not feelings. Write today's value next to each.
- Unanswered replies older than 2 days (target: 0)
- New leads with no outbound contact after 24 hours (target: 0)
- Contacts called from the daily list per week
- Appointments set from the daily list per month
Check: Four baseline numbers with today's date next to them.
What success looks like
- A saved, dated job description with five jobs and four never-rules
- A chosen data option
- Four baseline numbers you can recount in 30 days
Copyable templates
# AI CRM Manager: job description
Agent: ______________________ Brokerage: ______________________
CRM: ______________ Data option: CSV export / connector / read-only API
Signed: ____________ Date: ____-__-__
## Jobs (it does these)
1. Find neglected opportunities and rank them with a reason for each.
2. Turn findings into follow-up tasks I can enter in my CRM.
3. Summarize conversations I paste into short CRM notes.
4. Write my daily prioritized contact list with draft openers.
5. Flag duplicates, missing phone or email, and stages that contradict notes.
## Never (it does not do these, ever)
1. Send, schedule or queue any text, email, call or workflow enrollment.
2. Decide consent. CRM opt-out and consent fields win. No consent record means no text.
3. Give legal, tax, lending or credit advice, or sort or target anyone by race, color,
religion, sex, disability, familial status or national origin.
4. Invent facts. Every claim cites a Contact ID and field; missing data is "unknown".
## Baseline (count today, recount in 30 days)
- Unanswered replies older than 2 days: ____
- New leads with no outbound contact after 24 hours: ____
- Contacts called from the daily list per week: ____
- Appointments set from the daily list per month: ____
Try it
- Your CRM→toGrok as CRM Managerread-only data
- Grok as CRM Manager→toYouranked list + drafts
- You→toContactyou send
- You→toYour CRMyou log the result
- Your CRM→to30-day recount
How to test it
Read the four never-rules to someone on your team, or out loud to yourself. Then ask: "If the assistant did exactly this for a month, what could go wrong?" If the answer involves a message going out without you, tighten rule 1 before moving on.
Troubleshooting
I want it to send texts automatically to save time.
Start with drafts for 30 days. Automated sending needs consent records, A2P 10DLC registration, opt-out handling and a human review step. Chapter 02.10 shows what a safe version requires.
My team shares one CRM. Whose job description is this?
Write one per person who will act on the list. Add "Only list contacts assigned to me" so two agents never call the same person.
Advanced technical details
Optional. You can follow every step above without these.
Technical detailsWhy "read, rank, draft" is the safe division of labor
Reading and ranking are reversible: a bad ranking costs a few minutes. Writing to the CRM (tags, stages, workflow enrollment) and sending messages are not reversible. The HighLevel MCP documentation itself separates read operations from create, update and delete operations, and xAI's Grok Bot guidance recommends keeping sending, deletion and production changes behind approval. Build the same line into your own setup.
Sources
A method with illustrative numbers. Replace the examples with your own. Last checked 2026-10-20.
- LeadConnector MCP ServerHighLevel Developer Docs · read 2026-10-20
- Approvals, security, and privacyxAI documentation · read 2026-10-20
- The Fair Housing ActU.S. Department of Justice, Civil Rights Division · read 2026-10-20