Appmint Business Email and Customer Campaigns: Mailboxes, Segments, Offers and Broadcasts

Review status: Illustrated draft preparation is supported by the retained application captures below, inspected again against current source on 4 October 2026. Actual email/SMS delivery, recurrence, recipient tracking and suppression enforcement still require controlled live verification. No fresh send was performed for this revision.

Broadcast assembles four decisions into one campaign: which account sends, who receives, what the message says, and when it runs. You can prepare and save a draft before the sender is connected. Sending requires a usable account and a reviewed audience; a draft count is not a delivery count.

The screenshots follow a consultation invitation saved as a draft, then a separately named reminder. Their example addresses use .invalid and cannot be used to test delivery. For a real delivery rehearsal, replace the entire audience with addresses you control and verify their received messages separately.

Find your place in Broadcast

Open CRM → Broadcast. The Dashboard summarizes channel setup and recent activity; Broadcasts contains individual campaigns; Channels takes you to sender configuration; Analytics concerns reporting. Current source also exposes Unsubscribes; that tab is absent from the older dashboard capture and its newer interface still needs a fresh screenshot.

Read the channel state before creating a send. Not configured is a setup condition. It is not the same as a configured sender that failed to deliver. The first example deliberately remains a draft because no sending account was configured.

01. Navigate Broadcast and choose a channel

What this does

Broadcast combines the sender, audience, message and timing in one saved campaign. The report then shows what happened per recipient. We will prepare a controlled send before scaling to an audience.

Steps

1. Select Create Broadcast in the upper-right corner.
2. The drawer has four tabs: Sending Accounts, Recipients, Message, and Settings & Send. Work through them in that order, returning to a tab when its value needs correcting.
3. In Sending Accounts, select Email. The area below changes to Select Email Accounts. SMS instead requires the relevant phone sender.
4. Read any setup message below the channel. No email accounts configured means there is no account to select; continuing to write the draft does not resolve it.

Check the result and avoid these mistakes

This is a documented script. Sending and provider results need independent rehearsal. WhatsApp is explicitly Coming Soon in the current channel screen, even though a channel choice appears in the creator.

02. Choose the sender and rotation

What this does

Selected accounts are the addresses the campaign may send from. Rotation is useful with multiple configured senders; it does not repair an inactive or unverified account.

Steps

1. If accounts are listed, select the email account intended to appear as the sender. Do not choose an unrelated account just to clear validation.
2. If the list is empty, finish any text you want to preserve and use Save Draft. Close the drawer, open Channels → Email, and follow the Email Accounts setup entry. Return to Broadcasts, reopen the draft and select the configured account.
3. When using multiple accounts, choose Rotation Strategy: Healthiest First, Round Robin, Least Used or Random. Rotation chooses among selected accounts; it does not authenticate them or guarantee inbox placement.
4. Save and reopen the draft. Verify the selected accounts and rotation rather than relying only on the dashboard’s Active Channels count.

For SMS, choose the configured business phone sender and verify its readiness in the Phone module. A phone number listed in the UI is not proof that the required messaging registration or provider permissions are complete.

Check the result and avoid these mistakes

Email load failure and an empty account list are different states. Use the retry for a failed load. SMS requires a usable configured number and the applicable registration readiness; no SMS delivery has been performed.

03. Build and verify the audience

What this does

Recipient selection is the most important send boundary. Manual Entry is useful for an initial controlled test. Lists and CSV expand that audience only after their actual addresses are checked.

Steps

1. Open Recipients → Manual Entry.
2. Enter one address per line, or separate addresses with commas or semicolons. For the draft-only exercise use:

[email protected]
[email protected]
[email protected]

3. Read Total Recipients beneath the entry box. The captured exercise contains three entries and shows three. This checks the prepared list, not whether those mailboxes exist.
4. Read each address yourself before saving. Current manual-entry counting splits non-empty text at separators; a numeric count and the older “valid emails” wording are not independent address verification.
5. If you want to reuse this audience, select Save as contact list, give the list an identifiable name and save it. On a later draft, choose Email Lists, select the saved list and check that Total Recipients updates. A list merely appearing among the choices does not mean it is selected.

CSV alternative: choose Upload CSV, select your file and inspect its parsed address count. The current importer extracts addresses from the file, including additional columns, lowercases them and removes duplicates. It does not require an address-only first column. Export only the intended audience: a second email column can also be picked up. An empty result shows No email addresses were found in that file; an unreadable file has a different error.

List alternative: the UI offers groups, contacts and leads. List sizes are preparation figures; overlapping lists, missing recipient addresses and provider suppression require their own final delivery checks. Filter Contacts is another selection path in the creator and still needs a complete recorded walkthrough before this course can claim full coverage.

Check the result and avoid these mistakes

CSV is parsed into addresses by the current source; picking a filename alone is not the check. Audience/variable behavior across different list types still requires runtime verification. Do not imply a consent record is created merely by selecting an address.

04. Write the message and personalize it

What this does

The message editor combines formatted content, variables and attachments. A variable must resolve for the selected recipient data; its appearance in the editor is not proof of a correct personalized message.

Steps

1. Open Message. Set Broadcast Name to Tutorial Consultation slots — October. This is the name you will find in the campaign list; it is separate from the email subject your recipient sees.
2. Set Email Subject to Plan your room with a free 30-minute consultation. Choose the applicable Category, shown as Promotional in this example.
3. Enter the body in Message Content. The exercise invites a reply with a preferred weekday; it does not claim a booking was automatically created. Use a message and destination link that match your real offer.
4. Select Show Template Variables to open the field panel. Insert the required variable where its resolved value belongs, then review surrounding punctuation and spacing. A token shown in the editor is not proof that every audience record supplies that value.
5. For an attachment, scroll to Attachments → Choose Files, select the intended file and check its displayed name. Remove an incorrect file with its remove control before saving.
6. Choose Save Draft, close the drawer and reopen the same campaign in Broadcasts. Recheck the name, subject, body, audience and sender selection. This is the useful checkpoint before choosing a send time.

The Broadcast AI panel can assist with preparation. After accepting a change, inspect all four tabs: changing prose must not accidentally change the audience or sender. The retained screenshots show the panel, not a verified AI-generated campaign.

Check the result and avoid these mistakes

The current visible editor provides rich text and variables; do not invent a direct template picker or dedicated Test send button where none is exposed. Use a separate controlled-recipient draft for the first actual send.

05. Send now, schedule or repeat

What this does

Immediate send, scheduled send and repeat are different timing choices. Review the final summary before launching the saved campaign. The first test goes only to the controlled recipient.

Steps

1. Open Settings & Send. Read Broadcast Summary: name, channel, subject, recipient count and sender-account count must match the campaign you prepared.
2. For draft-only practice, use Save as Draft. In the captured example Sender Accounts: 0 selected is a reason to return to sender setup, not a ready-to-send result.
3. For a real controlled send, first select your usable sender and replace the practice audience with the recipient you control. Choose Send Immediately, review the summary again and select Send Now once. Wait for the result; do not create another campaign merely because the request is slow.
4. For later delivery, use a separate draft and select Schedule for Later. Set the intended date/time, review the final summary and select Schedule Broadcast. Check its stored schedule and timezone after reopening.
5. For recurrence, configure the displayed Repeat settings on the intended draft and inspect the saved timing. A recurring schedule must also be checked for its next run and its stop/cancellation behavior; those provider-backed executions remain pending in this course.

The send handler checks for name, at least one sending account, recipients, message content and an email subject. Correct the named missing input on its tab, then review again. Passing these checks still does not prove provider acceptance or recipient delivery.

Check the result and avoid these mistakes

Queue and provider execution are not yet observed. Verify the stored/actual scheduled timestamp against the expected timezone during rehearsal. Do not describe a scheduled record as a delivered message.

06. Read recipient results and cancel pending work

What this does

The campaign’s aggregate figures are useful, but the recipient timeline explains individual delivery. Sent, Delivered, Opened and Clicked are different events. Cancelling pending work does not recall messages already delivered.

Steps

Use the broadcast name to find the same record in Broadcasts. The retained example below shows two distinct saved drafts, each with three recipients, and Messages Sent: 0. Six total prepared recipients across two drafts does not mean six messages were sent.

For a campaign that actually ran, choose View report on that record. Open Delivery log and inspect the controlled recipient’s timeline. Open Activity for provider events and use Refresh. Compare the received inbox message with its subject and sender. For a pending or sending disposable campaign, use Cancel and reread its state. Use Duplicate to prepare a separate revised campaign only after reviewing the new audience.

Check the result and avoid these mistakes

Current reviewed report exposes Cancel for pending/scheduled/sending work. Pause and Resume are catalogue obligations without a confirmed visible control in this source pass; record this as a gap, not a demonstrated feature.

07. Unsubscribes, analytics and recovery

What this does

Suppression and failure details explain why some recipients should not receive another campaign. Provider event data supports the report; absence of events is not proof that nobody opened or received mail.

Steps

Open Unsubscribes and inspect the relevant address and channel. Return to the campaign’s Delivery log and compare failed, bounced or unsubscribed outcomes. Use Analytics for the broader result, then repair the specific sender, address or content issue before preparing a controlled retry.

Check the result and avoid these mistakes

Suppression enforcement, open/click collection and repeats require actual provider tests. Confirm delivery and recipient consent through the configured provider.

Before you use this for a real audience

The saved settings establish the configuration. The independent recipient, visitor or consuming operation establishes whether it worked. Return to the relevant chapter whenever you change a sender, audience, template or connected site, and repeat the result check for that change.

Limitations and checks

Primary UI rechecked on 4 October 2026 against retained September captures. The eight embedded screenshots were visually inspected for what each actually proves; they are not presented as newly recorded actions. This pass performed no live external send, DNS change, agreement acceptance, provider setup, generated audio or rendered video. Statements about expected results are recording requirements, not claims of completed tests.

Review status: Account setup and assignment are illustrated with inspected earlier Appmint captures. No agreement, DNS change or external send was performed for this revision.

Email Accounts manages the addresses your organization uses, their hosting provider, their assignment to people or AI employees, and whether they participate in Broadcast sending. These settings answer different questions: Does the address exist? Who may use it? Can it send campaigns? Does mail actually arrive? Saving one setting does not answer all four.

Concept illustration, not the Appmint interface. The two sides explain different jobs, not a claim that replying to a message launches a campaign. Configuration, assignment and delivery each need their own check.

The captured product-guide.example domain is a fictional setup example. It demonstrates form choices and an inactive assigned record; it cannot establish public DNS ownership, mailbox hosting or delivery. Use a domain your organization controls for the hosting and DNS steps.

01. Choose the email service

What this does

Email Accounts separates everyday hosted mailboxes from bulk sending identities. SpinForge Mail provides mailboxes people open in webmail. AWS SES is the bulk-sending route. A verified sender does not automatically create an inbox.

Steps

1. Open Email Accounts from your configuration/navigation entry. Read the four summary figures: Accounts, Active, Bulk senders, and On SpinForge Mail. An account can exist while the other counts remain zero.
2. In Domains, select the plus/add-domain action. Enter the domain name itself in Domain name, not an email address or a website path.
3. Under Email provider, choose SpinForge Mail for hosted mailboxes or AWS SES for bulk sending. The form initially selects AWS SES; explicitly choose SpinForge Mail if you intend to host an inbox.
4. Select Add Domain, then select the saved domain on the left and open Email setup. This is where that domain's provider setup continues.

The screenshot has AWS SES selected and a fictional domain. It is a provider-choice illustration, not evidence that SpinForge was activated.

Check the result and avoid these mistakes

Use a domain your organization controls. A fictional example domain can illustrate the form but cannot establish DNS ownership. Use the Email Accounts management screen described here.

02. Set up hosted email and prove domain ownership

What this does

Hosted email setup starts with the service agreement, then a TXT ownership challenge. Ownership verification comes before the mail routing records. Use the values generated for this domain rather than copying another organization’s example.

Steps

Read the displayed SpinForge Mail agreement. An authorized organization representative accepts it using the checkbox and Accept agreement, then selects Set up email. In Prove you own the domain, copy the shown TXT Name / Host and Value. Publish that exact record in the domain’s DNS host. Return and select Verify. If verification remains pending, compare the returned name and value before retrying.

Check the result and avoid these mistakes

This course has not verified domain activation live. After publishing the records, check the actual domain state in Appmint; entering records at the DNS host is not yet proof that Appmint resolves them.

03. Publish and check the mail records

What this does

Once ownership is verified, the panel supplies the records that make mail work. Receive and Send readiness are independent indicators. The active domain badge alone is not the same as verified delivery.

Steps

Open DNS records. Copy each supplied MX, SPF, DKIM and DMARC record with its type, Name / Host, Value and any priority into the intended DNS zone. Return to Appmint and select Check DNS. Inspect Receive and Send separately and read any record-specific status. Correct the mismatching entry and Check DNS again.

Check the result and avoid these mistakes

DNS hosts differ in whether they append the domain to a short Name / Host. Compare the stored full record name with the one Appmint supplies to avoid repeating the domain suffix. Review the existing records before changing the domain’s mail routing.

04. Create a mailbox and use webmail

What this does

The mailbox is the address and sign-in people use. Domain verification prepares the service; creating the mailbox prepares the person’s inbox.

Steps

In New mailbox, enter the local part in Address, a Display name and a new Password. Select Create mailbox. Confirm it appears in Mailboxes, then choose Open webmail and sign in with that address. Send a message to a controlled second inbox. Reply from that inbox and confirm the reply reaches webmail.

Check the result and avoid these mistakes

External send/receive remains unverified. A Created notice or webmail login cannot stand in for the two delivery observations.

05. Assign the account and maintain its identity

What this does

Assignment controls who can use an email account inside Appmint. From Name and Signature control how written mail is presented. These settings are separate from a mailbox password.

Steps

1. Return to Email Accounts and select the address's domain. Use Search by address or name to locate the exact record. If it is missing, clear Hosted by, Bulk sending and Assigned filters before creating a duplicate.
2. Open the account editor. Account Name identifies it to your team; From Name is the name recipients see; Signature is appended to mail written from it. Set these deliberately, then save and reopen.
3. Open the row's actions menu and choose Assign to people or AI.
4. In the assignment drawer, use Users to select named identities or Groups for a group assignment. Search for the intended person or AI employee, select their checkbox and read the selected count.
5. Choose Save Assignments. Return to the row and check Assigned to, then reopen the assignment drawer to verify the selection remained.
6. Finally, test account availability in the assigned identity's own context. An owner selecting someone in this drawer does not establish every user permission or email-listener behavior.

This example deliberately keeps the account Off. The Assignment updated notice and badge prove the assignment operation, not a working inbox. AI Employees must also be configured to use the relevant channel; see the AI Employees + Assistant course.

Check the result and avoid these mistakes

An AI employee assignment does not prove its listening configuration or delivery. Keep that check in AI Employees → Config and Profile. Verify permissions with the actual account.

06. Configure bulk sending through AWS SES

What this does

Bulk sending uses a sending identity and gateway. The account’s health, daily limit and priority affect its participation in rotation. Hosted SpinForge mailboxes intentionally do not expose bulk sending.

Steps

1. Select the domain configured for AWS SES and open Email setup. Follow its actual verification state and generated DNS records; the warning banner identifies domains still needing DNS setup.
2. Open the intended sending account and expand Bulk sending.
3. Enable Use for bulk sends (included in sender rotation) only for an account meant to send campaigns. A team member's ordinary mailbox is not automatically a campaign sender.
4. Select Sending Gateway, or inspect the explanation when no gateway is configured and the system default will be used. That fallback must still be usable; the label does not prove it can send.
5. Review Health, Daily Limit and Priority. The captured example shows Active health,500 and5, but these are example values, not recommended limits for every account. Priority controls order among eligible senders; the account's separate Active checkbox controls whether it is switched on.
6. Configure Warm up and its plan only when appropriate to the sender. Review Settings → Active and Primary separately, then save.
7. Return to Broadcast → Create Broadcast → Sending Accounts → Email. Confirm that the intended account is available and selected, then perform the controlled delivery check in the Broadcast course.

In this captured draft, Use for bulk sends and Active are unchecked. It must not be presented as a ready sender. The DNS warning also remains unresolved.

Check the result and avoid these mistakes

Actual SES provisioning and delivery remain unverified in this course. Selecting System default does not establish that a usable system gateway exists. Confirm the gateway and sender before the controlled send.

07. Bulk address creation, password recovery and removal

What this does

Bulk Generate Sending Addresses creates sending identities. It does not create multiple hosted inboxes. Hosted mailbox passwords and deletion are managed from the domain’s email panel.

Steps

Open Bulk Generate Sending Addresses. Choose Domain, Prefix, Count and Number Position, inspect the proposed addresses and complete the authorized generation. For a hosted mailbox password reset, use Account actions → domain mailbox management, select the mailbox’s reset control, enter the new password and save. Sign in again with the new password to check the change. Remove only a disposable mailbox; the domain panel requires its mailboxes to be deleted before removing email hosting.

Check the result and avoid these mistakes

A password reset changes the mailbox sign-in; coordinate it with the person who uses that account. Removing domain email deletes signing keys and stops mail. Read the confirmation and keep any needed messages before removing a mailbox or its hosting.

Your final checks

The saved settings establish the configuration. The independent recipient, visitor or consuming operation establishes whether it worked. Return to the relevant chapter whenever you change a sender, audience, template or connected site, and repeat the result check for that change.

Limitations and checks

Primary UI rechecked on 4 October 2026; four retained application screenshots were inspected individually and embedded beside matching procedures. This pass performed no live external send, DNS change, agreement acceptance, provider setup, generated audio or rendered video. Expected results describe checks still to perform; they are not claims of completed tests.