How an AI agent can create a current, CRM-aware customer follow-up
This workflow gives an AI agent a defined job, a bounded set of records, and a result a person can review. The agent reads the relevant Clarify context and matches it with Gmail, applies the rules in the prompt, and keeps the source behind every recommendation. It returns a proposed handoff rather than taking consequential actions on its own.
Can an AI agent create a current, CRM-aware customer follow-up?
Yes. Start with the scope, date range, decision rules, and fields that identify the right records. The agent can collect the evidence, compare states or sources, mark conflicts and missing data, and organize the result around the outcome above. A reviewer then checks the matches and judgment calls before approving messages, record updates, bookings, purchases, publishing, or other write actions. The guide below shows the records, boundaries, prompt, and handoff needed for this specific workflow.
Reconcile the thread and the account record
Gmail shows what the customer and team wrote. Clarify shows the account owner, opportunity, stage, notes, and expected next step. Match participants by verified email and name the exact thread or query. The agent should identify commitments or questions in Gmail that are absent from Clarify, plus CRM values that conflict with the conversation.
Example starter prompt
Review Gmail thread [link or query] and the matching Clarify records for [account].
Summarize the latest request, commitments from each side, unanswered questions, and conflicts with the CRM owner, opportunity, stage, or next step. Draft a concise reply that addresses the open items. Then list proposed Clarify updates with the email sentence and date supporting each one. Do not send or update records.Do not record a draft as an agreement
A proposed date or action in the draft is not a customer commitment. The agent should add it to Clarify only after confirmation. Internal notes should also stay out of the external email unless the owner deliberately includes them. Check quoted dates, names, attachments, and promised deliverables before approval.
Questions this workflow answers
What should we send after a customer email, and which parts of the CRM now need correction?
An agent can read one defined Gmail thread and compare it with the matching Clarify account, contacts, opportunity, owner, and next step. It verifies participants by email, extracts requests and commitments with their dates, and identifies information in the conversation that the structured record does not yet reflect. Similar names or several opportunities stay unresolved until the owner confirms the match.
The reply draft addresses the confirmed open items in the customer’s language. It checks names, dates, referenced files, and who promised each action. A suggested meeting date does not become an agreement, and a question about pricing does not prove a new stage. Internal notes, forecasts, and account hypotheses remain outside the customer message unless the sender deliberately includes appropriate wording.
CRM changes appear in a separate table. Each row shows the current value, proposed value, exact supporting email sentence, message date, and reason. A confirmed deadline may justify a task proposal; a customer correction may update a contact field; a new participant may need review before record creation. Conflicts between the thread and an older rep note are shown rather than overwritten.
The relationship owner approves sending and record updates independently. They may accept the email while rejecting a stage change, or update the CRM while revising the draft tone. Once the customer replies, only confirmed commitments are carried forward. The workflow keeps correspondence and account history aligned without allowing a generated draft to become evidence of something the customer never accepted.
Quoted customer language should stay attached to its dated thread so a paraphrase cannot later be mistaken for a confirmed requirement. Attachments and recipient changes receive their own review.
Expected handoff
Return the thread summary, relevant CRM context, conflicts, reply draft, and proposed field or note changes. Each change needs the current value, proposed value, Gmail citation, and reason. The relationship owner approves the message and CRM writes independently.