Customer
Sees only their own jobs.
- Pages
- Home, My jobs, Visit reports, Quotes, Invoices, What to expect
- Can start
- Book a job
Jobs
Jobs by status
New2
Assigned3
On site1
Waiting on parts1
Complete3
Canceled0
Field service dispatch portal for technicians
A field-service dispatch portal is where a dispatcher assigns each customer job to a technician, the technician sees only their own jobs, and completes each one on site with photos and a checklist. Customers see their own jobs and where each one stands.
Pattern: RequestsDescribe it to Pory
“Customers report jobs that need doing, our dispatcher assigns a technician, and the technician works through a checklist and adds photos on site before marking the job complete.”
Viewing as
In plain English
How Pory sets it up
Pory gives every customer, dispatcher and technician a sign-in of their own. Each customer sees only their own jobs. It covers job → assign → complete. Jobs, job checklist, visit reports, quotes, invoices and team live in Pory's own database, so there's no spreadsheet to keep in sync.
What it does
Dispatchers put each job in front of the right technician
Jobs were dispatched by phone call and text, and the whiteboard back at base was out of date by 9am. The dispatcher opens a new job, picks the technician, and it appears on that technician's list with the address and arrival window. The board shows what's still New, so no one's oven waits because a text went unread.
Assign to a personDone by: Dispatcher
Technicians start the day with only their own jobs in view
Technicians got a group text listing every job for the day and worked out for themselves which were theirs. Each technician signs in to a list of only the jobs assigned to them, with the visit date, the arrival window, the address and where each one stands. Nobody turns up at a job that was given to someone else.
Who sees which recordsDone by: Technician
Technicians check off each step and add photos before closing a job
Proof of work was a photo on the technician's own phone and a promise that the filters got cleaned. On site, the technician works through the job's checklist (shut off power, clean filters, test run) and logs a visit report with photos before marking the job complete. The customer reads the same report, and the office stops calling to ask whether the work got done.
ChecklistsDone by: Technician
Who sees what in a field-service dispatch portal
Every person signs in to their own view. This is what each role in the demo gets.
Dispatcher
Sees every job in the portal.
- Pages
- Home, Jobs, Dispatch calendar, Quotes and invoices, Team
Technician
Sees the jobs assigned to them.
- Pages
- Home, Assigned to me, On site, My calendar, Team
- Can start
- Log a visit report
What’s in the field-service dispatch portal template
The tables and fields Pory sets up for this portal. Describe your own version and change any of them in the editor.
Jobs
- Job (text)
- Visit date (date)
- Arrival window (choice: Morning, 7am to noon, Afternoon, noon to 5pm)
- Address (text)
- Job type (choice: Plumbing, Electrical, Gas and heating, Air conditioning, Appliance repair)
- Customer (link)
- Technician (link)
- Status (choice: New, Assigned, On site, Waiting on parts, Complete, Canceled)
- What happens next (text)
- Photos (file)
- What the customer told us (long text)
Job checklist
- Step (text)
- Job (link)
- Technician (link)
- Done (yes/no)
Visit reports
- Report (text)
- Visited (date)
- Technician (link)
- Job (link)
- Photos (file)
- Customer (link)
- What we found and did (long text)
Quotes
- Quote (text)
- Sent (date)
- Valid until (date)
- Amount ($) (number)
- Status (choice: Sent, Accepted, Declined)
- Customer (link)
- Quoted by (link)
- What's included (long text)
Invoices
- Invoice (text)
- Issued (date)
- Due (date)
- Amount ($) (number)
- Status (choice: Issued, Paid, Overdue)
- Customer (link)
- Job (link)
Team
- Name (text)
- Role (text)
- Area (text)
- Phone (text)
The parts behind this portal
Each one reads and writes the same records, so a form, its approval and the status page someone checks are one system. How Pory builds a portal
Decide
2 partsChecklists
A task list on each record, ticked off in its detail view, with progress shown. Use it for onboarding, inspections or opening duties.
Assign to a person
Name who a record is for and it lands on their list, and nobody else's.
Control
3 partsWho sees which records
Each person sees their own records, the ones assigned to them, or the ones they manage. Fields can be hidden per role. Pory sets this up from your description, and you can adjust it in the editor.
Passwordless sign-in
A sign-in link by email, by default. Password sign-in if you'd rather.
Your brand
Your domain, your colors, your logo. Members see you.
Frequently asked questions
A customer signs in with a link sent to their email and lands on Home. They see Home, My jobs, Visit reports, Quotes, Invoices and What to expect, and only the jobs that are theirs. From there they can use “Book a job”.
You invite them. Each person gets a sign-in link by email, with no password to set, and lands in the role you chose for them.
More field service portals
All field service portalsInspection reports portalChecklist → photos → defects assignedEquipment maintenance logs portalSchedule & historySafety incident reporting portalReport → investigate → closeCleaning & janitorial portalJob checklists & photo proofLandscaping & pool service portalService visits & each client's historyRestaurant & franchise ops portalChecklists & incident logs
Build your field-service dispatch portal with Pory
Describe who signs in and what each person needs, and Pory builds it. Join the waitlist while signups open; paid plans are a flat price with unlimited customers.