Identify what needs to change
Published September 10, 2026.
Ask whether the customer needs a display name, contact name, billing record, contract, or regulated identity record changed. These fields can follow different rules. Use the customer's current name in conversation unless a legal or system requirement prevents it.
Use proportionate verification
Confirm account control through the approved method. Request only the documents or data required for the specific record and jurisdiction. Provide a secure upload channel when evidence is necessary. Never ask the customer to expose sensitive documents in ordinary email or chat.
Map downstream systems before saving the update. Billing, shipping, identity, and marketing tools may synchronize differently. A permission review helps ensure the change does not alter account access.
The NIST Digital Identity Guidelines provide verification context. Use the customer name correction routine for lower-risk display errors.
Confirm without overexposing
Tell the customer which records changed, which remain pending, and when they can expect completion. Keep prior values only where retention rules require them, with restricted access. Audit rejected requests for unclear instructions and inconsistent evidence standards.
FAQ
Is a display-name update the same as a legal-name change?
No. A display preference may require less evidence and should not silently overwrite regulated records.
Should agents store identity documents in case notes?
No. Use the approved secure evidence system and retention policy.