Skip to content
Cascade Cascade
Қазақша Русский English

Use case

For SaaS

Login, invite and access recovery via outbound OTP to the user’s phone.

Quick Answer

For SaaS, Cascade covers login / invite / password-reset: send OTP → user enters code → verify. Cheaper to start with WhatsApp/Telegram.

Summary

In SaaS, OTP covers registration, login and password reset. Cascade delivers the code to a real number; the API key stays on the server.

Key Takeaways

  • The product scenario matters more than the channel choice.
  • Key only on the backend.
  • SMS costs more tokens than messengers.

Related Questions

Contents

  1. Task
  2. Flows
  3. Channels and price

Task

Add phone confirmation to SaaS: registration, login, team invite, password reset.

Flows

Registration / login

  1. The user enters a phone.
  2. The backend calls /otp/send.
  3. The user enters the code.
  4. /otp/verify → you create a session.

Invite

  • The owner invites by phone/link; OTP confirms the number is live before granting a role.

Password reset

  • OTP as a second factor after a reset request; do not expose the key on the client.

Channels and price

  • WhatsApp / Telegram — usually 1 token (cheaper for frequent logins).
  • SMS — 16 tokens, fallback channel.
  • Packages and base: /pricing.

TTL and resend: /faq/ttl-koda, /faq/mozhno-li-povtorno-otpravit. Technical breakdown: /use-cases/developers, guide /docs.

FAQ

Is Cascade suitable for SaaS?
Yes, if you confirm your user’s number rather than renting virtual numbers.
Where to start?
API key → /otp/send → /otp/verify → limits and monitoring in the cabinet.
Documentation API Pricing FAQ