Start with the action they came for.
A visitor wants a place at your webinar, your next newsletter or access to their account. Sendity gives them a short code and a channel action at that moment. They do not need to type an email address or phone number into a separate contact field.
On a phone, the action opens a prepared message in the chosen app. On a desktop, a QR code can take the flow to their phone. The visitor sends the message, then returns to the original browser to continue. Opening the app alone does not complete verification.
A correct code is only the beginning.
Sendity matches the message to a live, short-lived challenge. It also checks the evidence that connects the message to its sender.
For email
The incoming message must pass DKIM verification with an aligned sender domain. This helps reject a message that merely claims another email address in its sender field. Forwarding or mail systems that alter signatures can prevent verification; the visitor can try sending directly or use another supported address.
For WhatsApp
The message comes through the official Meta Cloud API. Sendity authenticates the webhook and requires a provider-observed phone number. A username or business-scoped user ID by itself cannot verify a phone number. Explore WhatsApp verification.
The result means the sender controlled the accepted communication account at that moment. It does not establish legal identity, age or permanent ownership.
Sendity verifies. Your app decides.
The browser can show progress and receive the completed result. Your backend must validate the signed authorization before it trusts the contact or changes application state. That keeps registration, permissions and account sessions under your control.
You decide whether a verified contact creates a lead, signs in an existing user or unlocks a specific action. Store the consent and preferences your product needs alongside that contact. Verifying a channel does not automatically grant permission to send marketing messages.
Use the browser client with the appropriate backend integration, or run your own Sendity server. The quickstart shows how the browser and server pieces work together.
The same verification, different outcomes.
- Webinar registration: confirm a reachable phone account, then reserve the visitor’s place.
- Newsletter sign-up: collect a verified email address and the visitor’s subscription choice.
- Campaign entry: verify the contact before your campaign accepts an entry. Eligibility and duplicate-entry rules remain your application’s responsibility.
- Account access: use the verified identifier to find or create an account, with additional checks where your risk policy requires them.