Three minutes. One Google sign-in. After this, Sara can check whether you’re free at the time a caller wants and book the appointment directly onto your calendar — same as if you’d done it yourself.
That link contains a one-time, signed token that expires in 14 days.
It opens Google’s real consent screen — not a Regulance form —
so you can verify the destination domain in your browser’s
address bar (accounts.google.com) before signing in.
Lost the email? Write services@regulance.ai and we’ll re-send a fresh link in a few minutes.
Google will list every account you’re signed into. Pick the right one — appointments will land on whatever calendar that account controls. If you have a personal Gmail and a Workspace account, this is the moment to choose carefully.
Regulance is currently in Google’s verification queue. Until that finishes, Google shows a yellow warning screen on the consent flow. The screen is part of Google’s normal review process and not a sign anything is wrong. See the next section below for the exact clicks.
Google will show you the specific Calendar permissions Regulance is requesting. There are two:
Sara does not read your emails, contacts, Drive, or any other Google service. Calendar only. You can revoke this any time at myaccount.google.com/permissions.
That page confirms the calendar email Sara is now linked to. Within a few hours we’ll send a second email with your Regulance forwarding number — then it’s on to Step 2: forwarding your line.
A yellow screen titled Google hasn’t verified this app. It says the app is requesting access to sensitive info and recommends you only continue if you trust the developer. There is no obvious Continue button — that’s by design.
Here is exactly how to get past it — Google requires three deliberate clicks so you can’t do it accidentally:
It’s small grey text under the body copy, not a button. Clicking it expands a section explaining what verification means.
Yes, the word (unsafe) is in the link. Google adds it to every unverified-app flow regardless of how the app actually behaves — it’s a generic disclaimer, not a verdict on Regulance. Clicking it takes you to the real permissions screen described in step 4 above.
From here on it’s the normal Google consent flow. You’ll see the two specific Calendar permissions Sara needs, click Continue, and you’re done.
Google requires every app that touches “sensitive” user data — Calendar events count — to go through a manual verification review. The review takes anywhere from a few weeks to a few months depending on the queue.
Until our verification clears, Google flags the consent screen with the yellow warning. The warning is not based on any actual analysis of the app — it’s a default for any unverified developer. Once verification finishes, the warning disappears and existing connections keep working exactly as before. You will not have to reconnect.
If you’d rather wait until verification clears before connecting, you can — but Sara can’t book on your calendar in the meantime, so callers who want an appointment will be told a team member will call them back.
She does not:
Next: forward your business line to the Regulance number we send in the second email. That’s the last setup step before your line is fully live.