How an AI agent can prepare an account brief with relationship history and next questions
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, 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 prepare an account brief with relationship history and next questions?
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.
Start with the meeting purpose
Name the Clarify account, meeting date, participants, and decision or outcome expected from the conversation. Ask the agent to review current people, company attributes, recent meaningful activity, active opportunities, promises made by either side, and the recorded next step.
Recency is not enough to make an activity relevant. Automated events and routine updates should stay out unless they change the account interpretation. The agent should cite the record and date behind every factual point.
Example starter prompt
Prepare a Clarify account brief for [company] before [meeting purpose] on [date]. Participants are [names].
Include the relationship history that affects this conversation, active opportunities, stakeholder roles, recent commitments, unresolved questions, risks, and the current next step. Cite the Clarify record or activity and date for every claim. Flag stale titles, missing owners, and conflicting notes. Do not update the CRM.Review interpretation separately
Check that customer statements are not blended with internal hypotheses. A sales note about likely priorities is different from a customer commitment. Preserve both labels. If several opportunities exist, confirm that the agent attached activity to the right one.
Questions this workflow answers
What account history and open commitments matter for the meeting we are about to have?
An agent can prepare a meeting-specific brief instead of replaying every CRM activity. Give it the account, date, participants, meeting purpose, and decision or outcome the owner expects. It searches Clarify for current contacts, relevant opportunity or project records, meaningful interactions, promises from each side, open questions, and the recorded next step. Each fact includes its source and date.
The meeting purpose controls selection. A renewal call needs contract timing, unresolved risks, and prior commitments. A discovery meeting needs known stakeholders, earlier questions, and what the team has already claimed. Automated opens, routine syncs, and duplicate notes stay out unless they change the interpretation. An older note can outrank recent activity when it records the controlling decision.
The brief must keep fact and interpretation separate. A customer saying “security review starts next week” is a dated statement. A rep writing “security may be the blocker” is an internal hypothesis. Stale titles, missing ownership, and notes attached to another opportunity become questions rather than polished assertions. Sensitive commentary remains limited to the audience permitted by the source record.
The account owner checks the few facts that would change the meeting plan and corrects stale source records when possible. The final brief includes an account snapshot, participant context, short timeline, opportunity state, commitments, risks, and questions to ask. It is designed to read in minutes, but its links make every point auditable. Post-meeting updates remain proposals until the owner confirms what was decided.
A last-minute participant change should trigger a focused refresh of role and relationship context, not a complete rewrite of the brief.
Expected handoff
Return an account snapshot, participant notes, dated relationship timeline, open opportunity context, commitments, questions, and proposed next actions. Keep source links beside the relevant facts. The account owner should be able to scan the brief in minutes and correct the underlying record when evidence is stale.