Contact Entry Recovery Request Boundary | Source Path, Message Wording, and Local Record
A contact entry recovery request should be paused and recorded before any reply. The answer is to separate the source path, message wording, device screen, and local record so the reader can return to the intended support or setup path.
Source path identifies where contact started
Write the page, app view, or service route that started the contact. remote assistance request check gives a related example of separating contact path from device-side prompts.
Message wording defines the boundary
If the wording asks for recovery material, record the exact message and pause the conversation. The recovery record belongs outside ordinary contact fields and should not be typed into a message thread.
Device screen stays separate from contact text
- Source path and contact entry.
- Exact recovery request wording.
- Device screen prompt, if any.
- Local record before the next reply.
For recovery-record handling, recovery phrase review explains how recovery material should be checked as an offline record.
Next step returns to the intended route
The final note should point back to the intended app, service, or setup route. If the question started from a purchase conversation, purchase conversation pause point provides a matching record structure.
