Preferences, Content & Service

Lesson 1

One suppression decision across every send

Subscribers keeps marketing delivery identity, status and preference data separately from Contacts. Manual unsubscribe and the self-service preference page both write the same BU suppression record. The Contact remains stored for service and sales use. Every marketing send checks suppression immediately before delivery, including queued flow activities and refreshed recurring audiences. Resubscription must follow a documented request from the recipient; it clears that BU suppression and adds an audit record.

Lesson 2

Reusable assets and safe HTML

Content stores BU images and saved HTML snippets for approved email designs. A marketing image receives a public asset URL so recipients can load it, so do not upload private customer documents. Check file size, alternative text and how the image behaves when blocked by an email client. A custom HTML block is useful for a small branded component; preview and test the full rendered email after insertion.

Lesson 3

Service commitments are measurable

A Service Case belongs to a customer and can have a company, category, priority, owner, status and activity history. An SLA rule determines the time allowed for a case at a given priority. When the rule applies, the case gets a due time; background processing records a warning or breach in its timeline and notifies the assigned owner. Closing a case records the resolution rather than erasing the history.

Lesson 4

Understand Subscriber history and test sends

A subscriber appears after a real marketing email is sent, including a Send Flow send. A test email validates the design but does not enroll the test address as a subscriber. Older real deliveries may also be added to the Subscriber list when it is opened. Use its status filter to compare subscribed and unsubscribed people. Manual unsubscribe and the public preference page both write a suppression record; a subsequent Send Flow checks it before delivery. Never resubscribe someone without a valid request from that person.

Lesson 5

Present your own preference and mailing details

A BU owner can open Subscribers → Email identity & preferences and set a short preference-page title and introduction, an accent colour and the business’s complete physical mailing address. The recipient-facing page and unsubscribe confirmation reflect that BU, and the address appears in the email footer and on the public mailing-address page. The email preference link comes from a real marketing delivery, so preview it through an address you control rather than copying a token from another person. Search Subscribers by exact or partial Subscriber ID, email or name to verify an assigned coupon or a preference change.

Trial sending is always from contact@supachrome.com with the SupaChrome sender name. A paid BU can configure its displayed sender name and reply-to address; the From address remains the platform domain until its own sending domain is verified and approved. A saved preference page does not grant consent by itself. A manual or self-service unsubscribe updates the same suppression list, and queued messages recheck it before sending.

Lesson 6

Design consent pages and choose defaults

Go to Pages → Preference Center or Unsubscribe Center and open Edit full page. The HTML and CSS editor controls the published visual design. Keep {{ConsentControls}} exactly once: SupaChrome inserts the secure, subscriber-specific form when a person opens their private email link. Public published URLs show a safe sample, so use a real message to an address you control to test the complete interaction. Custom JavaScript and custom form elements are blocked on consent pages.

In Settings → Email → Subscription Management, select the published default pages, create subscription categories and set the default footer and consent rules. Assign a category to each email. A global unsubscribe suppresses all marketing; a category opt-out suppresses only that category. Contact details show the consent timeline, and the delivery service checks suppression again immediately before sending. Public page URLs and opaque private links serve different purposes; never put subscriber addresses or Contact IDs in a URL.

Lesson 7

Add safe, reusable page and email fragments

The preference page title, introduction, accent colour and mailing address are editable under Subscribers → Email identity & preferences. Add optional HTML as a small fragment below the introduction to explain your brand or link to your policy. Leave out html, head and body tags. Scripts, embedded forms and stylesheets are blocked so the subscription button remains usable. The unsubscribe confirmation uses the same page details. Test the recipient link from an email sent to an address you control.

Content stores reusable HTML fragments for email blocks. Save only the inner markup, such as a table, paragraph or button-like link. The editor sanitizes markup on save and the email renderer sanitizes it again at send time. Preview the whole email after inserting a block, since it shares the email layout and must not contain a second document shell.

Lesson 8

Inspect a subscriber and suppression reasons

Click a name or email in Subscribers to open the person’s record. The subscription trail combines manual audit entries and preference changes made through email links. Past communication shows each real email send, its Send Flow, status and recorded events. Test sends are excluded. The record also shows assigned coupons. In an email, campaign or Send Flow analytics panel, open the bounce, unsubscribe and suppressed-send table to see the recipient and the exact provider or preference reason. When the sending provider does not supply an explanation, the table says so rather than guessing. A manual unsubscribe outside an email has no send attribution; find it in the subscriber trail.

Lesson 9

Manage topics and review consent

In Pages → Profile centre, create subscription topics such as Product news or Offers. A recipient gets a secure, personalized preference link in a real email. The recipient can turn each topic on or off, or unsubscribe from all marketing. Tag an email with its topic in Email settings. SupaChrome checks both the global suppression and that topic again just before dispatch, including after a wait in a Send Flow. A global unsubscribe overrides every topic. Open the subscriber record to inspect the consent timeline; archiving a topic removes it from the public choice list without deleting past consent events. Review the purpose and wording of each topic with your team before sending. A person can have a category preference while globally unsubscribed; the global setting still blocks all marketing mail. The timeline helps support staff explain when a choice was recorded and where it came from.

Lesson 10

Manage subscription categories safely

In Pages → Profile centre, create categories that reflect the topics your business sends. Choose Edit to change a category name or description. Archive hides it from new choices while preserving existing contact preferences and consent history; Restore makes it available again. Delete works only when the category is unused, because removing a category with email or consent references would erase important context. Select the right category on each email, then test a subscriber opt-out and inspect the Contact consent timeline. A global unsubscribe takes precedence over every category preference.

Lesson 11

Add starter sections to a page

Open a Landing, Form, Preference Center or Unsubscribe Center page in Pages. Add a heading, text, two-column section or divider from the section toolbar; landing and form pages can also add a hero and call to action. The toolbar inserts editable HTML and CSS into the current draft; the code remains yours to adjust. Preview at desktop, tablet and mobile sizes, save, then publish. Published pages keep the last published snapshot until you publish again. On a Form page, Phone field inserts an HTML input and automatically maps it to Contact phone when Contacts is the destination. For another object, add the destination field in Form destination before publishing. Consent pages keep the managed {{ConsentControls}} block: SupaChrome handles the secure form and the page editor styles its surrounding content.

Lesson 12

Edit visual page sections

Add a section in Pages, then open its card under Visual sections. Change its text, colors and four-side spacing; two-column sections can be expanded and styled up to four columns. Duplicate, move or delete these sections, then preview and publish the saved draft. Existing hand-written HTML, scripts and mapped form inputs remain in the source editor. If you edit a generated section directly in source, continue editing it there so the visual editor does not overwrite your code. Published pages keep their prior snapshot until you publish again.