Message Delivery Status

In this article

Understand delivery statuses

The delivery status tells you what happened to an email sent through YoPrint. Use it to check a customer message and retry a failed delivery after correcting the recipient's email address.

Delivery status What it means
Waiting to send The email is in the queue to be sent.
Sending... The email has been sent for delivery, but YoPrint has not yet received a delivery result. Most confirmations arrive within a few minutes, but mail server delays can take longer.
Delivered YoPrint has received a delivery confirmation. This is not a read receipt.
Delivery failed The email could not be delivered. Check the recipient's address before retrying.

A sent customer message showing Sending...

The same customer message showing Delivered

Delivery tracks whether the email reached the customer's mail server. YoPrint does not track email opens or read receipts.

The Status you assign for follow-up, such as Awaiting Customer Reply, is separate from Delivery. Changing a follow-up status does not affect delivery tracking, and delivery results do not change your follow-up status. See Manage customer message statuses.

Check a message's delivery status

  1. Open Sales in the top navigation.

    Sales in the top navigation

  2. Choose Messages.

    Messages in the Sales menu

  3. Check the Delivery column, then double-click the message text in the row to open the conversation. Click the message text rather than the blue order number link, which opens the sales order instead.

    A message row in the Messages list

  4. Hover over the recipient's name in the message header to check the email address.

    The recipient's email address appears on hover in the message header

Correct an address and retry a failed email

A typo in an email address can cause delivery to fail. Confirm the address with your customer before changing it. If the address is already correct, check with the customer before retrying.

When an email fails to deliver, YoPrint marks the message Delivery failed and shows a Retry Failed? button in the message header. Correct the recipient's address before retrying.

A customer message with Delivery failed and Retry Failed?

With the conversation open:

  1. In the composer at the top of the dialog, click the pencil icon (Edit recipients) beside Sent To.

    The Edit recipients pencil beside Sent To

  2. In the Email Participants dialog, open the three-dot menu beside the contact.

    The contact's three-dot menu in Email Participants

  3. Choose Edit Contact.

    Edit Contact in the participant menu

  4. Correct the Email address.

    The Email field in Edit Contact

  5. Click Save. Saving the corrected address updates the customer's contact record for future orders and messages.

    Save the corrected contact

  6. Close Email Participants to return to the conversation.

    Close Email Participants after saving the contact

  7. Click Retry Failed? beside the failed recipient in the message header.

    Retry Failed? beside the recipient on the failed message

The message returns to Sending... while delivery is attempted again. It changes to Delivered when YoPrint receives a delivery confirmation. Clicking Retry Failed? resends the email only to recipients whose delivery failed; recipients who already received the email do not get a duplicate. If delivery fails again, confirm the address and the customer's ability to receive email before another retry.

Find delivery-failure notifications

If delivery fails, YoPrint notifies the order's creator in the app and by email. The in-app notification identifies the order, for example Unable to deliver message to customer for SO0001. Alerts appear under the notification bell in the top navigation bar. Click the alert to open the conversation directly.

Use the message's Delivery status to check its current state. A failure notification can remain after you retry the message. You can dismiss or archive it from the notifications panel under the bell.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.