- Enable Send notifications through SMS to send agreement notifications via SMS.
- Enable Send notifications through WhatsApp to send agreement notifications via WhatsApp.
What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
Administer
- Admin Console Overview
- User Management
- Add, edit, and review active users
- Admin Console SSO
- Create function-focused users
- Review users who haven't completed verification
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Edit a user's group membership through the group interface
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
- Group management
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- In Product Messaging and Guidance
- Accessible PDFs
- PDF/A workflows
- Healthcare customer
- New request signature experience
- New custom workflow experience
- New create template experience
- Account Setup / Branding Settings
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Apply Adaptive Signature Draw scaling
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- Enable classic Reporting
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send Settings
- Show Send page after login
- Agreement creation experiences
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- In-person signing config
- Allow in-person signing
- Recipient groups
- CCs
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Remove recipients from in-flight agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Populate form fields with identity-verified data
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Add myself
- Send only to internal recipients
- Download agreement link
- Form field borders
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Restrict access to shared agreements
- Show Send page after login
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- Claim your domain
- Report Abuse links
- System Requirements and Limitations
User profile and configurable features
- Address Book
Send, Sign, and Manage Agreements
- Recipient Options
- Cancel an email reminder
- Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Restart the agreement
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
- Send (Compose) page
- Overview of landmarks and features
- Group selector
- Adding files and templates
- Agreement name
- Global Message
- Completion Deadline
- Reminders
- Password protect the PDF
- Signature type
- Locale for the recipient
- Recipient signature order/flow
- Recipient roles
- Recipient authentication
- Private message for the recipient
- Recipient agreement access
- CC'd parties
- Identity check
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Compose in-person agreement
- Recipient signing order
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Automatic field detection
- Drag and drop fields using the authoring environment
- Assign form fields to recipients
- The Prefill role
- Apply fields with a reusable field template
- Transfer fields to a new library template
- Updated authoring environment when sending agreements
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Field types
- Common field types
- E-signature fields
- Initials field
- Recipient name field
- Recipient email field
- Date of signing field
- Text field
- Date field
- Number field
- Checkbox
- Checkbox group
- Radio button
- Drop-down menu
- Link overlay
- Payment field
- Attachments
- Participation stamp
- Transaction number
- Image
- Company
- Title
- Stamp
- Field content appearance
- Field validations
- Masked fields values
- Setting show/hide conditions
- Calculated fields
- Verified forms
- Field types
- Authoring FAQ
- In-app authoring environment
- Sign Agreements
- Manage Agreements
- Manage page overview
- Copy an Agreement
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Bulk actions
- Hide multiple agreements
- Digitally sign multiple agreements
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Manage Shared Templates
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- Integration keys
Acrobat Sign Developer
- REST APIs
- Webhooks
- Sandbox
Support and Troubleshooting
Deliver agreement notifications using SMS or WhatsApp to reach recipients outside of email.
Adobe Acrobat Sign allows senders to notify recipients through SMS or WhatsApp in addition to email. This helps ensure recipients receive and act on agreements, even when email delivery is delayed, filtered, or ignored.
Using SMS or WhatsApp notifications can improve delivery rates and reduce delays in time-sensitive workflows by reaching recipients on devices they actively monitor.
Before you begin
- SMS and WhatsApp message transactions must be purchased and available to send messages prior to being enabled by an administrator.
- Sending notifications through SMS or WhatsApp consumes phone transactions from your account.
- Recipients must have a valid phone number capable of receiving messages.
Agreement Delivery via SMS is currently not supported for recipients with Thai (+66) phone numbers due to local regulatory requirements.
Configuration
Availability
- Acrobat Sign Solutions: Supported.
- Acrobat Sign for Government: Supported.
- Acrobat Standard and Acrobat Pro: Not supported.
Configuration scope
- This setting can be configured at the account and group levels.
- Group-level settings override account-level settings.
Default value
- Disabled.
Impact on in-flight agreements
- Changes to notification settings apply only to agreements sent after the setting is updated.
- When the transaction pool is depleted, mobile link delivery and phone authentication will be paused until more credits are available.
To access this setting
- Navigate to Send Settings > Send Agreement Notifications through
Enable SMS or WhatsApp notifications
These options control whether senders can use SMS or WhatsApp as notification channels when sending agreements.
-
-
Configure a default country code to ensure the Compose page is best formatted for SMS and WhatsApp delivery.
-
Save the configuration.
As soon as the option is enabled, all sender's will have the option available in their Compose experience.
Transaction usage and limits
- Each recipient consumes phone transactions when SMS or WhatsApp notifications are used.
- A single transaction bundle through WhatsApp typically includes:
- One initial "Please sign" message.
- One reminder message.
- One completion or delegation message.
- Additional reminders consume additional transactions:
- Each additional reminder consumes another transaction.
- Only one message is sent per reminder event. Recurring schedules (for example, daily or weekly) are not followed.
- SMS or WhatsApp delivery and phone authentication draw from the same transaction pool.
- Transactions are consumed when messages are sent, not when they are delivered or completed.
- If the transaction pool is depleted:
- SMS or WhatsApp delivery is paused.
- Phone authentication is paused.
- Email delivery continues unaffected.
Delivery behavior
- The system attempts to deliver messages through the selected channel using the available messaging infrastructure.
- Delivery depends on carrier availability, regional support, and recipient device capabilities.
- In rare cases, delivery confirmation from the messaging provider may be delayed or not received.
A reliability safeguard ensures recipients receive at least one SMS rather than none in cases where APO retains messages in the SENT status indefinitely. A known side effect is that duplicate messages may occur when the original message was delivered but APO did not confirm delivery within 5 hours.
- Notification activity is recorded in the agreement’s audit report and activity log. These records reflect when notifications are sent and can be used to verify delivery attempts.
Monitor transaction usage
Administrators can monitor phone-based transaction usage:
- You can monitor SMS usage and transaction consumption using the SMS Consumption report in Adobe Acrobat Sign.
- Go to Send Settings > Send Agreement Notifications through
- Hover over the Track Usage link.
The tooltip shows usage for:
- SMS or WhatsApp delivery usage.
- Phone authentication usage.
Once the transaction pool is depleted, mobile link delivery and phone authentication will be paused until more credits are available.
What shows on the sender's Manage page
- If email delivery is used, the recipient’s name or email appears normally.
- If using SMS or WhatsApp notifications only:
- The recipient appears as a partially masked phone number (for example, XXXXXX1212@sms.adobesign.com).
- The full phone number is shown only in recipient settings, such as when editing authentication.
- Agreements sent only by SMS or WhatsApp do not appear on the recipient’s Manage page if they have an Acrobat Sign account.
When viewing individual recipient records (for example, when replacing the recipient or editing the authentication type), the phone number is presented unmasked.
When viewing the individual recipient records (when replacing the recipient or editing the authentication type), the phone number is presented unmasked:
Audit Report and Activity log
SMS/WhatsApp delivery is clearly recorded in:
- The Audit Report.
- The Activity log.
Only the last four digits of the phone number appear for privacy
How senders use SMS or WhatsApp notifications
When enabled:
- Senders can include a recipient’s phone number when preparing an agreement.
- Acrobat Sign sends a notification message to the recipient through the selected channel.
- The recipient receives a message containing a secure link to access the agreement.
Notifications are delivered in addition to standard email messages.
Recipient experience
- Recipients receive a message through SMS or WhatsApp with a link to the agreement.
- Selecting the link opens the agreement in a browser for review and signing.
- If multiple reminders are triggered, additional messages may be sent based on reminder settings.
Things to know
- Delivery success may vary by region and carrier.
- Duplicate messages may occur under certain delivery conditions.
- Recipients must be able to receive messages on the provided phone number.
- SMS and WhatsApp notifications are supplemental to email delivery and do not replace email notifications.
- SMS and WhatsApp delivery does not support delegation. If a recipient delegates an agreement, the new recipient receives notifications only by email, even if SMS or WhatsApp was enabled for the original recipient.
- WhatsApp delivery does not include private messages in either the Please Sign notification or any Reminder notifications.