Video-call safeguard — impossible to promise a video call that will never happen
A service can't offer Zoom or Meet without the corresponding account connected.
The problem
Enabling Zoom or Meet on a service without having connected the corresponding account would create an empty promise: the client books, but no link ever arrives.
Without a safeguard, this configuration error is only discovered when a client complains.
A service can't offer Zoom or Meet as long as the corresponding account isn't connected.
Without Kagenda
A service offers Zoom, but the Zoom account was never connected: no link ever arrives.
With Kagenda
Impossible to activate Zoom on a service before the corresponding account is connected.
How it works in Kagenda
The safeguard checks the account connection before allowing activation.
- You try to activate Zoom or MeetOn a service.
- Kagenda checks the connected accountZoom or Google, depending on the choice.
- Activation only succeeds if the account existsOtherwise, the screen shows what to connect first.
Check before activation
- Account required
- Not connected → blocked
- Connected → activatable
In practice
- 1
An unconnected Zoom account
Activating Zoom on the service is blocked.
ZoomAccount not connected - 2
A connected Zoom account
Activation becomes possible, with no other step.
Account not connectedAccount connected - 3
No empty promise
The client can never book a video call that won't happen.
ResultNo broken promise
Frequently asked questions
What happens if I disconnect my Zoom account afterward?
The services in question stop offering Zoom, to avoid an empty promise.
Does this safeguard also concern Google Meet?
Yes, the same check applies to both integrations.
Is the personal link subject to this safeguard?
No, it doesn't depend on any connected account.
Can I bypass this check?
No, it directly protects your clients from an appointment with no link.
