What happens if the AI service is temporarily unavailable?

Simple Chat is built for reliability when AI providers or networks hiccup. The app uses multiple AI models with automatic failover, and the live dashboard connection includes automatic reconnection so conversations are not left hanging after a brief outage.

Merchants do not manage model routing or provider keys—the platform handles fallback so support keeps moving when a primary model is temporarily unavailable.

Automatic model failover

Primary AI models handle customer-facing replies and supporting tasks under normal conditions. If the primary model is unavailable, Simple Chat automatically falls back to alternative models to ensure uninterrupted service.

That failover happens behind the scenes. Your customers should not need to know which provider is active; they continue in the same thread while the system routes work to a healthy model.

WebSocket reconnection for live updates

The merchant dashboard and storefront chat experience rely on a WebSocket connection for real-time message delivery. If the network drops briefly—Wi-Fi blip, laptop sleep, mobile handoff—the connection includes automatic reconnection logic.

Staff viewing a live conversation should see updates resume without manually refreshing the page once connectivity returns.

What this means for your team

During provider outages or network interruptions, expect temporary delays rather than permanent stuck states. If something looks wrong for more than a moment, refresh the dashboard or ask the customer to reload the storefront page—but in most cases the built-in failover and reconnection recover on their own.

You do not need a runbook for switching models or API keys; focus on reviewing conversations after incidents the same way you would for any support spike—confirm replies stayed accurate and escalate any thread where automation paused mid-issue.