Skip to main content
The Glass module is for auto-glass shops running daily field operations and receivables in one place. It combines dispatch, customer records, insurance tracking, technician assignments, and unpaid job follow-up. The rail is grouped into Operations, Sales, Inventory, and Settings. Settings is collapsed until you open it. Glass reporting — Analytics Overview and Job Search — lives in the app-wide Reports hub, reached from More → Reports. For identifying a vehicle by photo, plate, or year and make, and pricing the glass it takes, see Identifying a vehicle.

Dashboard

The dashboard is the operational landing page. It highlights:
  • Today’s jobs so the team can see what needs to move now
  • Unpaid jobs so AR follow-up is visible without opening a report
  • Quick actions like New Job
If your team starts the day from dispatch, use the dashboard as the bridge between field work and office follow-up.

Jobs

A job is the center of the module. It ties together:
  • customer
  • vehicle
  • shop
  • technician assignment
  • insurance information
  • parts
  • status and schedule
  • invoice / receivable context
Open a job when you need the full operational picture for one piece of work. Attachments on a GlassBiller job sync into Zeno automatically and show on the job detail.

Starting a job from another job

When a car comes back — a warranty, a call-back, or simply more glass on the same vehicle — use New job from this on the job header and pick the reason. The new-job form opens already holding that job’s customer, vehicle, claim and parts, with every carried line priced at $0. Type a price on any line the customer is actually paying for; anything left at zero bills zero, and the carrier’s rate card will not fill it in. Nothing is created until you submit the form, so opening one costs nothing. Once saved, the two jobs show each other under their headers (“Warranty from #10847”), and the reason is stored on the job rather than buried in a note.

Dispatch and technicians

Dispatch groups jobs by day and shop so the team can see the workload in calendar context. Technicians stores the per-tech master record. A user linked to a technician record sees My Jobs — only that person’s assigned work — and My Report, which answers “how many did I do last week” on screen and still prints the pay-period PDF. Managers get Jobs, the full cross-shop list, and Dispatch for the daily board. Use these pages together:
  • Dispatch for office coordination
  • Jobs for managers searching across shops and dates
  • My Jobs for field technicians (auto-scoped to the signed-in tech)
  • My Report for a technician looking back over a week, a month, or the year
  • Technician detail for mapping people to work history

Customers, insurance, vehicles, and parts

The Glass module keeps the supporting records needed around each job:
  • Customers for contact and account context
  • Insurance for carrier-linked work
  • Vehicles for the actual units being serviced
  • Parts for what was installed or quoted
  • ADAS for calibration-related tracking
These pages are reference surfaces as much as list pages. Open them when you need to answer “what jobs are tied to this customer, carrier, vehicle, or part?”

Receivable

The Receivable page focuses on unpaid jobs. Use it when you need to follow outstanding balances rather than operational dispatch status. Like the rest of Zeno, receivable activity still rolls into the shared accounting layer in Books and Reports.

Settings

Module-wide setup lives in Settings → Glass: the daily digest recipient (an end-of-day recap of jobs, customer changes, and contact-sync status), GLAXIS Credentials for the supplier connection, and Pricing — per-shop insurance and retail rate cards (labor rates, NAGS discounts, adhesive kits, ADAS recalibration) synced from GlassBiller. Shop-specific setup lives on each shop record: invoice prefix, deposit account, address and phone, plus the OpenPhone number ID and review URL used to send post-job review-request texts.