Self-service reduces repeated entry when members can propose permitted changes and staff can review them in context. It does not remove the need for identity matching, configured fields or an independent decision. Test the complete request lifecycle before broad use.
Step 01
Confirm identity and permitted fields
Use a correctly matched member account and check which contact or address fields the configured person type permits. Explain the support path for an ambiguous identity. Staff-only fields should remain outside the member change experience.
Step 02
Compare current and proposed values
Submit a controlled change, then review it as a separate authorized staff member. Check whether the maintained record changed since submission. Investigate a stale request before deciding; the requester should not approve their own change through another staff responsibility.
Step 03
Explain the result to the member
Test approval, rejection and cancellation of a pending request. Confirm that the member sees the resulting status and the maintained profile reflects only the permitted decision. Keep a support owner for requests that cannot be resolved from the supplied evidence.