Email Sending and Document Delivery Guide

Overview

Tab Path: Utilities > Send Email / Document Toolbar > Email

The QBM email form is used by several document-delivery workflows. It allows users to prepare the message fully before sending.

This guide is based on the actual Email screen, including the Email tab, the Attachments tab, and the option to use the default email client.

Screen	Tab Path	Use It For
Send Email	Utilities > Send Email or Document > Email	Prepare and send the email message itself.
Attachments Tab	Send Email > Attachments	Add or remove supporting files before sending.

Field Or Control	What It Means
To	The main recipient list. Group addresses can also be used where available.
Cc	Additional copied recipients.
From	The sender identity used for the message.
Subject	The subject line shown to the recipient.
Template	A reusable message structure or text starting point.
Note / Body	The message text itself.
Right to Left Alignment	Useful when the email content needs right-to-left formatting.
Attachments	Files added to the message from the Attachments tab.
Send using default email client	Hands off the email to the user's desktop mail application instead of relying only on QBM's internal sending method.

The email form is a review screen. Users review recipients, message content, and attachments before sending.
The checkbox for the default email client changes the delivery route and is useful when the business prefers Outlook or another desktop mail program.
Templates and grouped addresses can speed up repetitive sending tasks when they are maintained carefully.

Open the email form from the document or utility workflow.
Review the To, Cc, and From values.
Enter or confirm the subject and the body text, and choose a template if appropriate.
Open the Attachments tab and add any supporting files needed for the recipient.
Choose whether to send using the default email client or QBM's direct method, then send the email.

Always review the attachment list before sending.
Use clear subjects so recipients can identify the document quickly.
Test the default-client route and the direct route separately when support is troubleshooting email behavior.
Keep reusable templates simple and professional.