# Authorized account contact change survey

Find verification and notification-routing gaps when a customer organization changes its authorized service contact.

If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.

## 1. Which types of notices still reached the former contact after the change?

Answer: ____________________

## 2. How were you told the replacement contact was authorized to act for the account?

Answer: ____________________

## 3. Which open request needed a separate routing update?

Answer: ____________________

## Author notes / illustrative keys where applicable

1. Identify the notice category and delivery step still using the old contact, so the service team can locate a stale notification route without collecting names or addresses.
2. Distinguish an announced contact replacement from a confirmed permission change. Ask which verification step was explained; a respondent's confidence cannot establish that authorization was actually granted.
3. Find requests whose recipient was stored separately from the account contact. This helps the request owner check outstanding communication rather than assuming one profile update reroutes everything.

Interpretation caution: Collect notice categories and routing steps, not personal contact details or identity documents. Feedback does not verify authorization.


## Illustrative finding and follow-up

Observation: In a synthetic example, the new contact receives general account notices but an older open request still sends updates to the former contact.

Action to test: Check the authorized-contact change and the open request's separate notification route, then explain which updates were completed and which require an owner.

Follow-up: After those routing changes, ask the new contact which notice categories arrived and whether the old request still required another update. Accept that no routing issue remained; do not infer permissions from receipt alone.