Sign-in or OAuth problems
If Google or Microsoft sign-in fails, confirm provider setup is complete in Supabase, redirect URLs are allowed and your browser is not blocking required cookies.
- Try email/password sign-in to confirm the account exists
- Check the URL returns to dashboard.simcoai.co.uk or api.simcoai.co.uk/auth/oauth/callback
- For signup/trial modes, confirm Terms, cookie choice and B2B checkboxes are ticked
- Clear old cookies if a previous OAuth attempt was interrupted
Paid feature blocked
SIMCOAI blocks paid features when subscriptions are missing, unpaid, cancelled, incomplete or outside limits. Billing pages remain available so you can recover access.
- Open Billing and check subscription status.
- Open Add-ons if the feature needs an add-on.
- Check call minutes, number limits and realtime voice entitlement.
- Refresh dashboard after a successful Stripe change.
Call logs are empty
Empty call logs usually mean calls are not reaching the assigned Twilio number, webhook signatures are failing, the account has no eligible phone entitlement, or no calls have completed since setup.
Run a test call from a normal phone.
Check number assignment and caller ID configuration.
Confirm webhook URLs point at the SIMCOAI API.
Contact support with the call time, number and account email.
AI sounds robotic or repetitive
Improve the setup knowledge, shorten the greeting, remove forced closing phrases and make escalation rules clear. SIMCOAI should answer quickly, let callers interrupt and avoid repeating disclaimers.
Say the AI disclosure once near the start.
Use short, natural sentences.
Update policies when the AI hesitates or over-explains.