Uptime and reliability: questions to ask a chatbot vendor before you commit

Updated 2026-09-19 · 5 min read · By the Convo360 team

Why 'uptime percentage' alone doesn't tell you much

Vendors often lead with a headline uptime number, but for a WhatsApp or voice bot, the platform being technically 'up' is not the same as your bot actually working. The more common failure in practice is your own connected provider: your AI key running out of credit, a telephony account's balance hitting zero, or a WhatsApp access token expiring, silently breaking the bot while the platform itself reports no incident at all. The right questions focus on how a vendor handles these everyday failure points, not just their own server uptime.

This is worth pressing on specifically during a sales conversation, because 'uptime' is an easy number to quote and a hard one for a customer to verify independently. Asking for the failure scenarios above, and how each is actually surfaced to you, tells you far more about day-to-day reliability than a percentage on a website.

What happens when your AI or telephony provider fails

Since a BYOK platform depends on your own connected keys and accounts, ask specifically: does the platform detect when your OpenAI, Claude, Gemini, or telephony provider starts returning errors, and does it tell you clearly, or does it fail silently until a customer complains? This is the single most common real-world 'my bot stopped working' cause, and it has nothing to do with the platform's own servers.

Backups: frequency, scope and how restore actually works

Ask three specific things, not just 'do you back up data': how often (nightly is a reasonable minimum), what's included (conversation history, contacts, flows, uploaded media, not just the database), and whether you've actually seen a restore work, versus it being an assumption nobody has tested. A vendor who can answer specifically ('nightly database backup, plus a separate nightly media/uploads backup') is giving you a real answer; 'we have backups' with no detail is not.

It's also worth asking how far back backups are retained. A nightly backup that's overwritten the next night protects against a server failure but not against a mistake discovered a week later. Retention of at least a few daysgives you a genuine safety net rather than a single point-in-time snapshot.

What happens to a failed broadcast send

A WhatsApp broadcast or campaign to thousands of contacts will occasionally hit individual failures: a number that's blocked the business, a template rejected mid-send, a temporary rate limit from Meta. Ask whether the platform retries these automatically or simply marks them failed and moves on, since the difference between the two can mean hundreds of customers missing an important message (an appointment reminder, a payment notice) without anyone noticing unless someone manually checks the send report.

Can you see what's happening without opening a ticket

Ask whether you get visibility into conversation logs, delivery status and provider errors directly on your own dashboard, or whether diagnosing a problem always means waiting on support to check logs you can't see yourself. Being able to look at a flow's execution log and see exactly which step a specific conversation failed on is a meaningfully faster way to fix an issue than describing symptoms over a support ticket and waiting for a reply.

This also matters for accountability during a busy period. A festival campaign or a sudden spike in enquiries is exactly when something is most likely to go wrong, and exactly when waiting on a support queue to diagnose it is most costly. Self-serve visibility into logs and status turns a potential half-day delay into a five-minute check.

Ownership: the real insurance policy against vendor downtime

The most important reliability question isn't about the vendor at all, it's about what you own if the vendor has a bad day. If your WhatsApp Business Account, phone number, AI provider keys and telephony account are registered to you (not the vendor), a platform-side outage is an inconvenience you can work around; if the vendor owns these on your behalf, an outage can mean you can't even message your own customers through another channel until it's resolved. Always ask directly: whose name is the WABA registered under, and can I export my number, contacts and flows if I ever need to leave?

How Convo360 answers these questions

Convo360 runs provider-health monitoring that detects when a customer's own AI or telephony provider errors, such as an expired key or an exhausted balance, and shows a clear alert on the dashboard rather than a silent failure. Nightly database and media/uploads backups run automatically. Failed sends in WhatsApp Studio broadcasts get retry handling rather than silently dropping. Analytics and per-step Flow Logs give visibility into exactly where a conversation succeeded or failed, without needing a support ticket to see it. Because the platform is BYOK, your WhatsApp number, WABA, AI provider keys and telephony account are yours, registered to your business and not the platform's, and flow, contact and template data can be exported, so a platform-level issue is never a reason you can't reach your own customers.

Step by step

1. Ask about provider-failure detectionConfirm the platform alerts you when your own AI or telephony provider key or balance fails, rather than failing silently.
2. Get specifics on backup frequency and scopeAsk for the exact schedule and what's included — database, contacts, flows and media — not just 'we have backups'.
3. Check broadcast retry behaviourConfirm failed sends in a campaign retry automatically instead of being dropped without notice.
4. Check what you can see without a support ticketAsk whether conversation logs and provider errors are visible on your own dashboard directly.
5. Confirm ownership of your number and keysVerify your WABA, phone number, AI keys and telephony account are registered to you, and that export is available if you ever switch.

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.