The office can live in threads. The field cannot. A crew member on a driveway does not need another chat to babysit. They need today’s job, a map, a status they can update, and a way to close it that the customer will hear about.
The usual workaround is a forward. A screenshot of WhatsApp. A pin in a group. A voice note that says “unit 4, I think.” That is not a brief. It is how the worst version of the request reaches the person who has to knock.
The Crew App is the other side of field service requests start in chat. The company owns the conversation. The field owns the visit. Those are different jobs. Mixing them is how you get a second inbox in the van.
A second inbox in the van also wrecks close. The customer writes the office. The crew writes the owner. The group writes itself. Three “done” stories, none of them the record. The job record exists so there is one close, then one notification.
The job record is what the field sees. So the desk still owns the quality.
What the field actually needs
Today’s work. Not the whole workspace. Not Insights. Not a customer’s three-week thread. The job in front of them.
On the phone that usually means:
- Site, including the unit, the gate, the “around the back.”
- Window, the one a person approved, not a time a model invented.
- Notes the desk decided were safe to send.
- A map that opens without a scavenger hunt.
- Status they can update without writing a paragraph.
- A checklist that matches the service you sell.
- Photos and a signature when the visit needs them.
- A complete action that tells the customer it is done.
That list is boring on purpose. Boring is how a driveway goes well. The Crew App is a phone PWA for that list. No store install. Browser title is WhatTheJob · Crew. The installed name is WTJ Crew. Crew members do not sign up themselves. The company adds them.
There is no portal for the end customer. They already wrote or called. When the crew marks it done, the customer is told on the channel they already used.
Why a forwarded chat fails
A screenshot looks complete and is not. It crops the shutoff note. It hides the second address. It arrives after the customer already changed the window. The crew member is now the person who has to reconcile three stories while standing in a doorway.
A group chat is worse. It mixes five jobs, two jokes, and a parts question. Status lives in whoever posted last. Complete means a photo in the group, a voice note, or nothing. Nobody tells the customer. The office finds out when the customer writes “are you coming” on the original thread.
The job record exists so the field is not the system of record. The desk writes the brief. The field executes it. If the brief is wrong, that is a desk problem you can fix. If the brief is a screenshot, it is a fog.
Features is the office side of the same record: list, board, calendar, the job you assign. The field surface is smaller on purpose. A crew member should not have to become a dispatcher to finish the visit.
Smaller is not poorer. The job should be complete: site, window, notes, checklist. Smaller means fewer places to get lost. The office can keep exceptions. The driveway should not. If the crew member has to ask “which job was that pin,” the record failed before they parked.
Assign is still a person
You pick the crew member and the window. The model drafts the request. It does not send anyone.
That sentence is the same gate as AI drafts the field job. You still approve it, pointed at the field. Autonomous assign is how you get the wrong person at the wrong site with the wrong checklist. A person still decides who goes.
The job the crew opens should already be a job. Convert happened. Assign happened. The driveway is not the place to discover this was still a conversation.
If something changes, the desk updates the record. The field sees the job, not a new screenshot. If the crew needs a person, they have a path that is not “text the owner’s personal WhatsApp and hope.”
Close is part of the product
Done is not a vibe. Done is a close the company can stand behind.
The crew member finishes the checklist. They add the notes and photos the visit needs. They take a signature when you require one. They mark it complete. The customer is notified that it is done.
An optional short survey can run on that same phone. It never blocks completion. Loyalty points are a separate switch, off until you turn them on. Neither survey nor points is the product. The product is a finished visit that started as a sentence.
If close lives in a group chat, the customer does not hear it. The office cannot see it. Insights cannot count it. The week looks busier than it was, or quieter than it was, depending on who remembered to post.
A visit that started as a sentence
Composite, not a case study. The customer wrote: “AC stopped. 24 King Street, unit 4. Tomorrow afternoon. Shutoff in the hall closet.” A person converted and assigned. The crew member opens the Crew App in the morning.
They see today’s jobs, not the inbox. They open this one. Address, unit, window, closet note, checklist for AC repair. They navigate. They update status. They finish the visit. They photograph the work. They complete.
The customer is told it is done, on WhatsApp, because that is where they wrote. They are not asked to download anything. They are not asked to rate the bot. If you turned the survey on, it is short and on the same device the crew already held.
Change the channel and the field half stays. Email in, same job record out. A call that became a thread, same close. The crew never needed the original inbox.
What the company adds, and what the crew never sees
The company adds crew members. They do not sign up on this site. They do not get a public registration. They get an installable phone surface for the jobs you assign.
They never see the whole workspace. They never see Insights. They never see another crew member’s full day unless you designed the record that way. They never see the customer’s original inbox as a second chat to babysit.
That is not a slight. It is how you keep the driveway simple. The desk can live in exceptions. The field should live in today’s jobs.
If a crew member needs a person, that path should be obvious and short. It should not be “find the owner’s personal WhatsApp and become the new hop.” The hop is what intake was supposed to delete.
Photos and signatures belong on the job because the job is the record. They do not belong in a group that also has Saturday jokes. When something goes wrong next month, you want the visit, not an archaeology project.
Phone, not a store listing
The Crew App is a PWA. The crew member opens it on the phone they already have. No store listing to approve. No “download our field app” campaign as the onboarding.
Installed name is WTJ Crew. Browser title is WhatTheJob · Crew. Those labels are for the home screen. In sentences we still say Crew App.
If the phone is offline on a driveway, the visit still has to be finishable in a way you can stand behind when they are back. The product is not a live stream of the office thread. It is the job you already approved.
A store listing would add a week of “which app” and a login the company does not control. The PWA keeps install on the company’s side. You add the crew member. They open today’s work. That is the whole onboarding story we will tell in this note.
What this is not
This is not a second WhatsApp for the van. This is not a workforce tracker dressed as care. This is not a store app the crew has to find. This is not a customer portal.
In-product we say crew, crew member, Crew App. We do not call people resources. We do not ask them to babysit the office thread.
The desk still owns quality. If the job record is thin, the visit will be thin. Intake and the human gate are how you stop sending thin records.
A thin record looks like a name and a pin. A usable record looks like unit 4, afternoon window, closet shutoff, AC repair checklist. The crew member should not have to phone the office to reconstruct the brief. If they do, the hop is still there. It just moved into the driveway.
Contact sales if you want to walk assign and the Crew App after we have walked the inbox. The driveway is where the week becomes true.
Walk it in this order on purpose. Inbox first, so the brief is a company record. Gate second, so a person stood behind the job. Field third, so the crew member is not reconstructing a screenshot. If we start on the phone tile, we will compliment a PWA and miss the hop that still sits in the office.
Questions
No. The Crew App is a phone PWA. Today’s jobs, status, maps, checklist, photos, and signature. Assigned by the company. Crew members do not sign up themselves.
No. They get the job record: site, window, notes, checklist. The desk still owns the quality of that record. A forwarded screenshot is not a brief.
A person. You pick the crew member and the window from the jobs list, board, or calendar. The model drafts the request. It does not send anyone.
The crew member closes it on the phone, notes, photos, checklist, signature. The customer is notified that it is done. An optional survey can run on that same device. Loyalty is a separate, off-by-default switch.