Your customers see their own scheduled visits, who is coming, what was done last time, the photos from the site, and the report they need to sign off. Field businesses run on information that usually lives in a technician's phone, and this pulls it into one signed-in place the customer can reach.
The closest starting point is Project Portal, a live Taskade Genesis app embedded on this page. Move work across a real client-visible board, then choose "Use this app" to clone it in about ten seconds and rebuild it around your service calendar and job sites.
The build gives you a job record customers can follow. Each visit carries the site, the customer, the date and window, the assigned technician, the work scope, the photos, the parts used, the completion notes, and the sign-off status. The customer signs in and sees their own site history, the next scheduled visit, and any report waiting for their approval. Your team works the same jobs from a dispatch board, so the schedule the customer sees is the schedule that exists rather than a copy someone maintains.
Photos are what make a field portal credible. A customer who can see the before and after of a visit, dated and attached to a job, does not need to take your word for what was done. The same photos protect your business when a question comes up months later about the state of a site. Capturing them at the job, straight into the record rather than into a camera roll that gets cleared, is the habit worth building, and the app runs on a phone so the technician does it where the work happens.
Workspace DNA runs the field operation. Memory keeps every site, visit, and photo, so the technician arriving in March knows what happened in November. Intelligence, powered by 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, writes the visit report from the technician's rough notes and photos, and flags a site whose recurring issue keeps returning. Execution sends the appointment confirmation, the on-the-way notice, and the report for sign-off.
The schedule renders in every layout you need:
- Board view for dispatching jobs across technicians and days
- Calendar view for the customer's own visit schedule
- Table view for the internal job register with status, parts, and sign-off
- List view for a single site's visit history
- Plus Mind Map, Gantt, and Org Chart across the 7 project views
Automations run the coordination. Connect Taskade automations so a booked visit confirms to the customer, a completed job publishes the report for sign-off, and an unsigned report after three days sends a reminder. With 100+ bidirectional integrations, your scheduling and accounting tools pull jobs and invoices in, while email and Slack push confirmations and dispatch notices out.
Keep the customer-facing report short and factual: what was done, what was found, what needs attention next. Long reports go unread, and the one line about a part that will need replacing next visit is the line that generates your next booking.
The AI agents in the app carry 34 built-in tools including file analysis and persistent memory. An agent reads the uploaded site photos and rough notes, drafts the customer-facing report, and files it against the correct visit.
The site history is the part customers value most and businesses underestimate. When a customer can see every visit to their property over three years, with what was done and what was flagged, quoting the next job becomes straightforward for both sides. Your technician arrives knowing what was found last time. Your office stops digging through paperwork to answer questions about work done two summers ago, and the recurring issue that keeps returning is visible as a pattern rather than as a series of unrelated call-outs.
Clone the app, invite your customers, and the record is yours. Client sign-in is available on Business plans and up, $25/mo billed annually, and App Users is in beta.
Read Build a Customer Portal for the portal shell, Media upload for photos from the field, or browse service builds in the Community Gallery. Start at Taskade Genesis. Pair this with Give Clients a Booking and Scheduling Page Behind Login and Build a Client Document Library With Uploads.
Frequently Asked Questions
Can technicians update jobs from a phone?
Yes. The app works on a phone, so notes, photos, and completion status go in at the site rather than being retyped in the evening.
Do customers see technician notes?
Only the ones you publish. Keep internal notes internal and publish the customer-facing report, which an agent can draft from the raw notes.
Can customers sign off on work in the portal?
Yes. Publish the report to their page with an approval action, and the sign-off is recorded with the person and timestamp.
How does a customer see their visit history?
Their site record holds every past visit with dates, work done, and photos, so the whole history is available without a phone call to the office.
Can this handle recurring maintenance?
Yes. Set the cadence and the visits generate on schedule, each carrying its own checklist and confirmation.
What about multiple sites for one customer?
Link several sites to one account. The signed-in customer sees all their sites, and each site keeps its own history.
Does this replace my dispatch tool?
It can, or it can sit beside it. Connect your existing scheduler through the integrations and use the portal as the customer-facing layer.
What should the customer-facing report include?
What was done, anything found that needs attention, parts used, and the next recommended action. Photos alongside each point, and a sign-off action at the bottom, cover almost every service business.
