> 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/customers-and-work/jobs/send-a-job-summary.md).

# Send a Job Summary

A Job Summary is the no-login recap you share with a customer after a visit. It bundles what happened on the job — visit details, the services performed, the assets inspected, deficiencies, parts and items, photos, property files, the inspection report and signed work acknowledgment, and any unpaid invoice with a pay link — into a single link the customer can open without signing in. It is the share-out counterpart to the Customer Portal.

You can send it from the job's task or from the "..." menu on a submitted inspection report attached to that job. Each section publishes on its own, and sending again updates the same customer link rather than creating a new one.

This is different from **Send Report** on the submitted report or in the Job task's Inspection Reports section. Send Report emails one inspection report PDF directly; Send Job Summary publishes a recap link and lets you choose from all available job sections. The two actions are enabled separately, so a business can use either or both.

## Before you start

* **Enable Job Summaries** must be on in Settings -> Job Summaries, and your role must have inspection-report write access. This setting is independent of the [Task Documents setting for direct inspection-report email](/administration/settings/task-documents-send-and-attach-supporting-documents.md).
* A section only appears when the job actually has that content — a visit with no inspection report won't show an Inspection report section, for example.

## Send a Job Summary

1. Open the job's task and find **Quick Actions**, or open a submitted inspection report attached to the job and use its "..." menu.
2. Choose **Send Job Summary**. The send screen opens as a panel over the page — configuration on the left, a live preview of exactly what the customer sees on the right.
3. Under **Record contents**, choose which sections to include. Each row shows a one-line summary of what's inside. Toggle a section off to hold it back — held sections stay private until you publish them.
4. Check the **Message** — the short personal note that appears at the top of the record. On an unpublished draft with an empty Message, Essential may draft a starting note from the technician's information; edit it, replace it, or clear it out. See [The suggested message](#the-suggested-message) below.
5. Add any **Attachments** or job photos you want to include.
6. Under **Recipients**, add who to email. Start typing to search the customer's contacts, or type and paste one or more email addresses. You can't publish until at least one recipient is added.
7. Choose **Publish & email update** to publish the included sections and email the recipients. Once the summary has been published at least once, **Copy link** becomes available to copy the existing share link to your clipboard — it doesn't publish anything on its own.

Publishing is additive: a section you publish becomes visible on the customer's link and stays there, and sending again updates that same link.

## The suggested message

When you open the send screen on an unpublished summary that doesn't have a message yet, Essential tries to write a starting note. **Drafting…** appears beside the Message heading while it works. The draft uses the technician's visit notes and job summary question answers, plus the visit's services, selected equipment, and open deficiencies.

This suggestion is best-effort. If it cannot be created or the record changes before it arrives, Message stays blank and you can type your own note or use **Suggest a message**.

It is ordinary text in an ordinary box — a starting point, not a decision:

* Edit any part of it, or select it all and replace it with your own words.
* Clear the box to send no message at all.
* If you had already started typing when the draft arrived, your words are kept and the draft is discarded.

Always read it before you publish. It is written from the technician's internal notes, and you are the one deciding what your customer should see. The live preview on the right shows exactly how it will read.

Once a summary has a message — one you wrote or one you kept — reopening the send screen leaves it exactly as you left it. While the summary is still an unpublished draft, one you deliberately left blank gets a fresh draft the next time you open it, so clear it again if you still don't want one. After you publish, the message only changes when you change it: a blank message on a published summary stays blank.

If a suggested draft is sitting in the box untouched and you then change what the record shares — hold back a section, add or remove a visit, or change the selected equipment — the draft is cleared and Essential tries to rewrite it to match. A message you have edited is yours and is never rewritten automatically.

The drafts pick up your business's voice over time. Essential looks at the messages your team has already published on past job summaries and at the wording you accepted from **Suggest a message**, then matches their length, tone, and the kinds of things you usually mention. The more summaries you send, the closer the drafts get to how your business writes. There is nothing to configure — a brand-new business simply gets a plain, factual note until it has a history to learn from.

**Suggest a message**, next to the Message heading, is the related tool for text you have already written: it rewrites your draft rather than creating one from nothing.

## What the customer sees

The customer opens the link with no login and sees a single-page record with your business's name and logo, the visit result, and whichever sections you published:

* **Your message** — the note in the Message box, shown at the top as "Note from {your business}". Nothing appears here if you cleared it.
* **Visit details** — visit type, appointment date, technician, and property.
* **Services performed** — each service and the asset it was performed on.
* **Parts, labor & items** — the items recorded on the visit.
* **Asset Groups** — open a group to see its assets, with any deficient ones flagged, along with that group's photos.
* **Deficiencies**, **Photos**, **Property files**, **Documents** (the inspection report and signed work acknowledgment PDFs), and any **unpaid invoice** with a Pay button.

The record is live — it reflects the current status of the job whenever the customer opens it.

> **Where to find it:** open the job's task -> Quick Actions -> Send Job Summary, or open a submitted inspection report attached to the job -> "..." -> Send Job Summary

## Related guides

* [Set up Job Summaries](/administration/settings/set-up-job-summaries.md)
* [Download or email an inspection report](/field-operations/inspection-reports/download-or-email-an-inspection-report.md)
* [Work acknowledgments on a job](/customers-and-work/jobs/work-acknowledgments-on-a-job.md)
* [Recurring service completions on a job](/customers-and-work/jobs/recurring-service-completions-on-a-job.md)
* [What your customers see in the Customer Portal](/administration/what-your-customers-see-in-the-customer-portal.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.withessential.com/customers-and-work/jobs/send-a-job-summary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.