How an AI agent can prepare a compact relationship brief with open questions and next actions
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 Attio 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 a compact relationship brief with open questions and next actions?
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.
Brief the next conversation
Give the agent the Attio company or person record, the meeting purpose, and the participants. Ask it to find the latest meaningful interactions, open opportunity or project context, prior commitments, known stakeholders, and unresolved questions.
Recency alone does not determine relevance. A recent automated activity may matter less than an older note containing a promised follow-up. The agent should identify the source and date behind each item so the meeting owner can judge it.
Example starter prompt
Prepare an Attio relationship brief for [account or person] before [meeting purpose] on [date]. Participants are [names].
Include the relationship history that affects this conversation, current opportunities or projects, stakeholder roles, commitments made by either side, open questions, and the latest agreed next step. Cite the Attio record, note, or interaction and date for every factual claim. Flag stale titles, unclear ownership, and conflicting notes.Keep the brief selective
The brief should help someone prepare in a few minutes. Ask the agent to omit routine activities and repeated notes unless they change the interpretation of the relationship. It should distinguish a recorded customer statement from an internal assumption or sales hypothesis.
Review sensitive notes before sharing the brief beyond the account team. The output should follow the permissions and audience of the source records.
Questions this workflow answers
What does someone need to know about an account before walking into the next conversation?
An agent can turn a long relationship record into a brief built around the purpose of one meeting. Give it the company or person, participants, meeting type, date, and questions the owner expects to resolve. It searches Attio for the interactions, notes, opportunities, projects, and attributes that change this conversation: recent commitments, unresolved objections, stakeholder roles, an agreed next step, or a relationship detail that has gone stale.
Selection matters more than chronology. A recent automated activity should not displace an older note that records a binding promise. The agent cites the record and date behind each fact, labels internal hypotheses, and shows conflicts rather than writing a smooth account story. A contact title that has not been verified in a year belongs in a preparation question. A next step contradicted by a later note needs owner review.
The participant section can show each person’s role in prior interactions, topics they raised, commitments they made, and what remains unknown. It must not infer authority, sentiment, or private motivation from sparse notes. Sensitive account commentary should respect the source record’s audience; a brief prepared for an external attendee needs a separate review from an internal account-team brief.
Ask the owner to verify the top three claims and open the linked source if any would change the meeting plan. The finished brief should be readable in a few minutes and end with concrete questions, not a transcript of the CRM. After the meeting, confirmed decisions can be proposed as updates, while pre-meeting assumptions remain labeled or are removed. That keeps preparation useful without allowing the generated summary to become a new unverified source.
Expected handoff
Return a short account snapshot, participant notes, recent developments, commitments, open questions, risks, and recommended next actions. Include source links and dates. Do not update relationship stages, ownership, or next steps until the meeting owner approves them.