When something fails, you are told — in your own dashboard, with detail
The worst kind of failure is the quiet one. Every failure the platform detects on your account is recorded where you can see it, with a detail view per incident — so "a third of that campaign never sent" is something you find out on the day, not weeks later from a customer.
- Failures are a screen in your dashboard, not something you have to ask support about
- Visible
- Each entry opens to its own detail view rather than a one-line code
- Per incident
- Available to every signed-in account, whatever you have subscribed to
- Any plan
لمن هذه الميزة
Anyone who has run a campaign on a cheaper tool and discovered days later that a third of it never actually sent.
القلق الذي تجيب عنه
"How would I even know if it broke?" Because it is on a screen you can open, with the detail attached, rather than behind a support email.
How failures reach you
Something goes wrong
A send fails, an external call is rejected, an integration breaks.
It is recorded
The failure is logged against your account rather than swallowed.
It surfaces
It appears in the error list, and as a concern on your dashboard.
You open the detail
Each incident has its own view, so you can see what actually happened rather than guess from a code.
Surfacing failure is a trust decision
Most platforms hide failures behind a support address, because a visible error list looks bad. We take the opposite view: you cannot manage what you cannot see, and a business that finds out about a broken integration from its own dashboard is in a far better position than one that finds out from a customer.
What is recorded
- Failures the platform detected against your account
- A detail view per incident, not just a line in a list
- Errors also surface as a concern on the dashboard, so you do not have to go looking
- Available to any signed-in user, on any plan
Where this fits with the rest
Campaign-level outcomes live with the campaign itself — every recipient carries its own sent, delivered, read or failed status. Account health and messaging cost live on the analytics dashboard. This screen covers the layer underneath both: the things that went wrong at the platform level and would otherwise be invisible.
من الجيد معرفته
أين تتوقف هذه الميزة، بكلمات واضحة — حتى لا يفاجئك شيء بعد الشراء.
- Requires a login only. There is no plan gate — any signed-in account can see its own failures.
- This is an operational log, not a support ticketing system. There is no reply-to-support thread attached to an incident.
- It records failures the platform detected. A failure that was never reported to us cannot appear here.
الأسئلة الشائعة
Do I need a paid plan to see this?
No. Any signed-in account can see its own failures, whatever it has subscribed to. Knowing that something broke should not be a paid feature.
Can I reply to an error to get support?
Not from this screen — it is an operational log rather than a ticketing system. It gives you the detail you need when you do contact support.
Will it show me every failed message in a campaign?
Per-recipient outcomes live with the campaign itself, where each recipient carries its own status. This screen covers platform-level failures, which is the layer that is usually invisible elsewhere.
Why show errors at all?
Because the alternative is a silent gap in your results. A visible failure you can act on today beats a quiet one you discover next month.
اكتشف المزيد من الميزات
اكتشف الأدوات الأخرى التي تجعل WizMessage منصة واتساب الكاملة.
- AnalyticsDelivery performance, messaging spend by category, and account health — on one screen.
- الرسائل الجماعيةمحرّر واحد، وكل أنواع رسائل واتساب، ودليل تسليم لكل مستلم. ليست أداة «أرسل وتمنَّ».
- WhatsApp CoexistenceConnect the WhatsApp Business number you already use, through Meta's own onboarding. Your phone keeps working; automation runs alongside it.
- إدارة الواجهة البرمجيةمفاتيح واجهة برمجية تتحكم بها ويمكنك إبطالها، وويب هوك بزر اختبار وسجل تسليم، وساحة تجربة، ومقاطع شيفرة جاهزة.
- Wiz CopilotAn in-app assistant that operates the dashboard by conversation — and stops at an approval you can read and edit before anything changes.
- Knowledge BaseYour price list, policy or FAQ becomes the chatbot's source of truth. No prompt engineering, no retraining.