Find any message you've sent
Wap2b keeps two logs. Picking the right one takes ten seconds and saves ten minutes.
Which log
Message logs — everything. Every message on the account, however it was sent: chatbox, broadcast, API or automation, inbound replies included, each with its delivery status and what it cost.
Broadcast log — broadcasts only. Every recipient of every broadcast, with delivery status. Search by contact number, or filter by date, broadcast or template.
| Your question | Open |
|---|---|
| Did this customer get my campaign? | Broadcast log |
| What is our whole history with this customer? | Message logs |
| What did that message cost? | Message logs |
| Which broadcast underperformed? | Broadcast log, or Analytics |
| What is our API integration actually sending? | Message logs, source filter |
| Why did this message fail? | Message logs |
The short version: broadcast log for a campaign, message logs for a person or a cost.
The source filter
Message logs carry a Source filter — chatbox, broadcast, API, automation. It is the fastest way to answer "what is that integration doing?" without wading through everything else.
Tracing one message
- Open Message logs.
- Search the customer's number.
- Find the message by date. The row gives you its status, its source and its cost.
- If it failed, the reason is on the row — A message failed decodes them.
- To tie it to a charge, match it against Wallet.
Answering "we never received it"
Almost always resolvable in under a minute:
- Search their number in message logs.
- No row at all → it was never sent. Wrong number, or they were excluded from the broadcast (opted out, or beyond the 500 cap).
- Failed → the reason is on the row.
- Sent but not delivered → their phone was off or offline.
- Delivered → it reached their device. Ask them to check archived chats and whether the number is blocked.
If something goes wrong
- A message you know you sent is missing. Check the date filter, and check you are in message logs rather than the broadcast log.
- The broadcast log does not show a chatbox message. Correct — it never will. Use message logs.
- Costs look wrong. Wallet is the authoritative record.
- You cannot open message logs. Agents do not have access, because the log carries per-message costs. See Work as a team.