Using the AI assistant in MyERPZ CRM

This page describes the AI capabilities in MyERPZ CRM, what they need in order to be useful, and — importantly — what they cannot do.

Where a capability is planned rather than available, it is marked. Nothing below is described as working unless it is.

What is available in CRM today

Lead scoring — evaluates the signals on a lead (engagement, recency, source, activity history) and suggests a priority. It is a ranking aid, not a verdict.

Next best action — recommends a specific step on a specific record, with the reasoning shown. The reasoning is the important half: no interaction for six days, high purchase intent, previous engagement was strong lets you judge whether the recommendation holds before acting on it.

Follow-up intelligence — surfaces overdue follow-ups, leads that have gone quiet, high-value opportunities and likely conversions, without anyone having to run a report.

Customer summaries — condenses a customer’s history so you are not reading back through every activity before a call.

Email generation — drafts follow-up messages for you to review, edit and send. Review them. They are drafts.

Sales forecasting — projects pipeline value, likely conversions, deal risk and trends from your closed history.

What it needs to be useful

AI over an empty CRM produces confident nonsense. Each feature has a real prerequisite:

• Lead scoring needs history to learn from. Expect four to six weeks of genuine use.
• Follow-up intelligence needs follow-ups to be logged. If your team tracks them mentally, there is nothing to read.
• Forecasting needs closed deals — won and lost. A pipeline with no closed history cannot be forecast from.

Turning these on during week one and concluding they are useless is the most common mistake. Give them data first.

What it cannot do

It cannot see records you cannot see. The assistant operates inside your permissions. The chain is organization → user → role → permissions → data access → AI context. If you cannot open a record in the interface, asking about it will not surface it. This is a hard architectural rule, not a setting.

It cannot act on sensitive operations by itself. Deleting a customer or lead, deleting a payment record, cancelling a booking, exporting customer data and sending bulk communication are designed to be prepared by AI and confirmed by an authorised person. Every such action is recorded in the audit log.

It cannot read data from systems MyERPZ is not connected to. It reasons over your MyERPZ CRM records. If half your customer history is in another tool, that half is invisible to it.

Planned, not available

Agents that carry out multi-step work rather than recommending it — a Sales Agent, a Customer Agent and a Reporting Agent — are planned and not usable today. They are marked as such on the AI page.

Getting good results

• Be specific. “Which deals are at risk this month?” beats “how are we doing?”
• Check the reasoning, not just the conclusion. If the reasoning is wrong, the conclusion is coincidence.
• Treat drafts as drafts. Read every generated email before it goes to a customer.
• Report bad output. Tell us when a recommendation is wrong — that is how it improves.