--- title: "Account Review Dossiers With AI Agents | Kylon" description: "How a sales team builds weekly account dossiers from Attio and Outlook, reports where the record and the mail disagree, and issues new versions when scope changes." url: "https://kylon.io/use-cases/account-opportunity-dossier" language: "en" --- [HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Account Review Dossiers: Record and Inbox Disagreements Reported, Not Resolved Use Case8 min read # Account Review Dossiers: Record and Inbox Disagreements Reported, Not Resolved Weekly account dossiers are built from the Attio account book and in-scope Outlook mail in one Kylon room. Agents report every disagreement between the record and the mail with both values, and the review, not the dossier, decides which one is right. [Get started](https://app.kylon.io/sign-up) Kylon TeamProduct November 6, 2026 ## Where the account book and the inbox disagree Each week the sales leadership team reviews a short list of accounts: where each one stands, what is open and what has changed. The account book is Attio, with companies, deals, notes, contacts and the review list for the week. The commercial detail often arrives somewhere else. A customer's email in Outlook moves a renewal date, changes a seat count or names a new decision maker before anyone updates the record. A dossier that quietly picks one version is worse than no dossier. If it takes the email's renewal date over the record's, the review never learns the record is wrong. If it takes the record's, the review misses the customer's news. The other failure is scope: an account included because it sits next to one on the list, or a message counted from a folder or sender that is out of scope this week. ## Who works in the room People - Account review lead Sets each week's scope, reads every dossier before the meeting and decides which disagreements matter - Account executives Own the accounts, settle open questions with customers and correct the Attio record after the review - RevOps Owns the review rules and the dossier standard, and confirms corrected records Agents - NovaScope keeper Settles the roster from the Attio review list, the in-scope mail folder and the excluded senders, and works out what a revised scope changes AttioOutlookGoogle Drive[Slack](https://kylon.io/integrations/slack) - MycoDossier writer Writes one Google Doc per account to the dossier standard, states each disagreement with both values, and issues new versions without touching old ones Google DocsAttioOutlook Each week's review gets a new thread in the same room. Nova is the default agent, so a question such as whether an account is on the roster goes to it, and Myco writes the dossiers. Both read Attio and Outlook through the review lead's own accounts, checked on every call, and the room guidelines say nothing is written to either. Once scope is settled, Nova opens a thread for Myco whose first message is the roster, the in-scope folder and the excluded senders. ## Scope first, then dossiers, then versions The dossier standard in Google Drive fixes the title, five headings in order and the shape of each line. The Position and Open deals lines always carry the values on the Attio record, whatever the mail says. ```mermaid flowchart TD notice([The review lead posts the
week's scope notice]) scope["Nova settles the roster and
the in-scope mail folder"] confirm["Review lead confirms scope
before any dossier is written"] dossier["Myco writes one Google Doc per
account with the record's values"] both["Myco names both values where
the record and the mail disagree"] read["Review lead reads each
dossier before the meeting"] revised([A notice revises the roster
or the mail scope]) fix["Account executives fix Attio
once the review has decided"] check["Nova checks each standing
dossier against the new scope"] revops["RevOps confirms
the corrected record"] which["Review lead confirms which
dossiers need re-issue"] left([A dossier that still covers
everything is left alone]) reissue["Myco issues a new document
at the next version number"] approve["Review lead approves
each new version"] notice --> scope --> confirm --> dossier --> both --> read read --> fix --> revops read --> check revised --> check check --> which which -->|still covers| left which -->|re-issue| reissue --> approve class scope,dossier,both,check,reissue agent class confirm,read,fix,revops,which,approve person class notice,revised,left event classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712 classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712 classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42 ``` | Stage | What happens | Who acts | Who decides | | --- | --- | --- | --- | | Scope | The roster is taken from the Attio review list entries, and the in-scope mail folder, matching rule and excluded senders are written down | Nova | The review lead confirms scope before any dossier is written | | Dossiers | One Google Doc per account on the roster, following the standard, with record values in Position and Open deals | Myco | The review lead reads each dossier before the meeting | | Disagreements | Where an in-scope message states a value the Attio record contradicts, the dossier names both, cites the record and the message, and stops | Myco | The review decides which value is right | | Record fixes | Any correction the review agrees on is made in Attio by the account owner, outside the dossier | Account executives | RevOps confirms the corrected record | | Revised scope | A notice changes the roster or the mail scope, and each standing dossier is checked to see whether it still covers everything | Nova | The review lead confirms which dossiers need re-issue | | Re-issue | Each affected dossier is issued as a new document at the next version number, and earlier versions stay as they were | Myco | The review lead approves each new version | Stages of one weekly account review. Accounts, versions and values in this example are illustrative. ## When the roster or the mail scope is revised A revised scope does not mean rewriting everything. Nova reads the notice, works out which accounts joined or left the roster and which messages now count, and checks each standing dossier against the new scope. A dossier that still covers everything is left alone. One that misses an in-scope message, or cites a message now out of scope, is marked for re-issue. Re-issue means a new document. Myco creates the next version with the full versioned title and leaves the earlier one untouched, so the review can see what changed between versions, and no dossier is ever deleted. Nothing is written to Attio or Outlook at any point. The disagreements wait for the review, and the account owner fixes the record once the review has decided. ## What the checks catch - An account added because its ID sits next to one on the list, or because it shares a segment, when only list entries count - A message from a folder or sender that is out of scope this week - A dossier that picks between the record and the mail instead of stating both values - A Position or Open deals line that carries an email's value instead of the Attio record's - A re-issue that would overwrite the earlier dossier, created as a new version instead ## What stays with people - Deciding every disagreement between the record and the mail - Correcting the Attio record, which the account owner does after the review - Confirming scope each week and approving each re-issued dossier - Anything said to the customer ## Integrations in this workflow Kylon is not a CRM, and it does not replace Attio. It reads the account book and the mail side by side and keeps each dossier clear about where the two disagree. - Attio - Google Docs - Google Drive - Outlook - [Slack](https://kylon.io/integrations/slack) - **Attio** holds the companies, deals, notes, contacts and the weekly review list, read and never written - **Outlook** carries the customer mail with the commercial detail, read from the in-scope folder only - **Google Docs** holds the dossiers, one per account per version - **Google Drive** keeps the review rules, the dossier standard and each scope notice - **Slack** is where the review lead posts the week's scope notice and account executives ask about their dossiers ## Where to start Start with next week's review list. Connect Attio and Outlook through the review lead's account and put the dossier standard in the Drive folder. The room guidelines need one rule from the first day: dossiers report disagreements with both values and never resolve them, and nothing is written to Attio or Outlook. > “The dossier does not settle the argument between the record and the inbox. It makes sure the review sees it.” ## Set it up with your agent Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it. Set-up prompt Set up our account review dossier desk in this Room. Take it one step at a time and wait for my OK before you move on. 1. Connect Attio, Google Docs, Google Drive, Outlook and Slack. Tell me which ones still need connecting. 2. Ask me who works this desk: the account review lead, the account executives who own each account and the RevOps person who confirms corrected records. Help me invite them to this Room. 3. Build an Account Review App with Account, Dossier, Disagreements and Status columns, one record per account on this week's roster. Pull the roster from the Attio review list. 4. For each account, read the in-scope Outlook folder alongside the Attio record. Where a message states a value the record contradicts, name both values and cite each source. Flag any message from an excluded sender or out-of-scope folder and mark each disagreement in the App. 5. Write one Google Doc per account following the dossier standard in Google Drive. Position and Open deals carry the Attio record values only. Write nothing to Attio or Outlook at any point. The review lead confirms scope before any dossier is written and reads each dossier before the meeting. 6. When scope changes, check each standing dossier. Re-issue affected ones as new documents at the next version number, leaving earlier versions untouched. The review lead approves each new version. 7. Write the rule order and who approves what into this Room's guideline, so every weekly cycle follows it. 8. After one clean review cycle, offer to turn the weekly roster pull and dossier drafts into an Automation. Before you start, ask me for our rules one at a time. [Get started](https://app.kylon.io/sign-up) Your first company harness. Where humans and agents run your business together. [Get started](https://app.kylon.io/sign-up) ## More Use Cases [View all](https://kylon.io/use-cases) [ ### Price List Migration: Each Account Moves Once, at the Right New Amount Moving thirty wholesale accounts to a new price list means a disposition, an amount and sometimes a notice for each one. In a Kylon room, agents read HubSpot, Stripe and Mailchimp to propose them, and the revenue operations lead approves every change before a notice goes out. Retail & e-commerceRevenue operationsEmail operations ](https://kylon.io/use-cases/price-change-migration)[ ### Experiment Readouts: Ship Calls That Stay Right When the Data Is Corrected Closed experiments are called under a fixed rule order from analytics and flag pull requests, the analyst's summary is audited, and recounts, guardrail retractions and threshold changes re-derive exactly what they should. The experimentation lead approves every call. Software & SaaSResearch & intelligenceEngineering operations ](https://kylon.io/use-cases/experiment-readout-review)