# Companion-video guide — Build a consultation campaign

**Manuscript:** [Build a consultation campaign you can check before sending](../appmint-run-a-customer-campaign.md). **Product:** Appmint Studio Manager. **Available:** actual application stills and a capture ledger. No campaign-send recording, delivered-message footage or completed referral lifecycle is available.

## What this video teaches

An owner writes one useful invitation, checks the audience and saves two independently editable drafts. The main result is the reopened record, not an animated “email sent” graphic. The optional referral chapter ends with a saved draft program, not a partner earning money.

Jordan Morgan runs Cedar & Form. Maya, Daniel and Priya are prospective customers. Keep these roles consistent with the CRM and website courses.

## Assets

Use the stills under [assets/appmint-campaign](../assets/appmint-campaign). The [evidence ledger](../assets/appmint-campaign/evidence.json) records route, timestamp, visible text and callouts. All UI images came from the running local application.

| File | Meaning and editorial use |
| --- | --- |
| `01-broadcast-dashboard.png` | Four main tabs and initially empty dashboard |
| `02-sending-accounts-empty.png` | Actual missing-sender notice |
| `03-recipient-count-mismatch.png` | Three syntax-valid entries versus four total entries, including duplicate/invalid input |
| `04-three-draft-addresses.png` | Restored three-address practice list |
| `05-message-details.png` | Name, customer-facing subject and Promotional category |
| `06-message-copy.png` | Reopened original body, scrolled into view with AI bar collapsed |
| `07-review-before-save.png` | Settings & Send summary; zero selected sender accounts |
| `08-draft-saved-list.png` | Original name missing after first save |
| `09-save-contact-list-form.png` | Shortcut offering to save the three addresses |
| `10-list-saved-zero.png` | Actual zero-contact result |
| `11-duplicated-draft.png` | Two drafts, generated duplicate title |
| `12-copy-subject-persisted.png` | Reopened reminder subject and Newsletter category |
| `13-empty-contact-group.png` | Group exists with zero members |
| `14-channels.png` | Channel configuration overview |
| `15-analytics-placeholder.png` | Analytics coming-soon screen |
| `16-affiliate-program-form.png` | New program form and its sections |
| `17-affiliate-hold.png` | Fourteen-day hold; Auto Credit No |
| `18-affiliate-percentage.png` | Ten-percent commission |
| `19-program-list-after-save.png` | Saved draft program card; use22 for stronger readback |
| `20-ad-campaign-builder.png` | Six-stage advertising planning interface |
| `21-two-named-drafts.png` | Final hero: both names persist, no messages sent |
| `22-affiliate-program-readback.png` | Saved program's commission, attribution and payout settings |

The early body screenshot was replaced with a properly scrolled capture. Use the current `06` file. Do not crop it so tightly that “Untitled Broadcast” appears to be a second campaign: it is the original before the name-recovery update.

## Recording sequence and narration

### 0:00–0:35 — Show the useful result

Start on21. Point to the two names, draft statuses and zero messages sent.

**Narration:** “We are preparing a small consultation offer. By the end, we'll have an invitation and a separate reminder, both saved and checked. We'll also catch two problems that are easy to miss if we trust the totals without reopening the records.”

Do not open with a generic montage of email or unrelated product footage. The viewer should immediately recognise the actual screen they are about to use.

### 0:35–1:40 — Find the right controls

Use01 and02. Show CRM → Broadcast and the four main tabs. Open Create Broadcast and name its four creator tabs.

**Narration:** “Sending Accounts answers who sends. Recipients answers who receives. Message holds the offer. Settings & Send is the final review. We have no sender configured here, so we'll save a draft while we work through the message.”

If filming fresh footage, use the sidebar rather than typing a localhost address. Local development URLs must not become learner instructions. The unrelated Google agreement banner visible in some captures came from another feature; it is not an email-setup step. Do not zoom in on it or accept it during recording.

### 1:40–3:20 — Enter and challenge the audience

Show04 with three addresses. Explain that `.invalid` is practice text and must be replaced before an actual controlled send. Then show03.

**Narration:** “Here is the trap. Four lines include a duplicate and an invalid address. The small label says three valid emails; the green panel says four recipients. Neither gives us a clean unique list. We remove the bad line and duplicate before continuing.”

Use a simple labelled diagram if helpful: four input lines → two unique syntactically valid addresses. Label it “Counting example,” not a server-delivery result. Do not animate four people receiving mail.

Return to04 so viewers see the corrected state before the next chapter.

### 3:20–5:20 — Write a message with one action

Show05, then06. Distinguish internal name from inbox subject. Read the body naturally; avoid reading every toolbar button.

**Narration:** “The offer tells the reader what they'll get, how long it takes and what to bring. The action is to reply with a preferred time. Jordan confirms availability afterward, so a reply is not mistaken for a booking.”

Highlight “Hi there” and explain the missing-name issue. Do not show first-name input fields: Manual Entry has none. Do not substitute an invented booking website. A future booking-link edition needs a real public page and a tested reservation result.

Pause long enough to read the entire message. Collapse the AI bar when recording the lower editor. The rich-text vendor's Upgrade control is visible in the toolbar; it is not an Appmint payment prerequisite and needs no tutorial callout.

### 5:20–7:20 — Save, reopen and repair the name

Use07 and08. Show Save as Draft, close, Refresh and reopening. The initial missing name is part of the actual sequence.

**Narration:** “The subject and body saved, but this first save lost the internal name. We open the existing row, confirm its content, type the name again and save. Now Refresh shows the correct name. Creating a second record would only give us more confusion.”

For a new recording, show the before/after update without cutting away the readback. If a later build fixes initial naming, record that behaviour and remove the obsolete workaround from the main flow; keep the dated evidence in research.

### 7:20–9:00 — Make a separate reminder

Show the Duplicate tooltip,11,12 and21. Open the original and copy to compare subjects. Explain that the Newsletter category change demonstrates independent persistence; the real message category should match its purpose.

**Narration:** “The reminder has its own subject and category. The original remains unchanged. Six total recipients here means three on each draft, not six different people and not six deliveries.”

Do not present a duplicated draft as a completed send or edit a past sent message to imply recipients receive an update automatically.

### 9:00–10:20 — Inspect the contact-list shortcut

Use09,10 and13. Keep the “0” visible and readable.

**Narration:** “The shortcut created an empty group. The notice says zero contacts, and reopening confirms zero members. We keep the addresses in Manual Entry for this exercise.”

This is troubleshooting, not a required happy-path action. Do not instruct every viewer to create empty groups. Keep implementation details brief; put customer-API explanation in a developer note if needed.

### 10:20–11:40 — Explain the real sending handoff

Use14,07 and15. Explain missing sender configuration, replacing practice addresses, checking monitored replies and inspecting the actual inbox after a controlled test.

There is no captured Summary tab because both records are drafts. Do not build a fake Summary with Delivered3. No provider configuration, inbox delivery, reply receipt, attachment delivery or tracking webhook was tested. Keep the manuscript's provider-dependent acceptance checks visible as a separate chapter card, not fabricated app footage.

Explain that the current scheduled-broadcast pickup path is incomplete and that Send Now is an activating action. Do not click it during a reshoot of this draft exercise.

### Optional 11:40–15:00 — Referral-program preparation

Use16–18 and22. Enter the program identity, keep Draft, use10% and14days, then Auto Credit No. Reopen Program Details and point to the persisted settings.

**Narration:** “The program describes the conditions for referral credit. It hasn't enrolled a partner, attributed an order or paid anyone. Our fourteen-day hold and disabled automatic credit give us a program draft to review before activation.”

No ADA10 link or5.40 affiliate payout was generated in this course. Do not reuse the Finance adjustment screenshot as referral earnings. That transaction was explicitly a ledger exercise.

### Optional 15:00–16:00 — Advertising planning

Use20. Briefly show the six stages. Explain that demographic ad audiences differ from CRM email recipients. The inspected launch path simulates a launch and saves internal state. Do not overlay external ad-platform success or claim money was spent.

## Required footage for a later delivery edition

A producer continuing this course needs a controlled sender, controlled inboxes and authorisation for the test messages. Record sender setup, account selection, the final saved audience, activation, actual provider result, delivered content and a real reply. Use the same campaign ID throughout. Confirm report rows and metrics on that deployed build before teaching them.

A referral delivery edition additionally needs a test partner, generated referral link, qualifying order, hold behaviour and matched wallet record. A wallet balance alone does not establish that lifecycle. Do not activate this practice program or release commissions just to fill a missing scene.

## Review before publication

Check that every screenshot is attached to the correct state: count trap versus cleaned list; original versus copy; draft versus active program. Retain the zero-contact outcome and first-save name recovery where they still apply. Keep private credentials, provider keys and real recipient lists out of footage. Export subtitles from the actual narration; do not describe actions the recording never shows.