Automated ServiceTitan Project Galleries

The Friday upload that never happens

How the automated gallery works

Six steps from a closed job to a published entry. Steps 2 and 5 are where this differs from simply connecting the API, and that's deliberate.

1. 1

   The job is completed in ServiceTitan

   Nothing changes for dispatch or the office. Technicians complete and close the job in ServiceTitan the way they do today.

2. 2

   The technician uploads photos to your own app

   Before leaving the driveway, the tech opens a small mobile web app your company owns, enters the job number, marks photos as before, during or after, and uploads them. The photos go to your media repository, not through ServiceTitan's API. The upload app is a compact custom web application, so there's nothing to install from an app store.

3. 3

   Job facts are used in the private review tool, where permitted

   When a reviewer opens the batch, the admin tool can look up the job number through the API, using read access your admin approves, and show the job type, business unit and completion date so the photos land under the right service. Those details appear only inside the private tool and aren't kept or published. If you'd rather not connect it, the reviewer picks the service from a list.

4. 4

   The office reviews and approves

   A reviewer confirms consent, crops out house numbers and faces, picks a cover photo and writes a one-line caption and alt text. Nothing publishes without an approval. The photo review and approval tool.

5. 5

   A public entry is created from content you own

   The website entry is built only from your photos and your team's caption, with a neighborhood-level location and a service tag. EXIF and GPS data are stripped, and each image is converted into web-ready sizes and formats.

6. 6

   The website portfolio updates

   The gallery, the matching service page and the sitemap update on the next publish. Unpublishing is one click and removes the entry from every page it appeared on.

What the published gallery does

• Filters that match how customers shop

  By service, job type and area. Each filtered view has its own address, so a salesperson can text a homeowner a link to tile roofs or heat pump installs nearby.

• Freshness without the chore

  Newest approved jobs first. Service pages pull the latest matching entries automatically, so the HVAC page always shows recent HVAC work.

• Fast images

  A phone photo can run several megabytes. Each approved image is generated in responsive sizes in modern formats such as WebP or AVIF, served with fixed dimensions so the page doesn't jump, and lazy-loaded below the fold.

• Entries search engines can read

  Descriptive alt text from the reviewer, readable URLs, and a path for the best jobs to become full write-ups. Completed jobs to case studies.

• Rules you set once

  Exclude job types that shouldn't appear, such as warranty calls or drain cleaning, and hold back commercial clients who don't want their buildings shown.

• A clean takedown

  If a customer changes their mind, unpublishing removes the entry, its image files and its links, and the consent record notes why.

Native ServiceTitan vs a custom automated gallery

Examples by trade

Hypothetical setups that show how the rules and timing change.

• HVAC

  A shop installing several systems a week might publish installs only, never repair calls, filtered by system type, with each service-area page showing recent installs at neighborhood level.

• Roofing

  Techs upload at tear-off, after dry-in and at final. The entry can't be approved until the final set arrives, so half-finished roofs never appear.

• Garage doors

  Quick jobs and lots of them: one cover photo per job and a batch approval on Friday afternoon. House numbers and driveway cars get the closest look.

• Plumbing

  Water heater and repipe jobs only. Drain and sewer calls are excluded by job type, so nobody scrolls past a clogged main line on the way to a tankless install.