## The channel can stay the same while the purpose changes

Email, SMS or WhatsApp can serve different roles in signing. An **invitation** delivers the document link. A **reminder** indicates that a signature is still pending. An **authentication token** is used at signing time to confirm access to the configured channel.

Separating these jobs prevents an inaccurate promise: delivering a message does not establish that a person read, agreed to or finished signing. Receiving a reminder is not authentication either.

## Configure according to your process

When preparing an envelope, verify contact details and choose channels allowed by the plan. Free uses email invitations. Paid plans provide channels according to the offer; automatic reminders are available from Essencial. SMS and WhatsApp generate additional consumption.

Choose authentication based on risk, the person’s experience and features actually enabled. Do not ask signers to reveal a token to an attendant: they should use it in the designated flow.

## When to add identity verification

A token helps demonstrate access to an email address or phone at that moment. It is not documentary identity verification or proof of card ownership. KYC is a separate layer whose purpose and configuration must be defined for the operation.

Compare [Signature plans](/en/sign/pricing) and explore [KYC](/en/kyc) for workflows requiring additional identification. When connecting steps, preserve records and make clear which information allows each process to continue. This distinction also helps support explain delays without asking customers for unnecessary personal information.