Mailbox troubleshooting · Practical guide
Mailbox availability during campaigns: separate connection health from human coverage
A connected mailbox and an available reply owner are separate dependencies. Review both before leaving a campaign active through maintenance, absence or a credential change.
Reviewed · Examples are illustrative
Who this helps: Mailbox owners planning time boundaries, capacity, access and reply coverage.
Define the decision
A mailbox can send while no one is monitoring replies, or an operator can be present while the connection is unavailable. Both situations affect the campaign differently. Document the expected interruption and the criteria for continuing, pausing or resuming rather than relying on a generic connected label.
Work through the procedure
- Identify campaigns selecting the mailbox and the work due during the affected period.
- Confirm whether sending access, incoming sync or human reply coverage will be interrupted.
- Assign a backup or pause the appropriate work when the required coverage is absent.
- After recovery, verify the connection and review uncertain sends and accumulated replies before resuming.
Worked example
The following is a synthetic example for this procedure, not a customer result or performance benchmark.
Availability plan
Operator absence: two working days
Mailbox connection: expected to remain active
Reply backup: not assigned
Decision: establish coverage or pause the campaign scope that requires it
Separate maintenance case: reconnecting the mailbox still requires review of uncertain attempts before retrying.Read the result
The plan avoids treating human absence as a technical failure or technical recovery as proof that every pending action is safe. If replies accumulated during an outage, review them before allowing later sequence steps to proceed. A backup needs both access and the context to fulfill promised actions.
Check before moving on
- Verify actual incoming reply visibility.
- Keep the selected sender list current.
- Document who can pause operations if the outage expands.
Limits and next action
This is an operational continuity method, not a native staff-availability scheduler in Zintara. Connection status does not guarantee human response coverage or uninterrupted provider service. Review the actual campaign and mailbox state.
Source: Zintara product context; procedures and examples are editorial guidance
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features. Check current provider guidance before changing mailbox configuration.
Related guides
- Mailbox connection test checklist: record what actually passed →
- Plan mailbox daily caps around all eligible work and remaining constraints →