One check at a time. Read what changes.
- 01
Connection
Update the app and use a reliable connection.
What this tells youA reliable connection and current app reduce basic technical uncertainty.
Check your own connection before another attempt. Do not reset storage or erase chat history just to clear a send error.
- 02
Account notice
Read any restriction or error notice.
What this tells youThe exact notice can distinguish a general failure from a stated account restriction.
If a restriction is shown, follow its explanation. Repeated sending or another account is not a way around it.
- 03
Report
Use official reporting if basic troubleshooting does not resolve it.
What this tells youA useful report describes the symptom and checks already completed.
Use the official reporting route. Include relevant app/device context and the exact error, without sharing passwords or codes.
The next step depends on the evidence.
| What you see | Useful check | Avoid assuming |
|---|---|---|
| Connection problem | Check your network and app state. | That a contact blocked you. |
| Account notice | Read the stated restriction and offered official route. | That repeated retries will remove a restriction. |
| Couldn’t send | Keep the exact wording and the context of the attempt. | That the label identifies one particular cause. |
| Delivered, no reply | Read receipt meanings before troubleshooting sending. | That a successfully delivered message is a send failure. |
A failed attempt and a later result.
A send error after many messages calls for reading the account notice rather than repeatedly retrying.
Couldn’t send
The illustrated message has an error label. Stop and inspect the connection or account notice.
Sent — if confirmed
After the relevant issue is resolved, inspect the actual new status. A successful retry is not guaranteed and does not mean Seen.
Make the next attempt informative.
Technical conditions changed
After addressing the connection or app issue, check the next visible result. Keep track of which message has which label.
Interpret the result →The account notice is specific
Follow the official account route. If there is other evidence of unauthorized access, review your own account security.
Review owner-account security →The conversation is unavailable
Read the notice as a separate symptom. Do not test the other person through new accounts.
Understand an unavailable chat →What to include in an official report.
The exact notice, when it appeared, your app/device context and the basic checks you tried. Keep unrelated private conversations out of the report.
Keep this boundary.
The error alone cannot prove that the recipient blocked you.
A missing reply and a failed send are different symptoms. Do not use repeated messages to probe a contact boundary.
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.
Troubleshooting connection, app and account restrictions.