Connection issues
| Issue | What to do |
|---|---|
| ”Access blocked: this app isn’t verified” on Google’s screen | Google Calendar is in early access while Google reviews our app, so connections are limited to approved accounts. Email support@voqo.ai with the Google account you’ll connect with to request access. |
| OAuth consent screen never appears | Check your browser’s popup blocker — Google’s consent screen opens in the same tab but some extensions interfere. Try again in an incognito window with extensions disabled. |
| ”Reconnect required” badge on the card | Your refresh token was revoked at Google (or expired after long inactivity). Click Reconnect and complete OAuth again. Your agent settings are preserved. |
| Connected the wrong Google account | Click Disconnect, then Connect again, and sign in with the right account. Make sure you’re signed out of the wrong account in your browser first. |
| ”Authorisation failed” after returning from Google | The redirect didn’t complete cleanly — usually a transient browser issue. Try again. If it persists, try in a different browser. |
Availability issues
| Issue | What to do |
|---|---|
| Agent says “I can’t check the calendar right now” | A transient network or Google API issue. The call continues normally. If this happens repeatedly, contact support. |
| Agent never offers any slots | Check that your Look-ahead window is long enough to contain free time (e.g. if your calendar is solidly booked for the next 5 days, no slots will be found). Try increasing Look-ahead or reducing Minimum notice. |
| Agent offers slots that conflict with existing meetings | The calendars selected on the action may not include the calendar the conflicting meeting is on. Open the action config and tick the missing calendar in the Calendars dropdown. |
| Slots are in the wrong timezone | Set the Default timezone field to your office’s IANA timezone (e.g. Australia/Sydney). If the caller mentions a different timezone on the call, the agent will use the caller’s timezone — but the default kicks in when neither is known. |
| Slots don’t respect my working hours | The integration uses your calendar’s free/busy windows, not your Google working-hours setting. Block out non-working hours on your calendar (e.g. as recurring busy events) so they show up as busy. |
Calendar picker issues
| Issue | What to do |
|---|---|
| Calendars dropdown is empty or “Couldn’t load calendars” | A transient Google API issue. Close and re-open the action config — the dropdown will retry. If it keeps happening, contact support. |
| A shared calendar I expected isn’t in the dropdown | The Google account you connected needs at least “See free/busy information only” access to that shared calendar. Ask the calendar owner to share it with the connected account, then re-open the action config. |
| I deleted a calendar in Google but it’s still selected on my agent | Re-open the action config — the dropdown will refresh from Google and you can remove the dead calendar from your selection. |
Permission issues
| Issue | What to do |
|---|---|
| Connected but the agent never uses the action | Check the agent’s Conversation Settings → Function Calls — the GCal — Check Availability action needs to be added to that specific agent (not just connected at the workspace level). |
| Removed the Voqo permission at Google but the integration card still says Connected | The card will flip to Reconnect required the next time it tries to use your calendar. To force the update, click Disconnect in Voqo and reconnect. |
When to contact support
Contact support if:- You’ve tried the steps above and the issue persists.
- You’re seeing repeated errors across multiple calls.
- The agent’s calendar lookup is consistently returning slots that conflict with real meetings.