SendHopper

Getting started

This summary covers the setup order. The full guides include first-SMS and first-email walkthroughs, screenshots, and instructions for each feature.

Browse all documentation
  1. Create your business. Choose its name, public slug and timezone. Invite colleagues with only the permissions they need.
  2. Set up account security. Enable two-factor authentication in Security settings. Provider changes, reminder approvals, consent restoration and exports also require a recent password confirmation.
  3. Add existing clients. Enter details or import CSV/XLSX with unique column headings. Record the service relationship and why the client expects reminders. Review duplicates and shared addresses. Importing never clears an unsubscribe.
  4. Connect and verify providers. SMS supports touchSMS, Twilio and Cellcast. Email supports Brevo, Amazon SES and custom SMTP. Save the provider credentials, then add and select the From address or number approved by your provider. Choose a separate fixed provider for SMS and email.
  5. Prepare a reminder. Choose recipients, the event date, preparation lead time, timezone and repeat pattern. Review the frozen occurrence preview. Approve only the intended recipients and content. Changed providers or schedules need a fresh review.
  6. Follow up in Operations. Accepted means the provider received the submission; it does not prove delivery. Unknown outcomes remain held for review with the original provider. Recording an outcome does not resend a message.

Recipient preferences

A STOP or unsubscribe adds the recipient’s known linked addresses to the Unsubscribed list. Archiving, reimporting or changing providers cannot remove that restriction. Authorized Organization Members can record fresh address-specific consent with evidence; other addresses remain stopped.

Automatic SMS resumption requires a displayed verification code returned from the same phone to a verified two-way number. Automatic email resumption is unavailable. Contact the business directly to record fresh email consent.

Technical restrictions, including provider blocks, bounces and shared-identity review, can remain after consent is restored.

Before sending

New businesses start paused. The operator reviews sender authorization, unsubscribe handling and the pilot budget before enabling sending. Provider outages never switch a fixed route to another account.

Custom SMTP supports password authentication over verified TLS on approved public servers. OAuth and automatic Google Workspace or Microsoft 365 compatibility are not provided. SMTP acceptance cannot establish inbox delivery.

Growth extras are available only when their release controls and paid entitlement are active. The Billing page shows checkout availability and the currently released features.

Continue to SendHopper