Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Validate the incoming route and parameters, restore required session state, and authorize access to the destination. Treat the link as untrusted input, not proof of permission.
Parse links through an allowlisted routing model and reject malformed or unsupported destinations. Prefer platform-verified HTTPS links where appropriate, while still validating content and authorization. If login is required, preserve a safe pending destination and continue after authentication without duplicating screens. Handle cold start, already-running state, expired resources, and account mismatch. Avoid arbitrary redirects and sensitive data in link parameters; the server must enforce access to the target resource.