Find the request. Verify the sender.
- 01
Requests
Open the current request-management view.
What this tells youA request or spam area can explain why a conversation is outside the normal inbox.
Review only your own account. A missing main-inbox entry does not by itself prove deletion or a failed delivery.
- 02
Sender
Review the sender before following links or replying.
What this tells youYou have checked the identity and context independently of the message’s claim.
A familiar display name or support claim is not verification. Do not use a link supplied by the request as your only check.
- 03
Response
Use report or block controls for a suspicious request.
What this tells youThe response fits the risk and the boundary you want.
Read the current Accept, Delete, Report or Block prompt. If reporting matters, review the relevant context before removing your copy.
Where a conversation appears matters.
| Area or action | Why inspect it | Important boundary |
|---|---|---|
| Regular chats | An existing conversation may be in the normal list. | Placement does not verify every message or link. |
| Message requests | An unfamiliar sender may be routed here. | Receiving a request is not an obligation to accept it. |
| Spam area | Review separately if your account offers it. | A message here may still need careful sender checks. |
| Accept or delete | Read the effect before confirming a response. | Acceptance can change the interaction; deletion is not the same as blocking. |
From unfamiliar request to a considered response.
An unfamiliar “support” request demanding a code should be verified through an independent official route.
Request waiting
An unfamiliar sender asks to share a plan. You have not established who they are.
Identity checked first
Verify through a route you already trust. Then decide whether to accept, delete, report or block using the current prompt.
Choose a response without rushing.
The context checks out
Read what accepting or replying will change. A legitimate request can still be declined.
Choose your contact boundary →The sender claims a false identity
Keep relevant context and use the official reporting flow. Verify independently before following instructions.
Review impersonation reporting →The chat is still missing
A request check is one possible location check. Distinguish an archived conversation from genuinely unavailable history.
Check for an existing copy →A request asking for a code.
Stop the interaction and use the official service independently. Do not provide the code here, in the request, or to a tool claiming to verify the sender.
Keep this boundary.
Moving or accepting a request can change the interaction; read the current prompt.
Never send a password or verification code in response to a request. A support-themed name is not evidence that the sender represents the service.
References and current instructions
Go to the source.
Labels, menu placement and feature availability can change. These are original interface illustrations; use the current official explanation before changing a setting.
Find the current article for your device and account type.