Common issues
Five issues we see most often, with the fastest fix for each.
Widget not showing on my site
If the script loads but no UI appears, check two things. First, the website's Content Security Policy must allow script-src and connect-src for *.dineos.com. Second, the website's origin must be on the widget's allowlist in Settings → Widget → Allowlist. The widget refuses to render on unknown origins by design.
SMS confirmations not arriving
If reservation SMS confirmations are not delivered, the Twilio sender pool likely has no available number for the destination country. Check Settings → Integrations → Twilio to confirm at least one verified sender exists for the relevant country code. Add one if missing — it takes a few minutes to verify.
No-show prediction badges missing
The no-show prediction badge does not appear until the restaurant has at least 30 days of reservation history. Until then, the field is blank in the reservation list and the model is not invoked. There is nothing to enable — the badges appear automatically once the data window is large enough.
Mobile push notifications not arriving
First, check that notifications are enabled for the DineOS app at the OS level (Settings → Notifications on iOS and Android). Then check Settings → Notifications inside the DineOS app — the category may be muted, or quiet hours may be in effect. Critical notifications bypass quiet hours; if those are also missing, sign out and sign back in to re-register the device token.
AI assistant not responding
If the assistant does not respond, the most common cause is an outage at the upstream model provider. Check the status page (link in the sidebar). If everything is green, refresh the page once — the websocket connection occasionally needs to be re-established after a network blip.