Start with the decision, not the identity
An unfamiliar request gives you little to work with. A name, photo or opening line can be copied or invented, so treating it as proof of who is writing is a weak basis for a choice. The practical question is simpler: do you want a conversation with this sender?
That framing also tells you what each option does and does not do. Accepting is a decision to talk. Deleting is a decision not to engage right now. Blocking and reporting are separate actions taken in the mobile app, not part of the request screen itself.
Viber message requests are available in selected countries; accepting moves a request into the regular chat list without requiring the sender to be added as a contact. Source
Because accepting does not add the sender as a contact, the request moves into your normal chat list and the conversation continues there. If you are unsure, you can leave the request unaccepted while you decide; nothing in the reviewed material requires a test message, code or payment to judge it.
What each choice actually does
| Choice | What it does | What it does not do |
|---|---|---|
| Accept | Moves the request into your regular chat list; the sender does not need to be added as a contact | Does not verify who the sender is |
| Delete | Removes the request from the requests view | Does not stop the sender messaging again |
| Block / report (mobile) | Separate actions in the mobile app | Not the same as deleting the request |
Deleting a request does not prevent the sender messaging again; blocking and reporting are separate mobile actions. Source
The distinction matters most when a request feels unwanted. Deleting clears the item but leaves the door open for another attempt, so if the goal is to stop contact, deleting alone does not accomplish it. Blocking is the action aimed at stopping further messages, and reporting is a separate step for flagging the sender. The reviewed claims describe these as mobile actions; they do not establish a desktop equivalent or an exact menu path, so check the current app rather than assuming a layout.
Do not confuse switching off the inbox with blocking
A common assumption is that turning off the requests inbox will keep strangers away. It does the opposite of filtering them out.
Turning off the requests inbox routes such messages into the regular chat list instead of blocking them. Source
So if your aim is to reduce unfamiliar contact, switching the inbox off works against that aim. Keep the inbox on if you want a separate place to review requests before they reach your main chat list, and use blocking for senders you do not want to hear from again.
A checklist you can apply to any request
This is a proposed way to organize the decision, not a test we ran. No outcome or accuracy figure is implied.
- Ask whether you want the conversation. If yes, Accept is the matching action. If no, do not accept.
- If you want it gone but are not ready to act further, Delete removes it from the requests view — knowing the sender can try again.
- If you want contact to stop, use the mobile block action rather than relying on Delete.
- If the message is abusive or deceptive, treat reporting as its own step alongside blocking.
- Leave the requests inbox enabled unless you deliberately want unfamiliar messages routed into your regular chat list.
- Do not send a test message, code or payment to work out whether a request is genuine. The reviewed material does not make any of these a requirement for judging a request.
Common failure paths
- Deleting and expecting silence. The sender can message again; deleting is not blocking.
- Switching off the requests inbox to avoid strangers. Their messages move into the normal list instead of being blocked.
- Accepting to “find out who it is.” Accepting starts a conversation; it does not verify identity.
- Assuming a desktop block exists. The reviewed claims describe blocking and reporting as mobile actions.
Where TraceSeek fits, and where it does not
TraceSeek is a separate app for searching publicly accessible profile candidates from a username, with 3,000+ platforms covered. It is not a Viber setting and cannot accept, delete, block or report a request, change your Viber settings, recover a private account or verify who a sender is. A public username match is a lead, not proof of ownership.
If the request is tied to a profile you are being asked to share, the more useful next step is to review that account task before you expose anything: review the related account task.
The short version
Choose by intent: Accept if you want to talk, Delete if you want the request out of the way but accept that the sender can return, and use the mobile block and report actions when you want contact to stop or the sender flagged. Keep the requests inbox on if you want that separate review step, because turning it off sends unfamiliar messages straight into your normal chat list.