Outcome
The campaign is submitted exactly once with valid content, a permitted audience, current Mail gates, and a correctly interpreted immediate result.
Navigation path
Email Blasts > Composer > CREBuilder Mail > Send
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
- A complete campaign design
- A consent-reviewed unique audience of 1 to 500
- Mail settings ready and enough displayed allowance
Confirm every authoritative gate
Short animated UI capture. No audio.
| Gate | What must be true |
|---|---|
| Subscription and schema | The account can make a new hosted send and the required Mail schema is current. |
| Subject and content | Subject is present and no more than 300 characters; links, images, source facts, and responsive preview were reviewed. |
| Audience | At least one and no more than 500 strict-valid unique addresses remain after authoritative suppression. |
| Mail access | Access is approved, current terms are accepted, and the company is not suspended. |
| Compliance address | Street, city, state, and ZIP/postal code are complete. |
| Platform and sender | Hosted transport is available and the effective shared or verified sender resolves. |
| Allowance | Displayed daily, monthly, and any ramp-adjusted capacity covers the effective audience. |
| Review | The audience and account review policy is accepted, including any hold before transport. |
The server checks again
Client feedback helps correction, but the send boundary revalidates identity, recipients, suppression, access, terms, address, quota, sender, platform capacity, and review policy.
Understand review and allowance behavior
| Audience or account state | Review behavior | Allowance behavior |
|---|---|---|
| New approved CRM sender | The first clean CRM campaigns normally enter human review; use the displayed remaining review runway as authoritative. | Uses current displayed account limits. |
| Uploaded-classified audience | Every campaign is held for human review. | Uses half the displayed allowance. |
| Always-review account mode | Every campaign is held regardless of audience source. | Uses displayed account and ramp limits. |
| Verified new domain | Review policy still applies. | Daily capacity can start below the nominal cap and increase over the first weeks. |
| Platform capacity paused | Submission cannot proceed to transport. | Wait for the displayed recovery rather than retrying around the pause. |
What the screen should tell you
- Daily and monthly caps and remaining capacity
- Any lower ramp ceiling
- How many upcoming clean campaigns remain in review
- Whether the audience is treated as Uploaded
- Whether Mail is suspended, platform-paused, or unavailable
- Whether a held campaign is waiting for a human decision
Displayed limits are authoritative
Account overrides, warm-up, recipient provenance, and current platform capacity can change the usable amount. Do not rely on a hard-coded allowance from an older guide.
Submit once and interpret the immediate result
- 1
Run the final content preview
Composer > Desktop, Mobile, and full preview
Read subject, message, every property, image, metric, link, broker identity, signature expectation, and footer context.
Expected result: The final rendered message is accurate at desktop and mobile widths.
If this does not happen: Correct the draft and wait for autosave before continuing.
- 2
Run the final audience review
Composer > Recipients summary
Confirm source classification, unique count, invalid count, suppression expectations, consent, review path, and allowance impact.
Expected result: The audience is permitted, strict-valid, no more than 500, and understood.
If this does not happen: Remove uncertain or invalid recipients. Re-import any file that disappeared after reload.
- 3
Review Mail state
Composer > Send with CREBuilder Mail
Confirm approval, current agreement, complete address, effective sender, no suspension or platform pause, and enough displayed allowance.
Expected result: The Send action reflects a current ready state.
If this does not happen: If capability is unknown, retry status. Keep the draft and do not submit until the check succeeds.
- 4
Submit exactly once
Composer > Send
Select Send one time.
Expected result: The composer stays on the in-flight state, the client freezes repeat submission, and the server binds the operation to this exact payload.
If this does not happen: Keep the composer open while the state resolves. If browser storage cannot provide safe operation identity, the send fails closed. Fix storage and retry only when the app clearly reports no attempt.
- 5
Read the returned outcome
Composer result or Email Blasts hub
Treat Sent, In review, Rejected, Failed, Sending, or Outcome unconfirmed according to the status guidance.
Expected result: Your next action follows durable state rather than guesswork.
If this does not happen: Held is not sent. Sending or Outcome unconfirmed may already have attempted transport, so do not create a duplicate send.
One operation, one durable outcome
Rapid clicks and request retries should resolve through the same operation rather than create duplicate transport.
One Send action
Durable operation identity
Preflight and review gates
Terminal sent, rejected, failed, or held state
Sending or outcome unconfirmed
- One Send actionDurable operation identity
- Durable operation identityPreflight and review gates
- Preflight and review gatesTerminal sent, rejected, failed, or held state
- Preflight and review gatesSending or outcome unconfirmed
Know what CREBuilder appends and what Sent means
| Behavior | Meaning |
|---|---|
| Separate messages | CREBuilder submits a separate hosted message for each address selected for transport rather than exposing a group-recipient list. Suppression and later provider outcomes can reduce what is accepted or delivered. |
| Compliance footer | CREBuilder appends the complete company physical address and a personalized unsubscribe link at send time. |
| Signature | An enabled per-user sanitized signature is appended by hosted composition. |
| CSS inlining | Styles are prepared for email-client compatibility at the send boundary. |
| Sent status | The provider accepted or CREBuilder recorded the transport attempts. It does not guarantee inbox placement or reading. |
| Analytics | No open or click analytics are exposed. Property metrics in the composer are listing facts, not engagement metrics. |
| Scheduling | There is no in-app hosted campaign scheduling. |
The campaign is held for review
Likely cause: The account is in its clean-send runway, the audience is Uploaded, or the account uses always-review mode.
- Return to the hub.
- Wait for approval or rejection notification.
- Do not submit another copy.
- Review usually completes within the time described by the current UI.
Preflight removed some recipients
Likely cause: The authoritative suppression check found unsubscribes, hard bounces, or complaints.
- Accept the reduced final audience.
- Do not re-add protected addresses.
- If none remain, stop and rebuild only from permitted contacts.
The immediate outcome is unconfirmed
Likely cause: Transport certainty could not be established after the attempt boundary.
- Open Recent blasts and retain the operation context.
- Do not resend.
- Wait for reconciliation or contact support with subject, time, sender, and status.
Final verification
- Composer > Recipients summary: The audience is permitted, strict-valid, no more than 500, and understood.
- Composer > Send with CREBuilder Mail: The Send action reflects a current ready state.
- Composer > Send: The composer stays on the in-flight state, the client freezes repeat submission, and the server binds the operation to this exact payload.
- Composer result or Email Blasts hub: Your next action follows durable state rather than guesswork.
- No blocking warning, failed status, or unresolved validation message remains in the completed workflow.