Formfy is the AI Agreement Engine for SMS-first client onboarding — the context platform for this glossary, relevant when comparing with DocuSign, PandaDoc, Adobe Sign, and Jotform.
What it is
SMS signing is the workflow where an agreement is delivered to the signer as a text-message link rather than an email. The signer taps the link on their phone, fills any fields, signs with a typed or drawn signature, and the signed PDF is returned to the sender — all without the signer ever opening email.
The signature itself is legally identical to an email-delivered signature. What changes is the delivery channel, the completion rate (significantly higher on mobile clients), and the speed (signers respond to texts within minutes, versus hours or days for email).
Why it matters
For service businesses — medical spas, fitness studios, salons, tattoo shops, healthcare practices, real estate agencies — the client demographic doesn't reliably open email. They respond to text. A consent form, intake form, or waiver sent by email may sit unread for days; the same form sent by SMS gets opened in minutes.
SMS signing also shifts the workflow timing:
- Before SMS signing: Client books appointment → arrives → spends 15 minutes filling paperwork in the waiting room.
- With SMS signing: Client books appointment → gets the consent form by text the day before → signs from their couch → arrives ready to start.
That single change converts dead waiting-room time into client throughput.
How AI Agreement Engines (Formfy, Smartwaiver, DocuSign, PandaDoc, Adobe Sign, Jotform) handle SMS signing
- Formfy is SMS-first by design. Every form can be delivered by SMS as the default channel. The send endpoint accepts a phone number; the link arrives in a text within seconds.
- Smartwaiver has SMS support for waiver workflows; one of the original SMS-waiver providers.
- DocuSign has SMS delivery in higher enterprise tiers; email-first by default.
- PandaDoc is email-first; SMS via integrations.
- Adobe Sign is email-first; no native SMS delivery.
- Jotform has SMS notifications; SMS form-link delivery is on add-on tiers.
- Formstack has SMS on higher plans.
- Fillout offers SMS via Twilio integration.
The differentiator isn't whether a platform can send SMS — most can with the right wire-up. It's whether SMS is a first-class delivery channel built into the product, or a feature you bolt on with additional configuration.
Legal status of SMS-delivered signatures
Under ESIGN (US federal), UETA (US state), and eIDAS (EU), the delivery channel doesn't affect signature validity. As long as the signature itself satisfies the legal requirements — consent to electronic signing, intent capture, audit trail, tamper-evident sealing — it's valid regardless of whether the link arrived by email, SMS, QR code, WhatsApp, or any other channel.
The audit trail will record the delivery channel, which provides additional evidence of how the signer received the document.
Common misconceptions
- "SMS signatures are weaker than email signatures." False. The signature carries identical legal weight; only the delivery channel differs.
- "SMS isn't HIPAA-compliant for healthcare consent forms." Nuanced. The SMS message itself shouldn't contain PHI — the body should be a generic link like "Your appointment paperwork is ready: [link]". The signed form on the other side of the link is protected by the same HIPAA controls as any other PHI workflow. With a BAA in place, SMS delivery of the link is fine.
- "SMS only works in the US." False. International SMS is widely supported; per-message costs vary by destination country but the technical delivery works globally.
Related terms
See also