Send an email and understand its status¶
This guide follows the inspected Final Screens for composing a personal mailbox email and viewing its sending status. The current frontend remains a preview: its Send control navigates back to sample inbox content. That transition does not submit an email.
Use the steps below in a connected implementation. Check the correct organization and work mailbox connection first. A working connection is useful preparation; accepting an email for processing is still separate from the later provider send.
Compose an email¶
- In HiveComms → Mailbox, check Signed-in work email.
- Select Compose email.
- Under To, enter the recipient's Name and Email. Check both carefully; the inspected design uses one primary recipient.
- If others need a copy, complete each Cc name and email. Use Add another Cc for another copy recipient. Each copy recipient must be complete.
- Enter Subject and Message.
- Review the sender, recipient and copy addresses, subject and message. Select Send email once when ready.
- Keep the resulting status associated with this send. If the confirmation is lost or unclear, follow the recovery guidance below before submitting again.
Personal sending supports one primary recipient and optional Cc recipients. This walkthrough covers the direct-address form. Instructions for choosing a person from your organization will be added when that interface is verified.
This compose path does not provide outgoing attachments, Bcc, scheduling, saved drafts or an original-message reference for reply threading. The preview's Attach control and Reply navigation do not establish those outcomes. Reading an incoming attachment and attaching a file to an outgoing message are separate capabilities.
The sender comes from the person's connected mailbox when the background send executes. The status result does not itself include a full copy of the compose form. If the interface loses your compose context, do not guess the recipient or message from a status badge alone.
Read the sending status¶
Status describes the processing recorded by Zerohive. It does not prove that the recipient received, read or acted on the email.
| Intended screen label | What it means in the inspected personal sending path | Your next step |
|---|---|---|
| Queued | Zerohive returned an acceptance result for background processing. The provider has not necessarily received the email. | Keep the result and allow processing. If status remains unresolved, ask support to reconcile the original send. |
| Sending | A send attempt is recorded as in progress. A request timeout or closed page is not proof that the attempt stopped. | Wait for the result; do not create a duplicate while the outcome is uncertain. |
| Accepted by provider | The outgoing provider accepted the send. Saving a Sent-folder copy is a separate operation and can fail after acceptance. | Do not expect this status to automatically become Sent and confirmed in the inspected path. Check the actual evidence if confirmation matters. |
| Sent and confirmed | In the ordinary personal-send recovery path, a matching message identifier was found in the sender's Sent folder after an uncertain send. | Treat this as sender-side evidence, not recipient delivery or a read receipt. |
| Trying again | Another automatic attempt was scheduled after a retryable failure. | Do not manually send another copy. If retries stop or remain unresolved, seek support. |
| Confirmation unavailable | Sending may have started, and the service could not establish the outcome. | Reconcile the original send before sending again. An absent Sent-folder copy is not proof that no recipient received the message. |
| Not sent | Processing has reached a recorded failed state, including permanent failure or exhausted retry attempts. The badge alone does not identify the exact cause. | Review the error and connection with support as needed; do not infer a specific provider rejection from the generic label. |
The designs also include Delivery window ended and Sending stopped. The backend declares these states, but this inspection did not establish a user cancellation action or automatic expiry process that produces them. Do not assume a Cancel control, a fixed sending window or a recall capability is available.
Automatic retries have a finite policy. Their existence does not promise a delivery deadline, continuous provider availability or exactly one external delivery under every failure. A subject match in Sent Items alone is insufficient to identify a particular attempt.
Recover from a missing or uncertain result¶
If you select Send email but do not receive a usable result, keep the original compose information and any reference supplied by the connected product. Check the existing status first. Repeating the action as a new send can create a second email.
In the inspected uncertain-result screen, Open Sent Items opens the intended sent-mail location and Back to Inbox leaves the status view. Inspect the relevant message using the reading guide. Compare the sender, recipients, time and content, not only the subject. Support may need to reconcile the original send with provider evidence when the result remains unclear.
| Situation | What to do |
|---|---|
| The page closes or times out after Send | Recover the existing result or ask support to trace the attempt. Do not treat the interrupted page as proof of failure. |
| A retry is already scheduled | Allow that attempt to proceed. Avoid composing another copy to work around the wait. |
| Provider acceptance appears but Sent Items has no matching copy | A Sent-folder save can fail after acceptance. Ask support to check the send before resubmitting. |
| A similarly titled message is in Sent Items | Compare recipients, time and content. Repeated subjects are common and do not identify the original attempt on their own. |
| The result says access is unavailable | Check that you are the sender in the correct organization, or ask an authorized support person. Being the recipient does not by itself grant access to the sender's Zerohive status. |
| Credentials changed or the mailbox was disconnected during sending | Reconcile the existing attempt. Disconnecting is not a recall or proof that an already-started send stopped. |
| Recipient or Cc details are rejected | Correct the incomplete or conflicting recipient information before submitting a new, clearly intended send. Each direct-address recipient needs both a name and a valid email. |
| The outcome remains unclear | Give support the organization, sender, intended recipient, approximate time, visible status/error and any available send reference through the approved channel. Share only the message content needed for investigation. |
The status page is available to the sender in the current organization and to appropriately authorized tenant-wide support readers. An administrator title alone is not proof of the required permission. Status access does not automatically grant access to another person's mailbox contents.
Business and record-keeping expectations¶
Use provider acceptance and sender-side confirmation for their stated purposes. Where a business process needs the recipient's acknowledgement or a verified work outcome, obtain that separate evidence. A mailbox badge cannot replace it.
Recorded outgoing activity also has its own limits. Read mailbox email history before using history as evidence of communication or staff performance. Read Email linked to a business task for source verification, corrections and contribution meaning. This personal compose guide does not establish completion of a request, case, project or correspondence workflow.