Outcome
You can create a complete, saved, responsive campaign, choose the specialized single-property or portfolio workflow, and recognize that CREBuilder does not provide campaign scheduling.
Navigation path
Email Blasts > New email blast or Draft > Composer
Access
Active CREBuilder subscription for new hosted sends; prior drafts and history may remain visible
On this page
Before you start
Data, sources, and access to prepare
- One completed document for single-property mode or at least two for multiple-property mode
- Current property images, metrics, broker profile, and listing links
Choose the composer mode before designing
Short animated UI capture. No audio.
| Mode | Best for | Design behavior |
|---|---|---|
| Single property | One sale, lease, or BOV listing | Four templates, section controls, gallery selection, property metrics, inline content, and optional website CTA |
| Multiple properties | A portfolio or selection of at least two listings | Fixed portfolio hero and property cards, with shared colors, fonts, and eligible property website links |
Hidden controls are intentional
Portfolio mode does not expose the single-property template, section, gallery, or metrics controls. Use the mode that matches the actual message rather than looking for hidden settings.
Build and preview the campaign
Short animated UI capture. No audio.
Short animated UI capture. No audio.
- 1
Confirm source properties and method
Email Blast composer header and Send with area
Verify the selected document or documents and CREBuilder Mail versus Download HTML.
Expected result: The campaign structure and delivery boundary are correct before content work.
If this does not happen: If the wrong source was selected, return to the hub and start the correct draft. Do not disguise it by editing only the title.
- 2
Write the subject
Composer > Subject line
Enter a specific subject of no more than 300 characters.
Expected result: Preview shows a clear, audience-appropriate subject.
If this does not happen: If the subject exceeds the limit or lacks context, shorten it before audience work.
- 3
Write the message
Composer > message controls
Enter the intended introduction or portfolio message.
Expected result: Preview updates with the campaign message.
If this does not happen: Remove unsupported or ambiguous claims before audience work.
- 4
Apply available design controls
Composer > Design
Configure only the controls offered for the current mode.
Expected result: The visual hierarchy supports the message without hiding required facts.
If this does not happen: If a control is absent, check whether the campaign is in portfolio mode.
- 5
Review campaign content
Composer > Preview
Inspect images, metrics, links, broker identity, and footer context.
Expected result: Every visible campaign element is current and relevant.
If this does not happen: Correct the source property or campaign control for the first mismatch.
- 6
Open each responsive preview
Composer > Preview width selector
Switch between Desktop and Mobile.
Expected result: The preview renders at each supported width.
If this does not happen: Reload the composer if a preview mode does not render.
- 7
Read the full preview
Composer > Full preview
Open the full preview.
Expected result: Content, cropping, links, spacing, and footer remain readable at both widths.
If this does not happen: If content is clipped or a link is unavailable, correct the source property or design before proceeding.
Understand autosave, recipients, and delivery
Draft to outcome
Design is autosaved, but recipient files and delivery require separate explicit actions.
Edit campaign
Draft autosaves after about 1.2 seconds
Build and review audience
Hosted preflight and send
Download HTML
No recipients
- Edit campaignDraft autosaves after about 1.2 seconds
- Draft autosaves after about 1.2 secondsBuild and review audience
- Build and review audienceHosted preflight and send
- Draft autosaves after about 1.2 secondsDownload HTML
Important draft boundaries
- A current-property workflow can resume its draft.
- An imported recipient file is never stored with the draft and must be re-imported after reload or later return.
- A matched audience handoff opens context but does not insert or send until the user explicitly reviews and inserts it.
- Download HTML contains design, not a recipient list or a delivery event.
- There is no in-app campaign scheduling control. Send now through hosted Mail or schedule in an external platform after downloading HTML.
Recover design and mode problems
A control described for single property is missing
Likely cause: The campaign is in multiple-property mode, where the portfolio layout is fixed.
- Confirm the selected property count.
- Use portfolio colors, fonts, message, and property cards.
- Start a separate single-property campaign when detailed sections are required.
Recipient file disappeared after returning
Likely cause: Imported files are intentionally not stored with drafts.
- Re-import the original file.
- Review its count and provenance again.
- Do not assume the old audience is still attached.
The requested property website link is unavailable
Likely cause: Listing Hub is disabled, a source property is unpublished, or link status could not be confirmed.
- Read the composer availability label.
- Publish every included property when appropriate.
- Retry status before enabling the CTA.
- Do not paste an unverified public link into campaign content.
You need a scheduled send
Likely cause: CREBuilder Mail does not currently expose campaign scheduling.
- Send now only when ready.
- Or download HTML and use an external campaign platform that supports scheduling.
- Do not promise an in-app scheduled state.
Final verification
- Composer > Design: The visual hierarchy supports the message without hiding required facts.
- Composer > Preview: Every visible campaign element is current and relevant.
- Composer > Preview width selector: The preview renders at each supported width.
- Composer > Full preview: Content, cropping, links, spacing, and footer remain readable at both widths.
- No blocking warning, failed status, or unresolved validation message remains in the completed workflow.