← Back to Control
Compliance + recipient approval

Permission-based communication, without buried consent language.

SendForge is moving away from the old opt-in form model. Recipient approval happens inside a lightweight client-facing SendForge experience, where people choose which businesses can contact them and which channels are allowed — text, email, or both — then update or revoke that any time.

Public explanation

We frame approval around deliberate user action and sender-specific permissions. The contact decides who can reach them, by channel, inside their own controlled experience.

Recipient-controlled

Approval is granted directly by the recipient inside their own SendForge-facing experience, not inferred from a hidden checkbox.

📨

Channel-specific

Users can allow text, email, or both, and those approvals stay tied to the specific sender relationship.

🧾

Recorded + reviewable

Permission changes are structured, logged, and easy to review later for internal governance and external standards.

Approval surfaces

Use the right recipient flow for the right context.

These pages represent the kind of client-facing approval surface a business can direct people into. Each one uses sender-specific language, clear channel choices, and practical copy that maps to real communication use cases.

Team communication

For staff, crews, and internal coordination.

Open page

Customer support

For follow-ups, case updates, and service conversations.

Open page

Appointment reminders

For clinics, service providers, and scheduled visits.

Open page

Service updates

For repair progress, field service, and account change notifications.

Open page

Account notifications

For login alerts, account actions, and important changes.

Open page

Marketing promotions

For promotions where the recipient has deliberately enabled them for that sender.

Open page