Skip to main content
Mailboxes are the email-side identities used inside a sender profile. Within multichannel execution, mailboxes provide the actual email sending and reply-handling context for sequence actions.

​
Role inside sender profile

A sender profile can hold one or more mailboxes. That lets the sender profile represent a complete sender context for email execution, while the sequence decides when email actions should occur. For an end-to-end example of how mailbox-backed email execution is enabled through sender-profile assignment in a multichannel flow, see Create a multichannel sequence. In the multichannel-api public response model, mailboxes are exposed under sender profiles as mailbox identities with values such as ID and address. In salesforge-api, mailbox health and status are operationally richer, which is why mailbox readiness matters even when this concept page stays abstract.

​
Mailbox readiness and health

At the concept level, a mailbox should be thought of as either usable for sending, still being prepared, or unavailable for reliable execution. Across Salesforge mailbox handling, operational states such as Active, Pending, Access Lost, and Suspended are important because they affect whether email steps can proceed safely.
  • Active generally represents a mailbox that is ready for normal sending behavior.
  • Pending represents a mailbox that exists but is not yet fully ready.
  • Access Lost means the mailbox connection or authorization is no longer healthy.
  • Suspended means the mailbox should not be used for normal sending until the issue is resolved.
For shared product-level guidance, see Mailbox concept.

​
Practical usage patterns

  1. Keep mailbox assignment aligned with the sender profile that will execute the sequence.
  2. Validate mailbox readiness before launch and when investigating delivery issues.
  3. Use mailbox identity consistently for reply handling and thread continuity.