Before the call
Use Driver to prepare an account brief from a selected set of Jira tickets. Gather the account’s stable identifier, the ticket URLs, and the period you want reviewed. Supply any aliases or parent/sub-account relationships so similarly named customers are not combined.
- Select the account’s relevant tickets in Jira and give Driver their full URLs. The agent needs access to those projects. Include reviewed handoffs or incident summaries that contain facts from teammates’ private investigations.
- Ask in Driver: “Prepare a brief for account acct_acme from only these tickets for October 1 through October 31 UTC. Group duplicate reports of the same issue. For each issue, show the supporting tickets, current status, confirmed finding, customer consequence, workaround, next action, and owner. Mark unknowns and unreadable tickets.”
- Review the account mapping and source citations. Confirm whether an issue affects this account, might affect it, or was ruled out. Include the record with the account ID, environment, and timestamp when a claim depends on runtime impact.
- Check Jira’s current ticket states and confirm any release or deployment statement with its owner. Ask Driver to list unresolved questions separately so you can get answers before the call.
- Copy the reviewed brief into your account notes. Update the Jira tickets with new customer facts and the next action your teammates need to take.
The brief should let you explain each open issue, the evidence behind its status, and who owes the customer an update. Label its ticket set and capture date; refresh it when ticket or rollout information changes. To estimate impact across multiple accounts, use the account-counting recipe.