---
# System prepended metadata

title: UptimeHealth Email Standards

---

# UptimeHealth Email Standards
Emails are generally categorized as those sent to *technician*, *requester*, or *both*. The header and footer of each email is consistent regardless of the recipient. The body, which contains the *greeting*, the *message*, and the *job info*, is unique to the recipient.
## Emails To The Job Requester
Emails sent to the requesting party are sent to the person who requested the job and the device manager is always sent a carbon copy.
### Greeting And Message
Below is a list that describes the *greeting* and *message* sections of emails sent to the requester: 
* Emails greet the requester by their **company's name**
    * The is because the email could be read by either the device manager or the requester
* Service request is associated with the requester's **facility name**
    * This is so that the requester can assure their request is for their facility and the device manager can quickly see where the service is needed
* Technician is referenced by **technician company name**
    * This depth of info is adequate for the reader

#### Example greeting and message sections sent to requester
![](https://i.imgur.com/AA6dWuE.png)
### Job Info
The list below describes the *job info* section of emails sent to the requester:
* **Requester's full name** is included
    * This is so that the device manager may contact the person to inquire about the job
* **Technician's contact info** is given
    * This is so that the requester of device manager may contact them if necessary
#### Example job info section sent to requester
![](https://i.imgur.com/6nhfm1o.png)

## Emails To Technician
Emails are sent directly to the technician whom the facility requested to complete the job.
### Greeting And Message 
Below is a list that describes the names used in the emails sent to the technician:
* Emails greet the technician by their **company's name**
    * The is in case multiple technician's share an email address for service requests or have an admin that dispatches
* Service is noted as being created by the requester's **facility name**
    * This is so that tech who services multiple facilities owned by a company will know precisely which one needs service
#### Example greeting and message sections sent to technician
![](https://i.imgur.com/so8AecU.png)
### Job Info
The list below describes the *job info* section of emails sent to the requester:
* **Requester's contact info** is included
    * This shows the tech the address where they will go plus phone & email in case they want to contact the facility
#### Example job info section sent to technician
![](https://i.imgur.com/cCu022B.png)
## Emails Sent To Both Technician And Requester
Job-related emails (except for the initial 'New Job' email) will recursively list all devices *and* areas associated with the job. Below is a list describing this:
* If there are devices, there will be a section that says *This is a list of the devices associated with this job*
    * Each device will note the **Work Order ID**, **Asset ID**, **Control ID**, **Make**, **Model**, **Serial #**, and **Issue**
* If there are areas, there will be a section that says *This is a list of the areas associated with this job*
    * Each area will note the **Area**, **Work Order ID**, and **Issue**
        * Currently only one issue is listed for areas
* If there are areas and devices, there will be a list for each
    * This is currently pending an enchancement to our app but is already implemented in the email templates
#### Example job info section sent with multiple devices
![](https://i.imgur.com/39LZam2.png)
#### Eaxmple job info section with multiple areas
![](https://i.imgur.com/vED8hKy.png)