Virtual assistant customer data request triage

Key takeaways

• Use a written brief and definition of done.
• Keep approvals and escalation rules visible.
• Review quality before expanding the workflow.

# Virtual assistant customer data request triage

Separate request scope, identity, source, deadline, and verification state. The assistant can locate records and flag missing proof; the authorized owner decides disclosure or correction.

Applying virtual assistant customer data request triage

Triage should establish whose request it is, which records are in scope, and what proof supports the request before anyone edits or releases data. Separate identity evidence from the requested action, and mark a record as unresolved when the source systems disagree.

Role boundary and review

The assistant may gather records, compare fields, and prepare a discrepancy note. An authorized owner decides disclosure, correction, or refusal and records the reason. Keep the request, evidence, scope decision, and response status together so a later reviewer does not infer approval from a completed search. the [services library](/services) can clarify the assistant's record-finding role, while the [[provider vetting guide](/provider-vetting)](/provider-vetting) helps assess privacy boundaries. [NIST guidance](https://www.nist.gov/itl/smallbusinesscyber) is a useful access-planning reference. ### Request record Keep identity evidence, requested scope, source records, discrepancy notes, authorized decision, and response status.