> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/set-up-job-summaries.md). # Set up Job Summaries The Job Summaries settings page turns Job Summaries on or off and sets what each new Job Summary shares by default. A Job Summary is the no-login recap link you send a customer after a visit — the share-out counterpart to the Customer Portal. Your team then sends individual summaries from each job; see [Send a Job Summary](/customers-and-work/jobs/send-a-job-summary.md). Job Summaries do not control the direct **Send Report** action for inspection reports. That action emails one report PDF and is enabled separately with **Email inspection reports** under Settings -> Work Management -> Tasks -> Task Documents. A business can turn on either sharing method or both. > **Where to find it:** Settings -> Customer Experience -> Job Summaries ## Turn Job Summaries on or off Use **Enable Job Summaries** to turn the feature on for your business. When it's on, the defaults below are what every new summary starts from. ## Choose what's shown by default The **Shown by default** list sets which sections a new Job Summary includes to start: * Visit details * Arrival time * Time spent * Service description * Services performed * Asset Groups * Deficiencies * Photos * Property files * Inspection report * Work acknowledgment * Parts & labor * Unpaid invoices Toggle any section on or off. Arrival time, Time spent, Service description, and Parts & labor start off. Arrival time, Time spent, and Service description also stay off for businesses already using Job Summaries; existing summaries and shared links do not gain this information automatically. These are only defaults — whoever sends a summary can still turn individual sections on or off for that send before it goes out, and a section only appears when the job actually has that content. To show customers when your technician arrived, enable **Arrival time** and choose **Save defaults**. Each new summary then shows the time the technician first clocked in on each visit. You can still turn it off for an individual summary before sending it. For office job tickets, enable **Time spent** and **Service description**, then choose **Save defaults**. The sender can edit each visit’s Service description in the summary before saving and sharing. New summaries will start with those sections selected. For an existing summary, include them in that summary's Record contents before publishing. Review the preview: once published, these details are visible to anyone with its share link, just like the other published sections. Job custom fields have individual toggles under **Record contents → Edit** on the [Send Job Summary screen](/customers-and-work/jobs/send-a-job-summary.md#include-job-custom-fields-such-as-a-po-number). They start on, and each toggle automatically remembers the default across your business for future summaries. ## Customize the email The **Email** section is the message that goes out with the share link. Essential wraps it in your branding — your logo, a **View job summary** button, and your contact details. Personalize the **Subject** and **Message** with Liquid variables such as `{{ customer.name }}`, `{{ visit_dates }}`, `{{ reference }}`, and `{{ record_url }}`. **Save defaults** applies the toggle, the default sections, and the email together. It affects new records only — existing live links stay unchanged. The **Subject** editor starts at one line and grows automatically as text wraps or line breaks are added. The default subject includes the property name, street address, and visit dates when available. The email body includes the property name and address, job number, technicians, and visit dates when available. Existing saved subjects remain as configured; use `{{ property.location.name }}` and `{{ property.location.address }}` to include both in a customized subject. Use **One visit**, **Multiple visits**, and **No portal access** above the email preview to check conditional Liquid and the finished email details for each case. A portal link appears only when your business has the Customer Portal set up and the sample customer has access. Switching this preview tab does not change the Subject or Message and does not save any settings. ## Related guides * [Send a Job Summary](/customers-and-work/jobs/send-a-job-summary.md) * [Task Documents: send and attach supporting documents](/administration/settings/task-documents-send-and-attach-supporting-documents.md) * [Download or email an inspection report](/field-operations/inspection-reports/download-or-email-an-inspection-report.md) * [Enable or disable the Customer Portal for all customers](/administration/settings/enable-or-disable-the-customer-portal-for-all-customers.md) * [What you can set up in Settings](/administration/settings/what-you-can-set-up-in-settings.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://learn.withessential.com/administration/settings/set-up-job-summaries.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.