E-mails QuantumOps sends
A catalog of the e-mails that QuantumOps and your sign-in service send, with who receives each one, when, what the subject says, how to switch it on or off and where to read more.
Last updated 26 days ago
QuantumOps sends e-mail for many features, and some messages come from other systems on its behalf. This page lists each e-mail by feature: who receives it, when it is sent, what its subject says, how to switch it on or off and which page explains the feature. Use it when someone asks where a message came from, or why one did not arrive.
Where each e-mail comes from
Five senders are involved. Knowing which one sent a message tells you where to look when it goes missing. Which sign-in service your instance uses decides some of the rows below; Signing in says how to find out.
For e-mails sent through HaloPSA, QuantumOps sends the body of the message. Where the tables below say the subject comes from your HaloPSA e-mail template, QuantumOps sends no subject of its own and HaloPSA builds it.
Sign-in and account e-mails
AI processing and verification codes
All of these come from QuantumOps and have no switch.
E-mails to your customers, sent through HaloPSA
QuantumOps posts each of these to HaloPSA, which sends it from your mailbox. They need a working HaloPSA connection.
On Autotask and ConnectWise PSA these messages go out differently: QuantumOps posts each one to the ticket as a customer-visible note, and your PSA e-mails it with its own template. Neither PSA can send a free-form e-mail for another system. See Customer e-mail on Autotask and ConnectWise. An NPS campaign e-mail, which is not tied to a ticket, is sent by QuantumOps itself on those PSAs.
Surveys sent for closed tickets work differently. QuantumOps does not send a survey when a ticket closes. The faces in those e-mails are a block you paste into your own HaloPSA e-mail templates, and HaloPSA sends the message. See Adding the survey to HaloPSA e-mails and Survey settings, tags and the survey page. Launching an NPS campaign e-mails a personal survey link to each address on your list, through HaloPSA, with the campaign's Email Subject. See NPS campaigns.
Identity verification e-mails
Q-Notice and alert e-mails
A notice can list up to 25 addresses on its Email channel. QuantumOps sends at most 200 recipient e-mails an hour for your organization, counting each recipient: a notice to ten people is ten. A notice that would go over the limit is recorded as a failed e-mail delivery with the reason, not dropped silently.
QBR e-mails
QBR Studio e-mails come from QuantumOps, except the pre-read, which you can send from your HaloPSA mailbox instead. Each notice is sent once per step; a notice that fails three times is not tried again.
For the pre-read, Your Halo mailbox (recommended) sends from your HaloPSA mailbox, with the subject from your HaloPSA e-mail template. The QuantumOps sender (donotreply@qops.app) sends it from QuantumOps with the report title as the subject and replies going to the report owner. See Review, publish and share with the client and QBR settings.
Timeclock and payroll e-mails
Timeclock notices come from QuantumOps and are off until you switch them on, except the accountant's review notice, which is on from the start. Open the Settings section of the Timeclock Admin Hub, then Notification Settings. Each event has its own card. On a card you switch the event on, check Notify affected employee and/or Notify supervisors, and add other addresses under Additional recipients:. New cards start with Notify supervisors checked for time off requested, holiday bid submitted, punch exception created and missed clock-out, and with Notify affected employee checked for the approved and declined events, for the time-off reminder and for missed clock-out. Notify supervisors mails every supervisor who has an address. The affected employee receives an e-mail only if they have an address on their payroll record. See Timeclock and payroll e-mail notifications and Timeclock administration.
The time-off reminder and the holiday-bid e-mails have a card each on that screen and stay off until you switch them on.
Paystubs are separate. Your Pay Statement - followed by the pay period's dates is sent from QuantumOps Payroll to each employee, with the paystub as a PDF attached. It goes out when you select Send Paystubs in the Finalize step of the payroll wizard, which needs a locked period. An employee without an e-mail address on their payroll record counts as failed, and the wizard reports how many failed. See Payroll wizard: finalize and paystubs.
Partner e-mails
Partner organizations that use White Label credits also receive a monthly credit-usage summary and a warning e-mail when credit use crosses a warning level. Those e-mails go to the addresses set by the partner's administrators. They are described in the partner documentation.
When e-mail is not set up
QuantumOps sends its own e-mail through a mail service that TechPulse sets up for your instance. If it is not set up, the e-mails from QuantumOps in the tables above are not sent. Most features do not warn you: the message simply does not arrive. These are the places that do say so:
- QBR settings shows E-mail is not configured., and the Send a pre-read dialog says the pre-read cannot be sent and does not let you send it when The QuantumOps sender is chosen. With Your Halo mailbox (recommended) the pre-read goes through HaloPSA and is not affected. Copy the client link instead.
- The Ticket Dashboard answers We could not send the verification email. Please try again shortly. when you select Send code.
- For Authenticator step-up the panel shows Not verified with a reason, and nothing is sent to the caller. Use your out-of-band identification procedure.
- With Auth0, Send password reset reports that the reset link was created but could not be e-mailed when the mail service refuses the message, and an invitation reports that the welcome e-mail could not be sent; neither says it succeeded.
- Send Paystubs reports how many paystubs failed.
Pausing and resuming AI processing still works without e-mail; only the notice is lost.
E-mails sent through HaloPSA depend on your HaloPSA connection and mailbox, not on this. That includes a QBR pre-read sent through Your Halo mailbox (recommended). E-mails from your sign-in service depend on that service. If e-mail from QuantumOps never arrives for anyone, ask TechPulse to check that e-mail is set up for your instance. See Getting help.
Related pages
- Activating your account covers the sign-in service e-mails from the receiving side.
- Team Management is where invitations and password resets are sent from.
- Issuance campaigns covers the campaign delivery options.
- Working the alert feed covers the Customer Success e-mails.
- Roles and access, Modules reference and the Glossary are the other reference pages.
Was this helpful?
More in Reference
Roles and accessStill need help? Ask the team