WapifyDocs

Message logs

Every message Wapify sent, with status, customer reply, failure reason and a one-click resend.

AllCOD ConfirmationUpsellAsk for reviewBack in StockAbandoned CartCampaigns
Search by order number, customer name or phone
TimeAutomationOrderCustomerStatusReply
10:24COD#1001JohnDeliveredConfirmed
10:22Cart—SaraSentLink Sent
10:19Review#0994OmarDeliveredReviewed
10:02COD#0993NourFailedRetry

Every message Wapify has ever sent, with what happened to it. The All tab exists so a failure can't hide behind seven other tabs.

Logs is the record of every individual message: when it went out, which automation sent it, who received it, what happened to it, and what the customer did. It's the first place to look when a number in Analytics doesn't match what you expected.

Tabs

Nine tabs: All, then one per automation, then Campaigns.

All is first deliberately. Every other tab requires you to already know which automation a message came from — and when Analytics tells you "12 failed", there'd be nowhere to reconcile that number. A single failed cart send used to be invisible behind seven other tabs.

What each row shows

TimeWhen the message was sent.
AutomationWhich automation or campaign produced it. On the All tab this is a column; on the others it's implied.
OrderThe Shopify order it relates to, by order name. Empty for messages not tied to an order, such as abandoned carts and campaigns.
CustomerName and phone number.
MessageThe message that was sent, expandable.
StatusSending, Sent, Delivered or Failed — with the failure reason on the row.
ReplyWhat the customer did: Confirmed, Cancelled, Reviewed, Feedback, Link Sent, or No Reply.

Statuses

StatusMeaningWhat to do
SendingIn flight, waiting for WhatsApp to confirm.Nothing — it resolves within seconds, and stale rows are swept after 30 minutes.
SentAccepted by WhatsApp; delivery not yet confirmed.Nothing. Most become Delivered shortly after.
DeliveredIt reached the customer's phone.Nothing.
FailedIt didn't go out. The reason is on the row.Read the reason, fix the cause, then Retry.

Wapify deliberately never records or shows whether a message was read. Replies are the engagement metric, and they're what the Reply column reports.

Common failure reasons

Invalid or missing phone numberThe order has no usable number, or one saved without a country code. Fix it on the order, or fix your checkout so it's collected properly. Retrying without fixing it will fail again.
Monthly limit reachedYour allowance for that message category is used up. Upgrade, connect your own number, or wait for the reset. See Message limits.
Template not approvedOn your own number, that template isn't approved yet. Check the Templates page.
Not a WhatsApp numberThe number is valid but has no WhatsApp account. Nothing to fix.

Search and filter

Search covers order number, customer name and phone number. Filter by status to isolate failures — the fastest way to audit a bad day is the All tab, Status set to Failed.

Results are paginated with a page-size control, and there's a manual Refresh for watching sends land in real time.

Retrying

Failed rows carry a Retry button. A retry is a manual send: it goes immediately, ignoring delays and quiet hours. Fix the cause first — retrying a send that failed on a bad phone number just fails again.

Reminders in the log

Follow-up reminders appear as their own rows, labelled so you can tell a reminder from the first message. They're counted in the same automation's tab, because from an allowance point of view they're the same family of message.

When to use Logs instead of Analytics

QuestionWhere to look
"Did this specific customer get their message?"Logs — search the order number.
"Why did 12 messages fail yesterday?"Logs — All tab, filter to Failed.
"Is my confirmation rate improving?"Analytics — COD Confirmation tab.
"How much revenue did WhatsApp drive?"Analytics — Overview, and Revenue attribution.
"Which campaign recipients didn't get it?"Logs — Campaigns tab, or the campaign's own recipient list.