Preserve the submitted target
Record the exact address and channel name used for any active request. A new public name should not cause you to overwrite the original order history. Keep the time of the change so the sequence is understandable.
Verify the current destination
Open the target and confirm that it still identifies the intended channel. Ask about compatibility if the service depends on the original input. Do not assume every listing or saved automation handles a changed name in the same way.
Update future briefs carefully
Once the current address is confirmed, revise future order templates and client documents. Keep a note connecting old and new identities where relevant. Avoid creating another request solely because the display name looks different before checking the active order’s status.
Decision checklist
| Decision | What to check |
|---|---|
| History | Original submitted name and URL |
| Current target | Confirmed channel destination |
| Templates | Future briefs updated after verification |
Worked example
In an illustrative rebrand, a streamer changes the channel name before a scheduled session. The buyer checks the current destination, informs support about an active request if necessary, and updates future briefs without deleting the old reference.
Example figures explain the decision; they are not current prices or promised results.