Skip to main content

Work orders, status, and assignment

Use Requests to see what needs attention and who is responsible. The workspace heading is Work Orders. Choose the correct business first, then select Services, Rentals, Stints, or Menus: each order type has its own records and fulfillment actions.

The example follows a drain-cleaning job at Maple Plumbing Co. A dispatcher finds it without an assignee, reviews the visit instructions, and gives it an owner. Assignment answers who is responsible; status answers where the work stands. Neither replaces the customer's requested timing or a scheduled shift.

Job Status​

Find the work that needs attention​

  1. Open Requests → Services.
  2. Choose Requested, Active, Completed, or Cancelled.
  3. Select List to scan jobs or Form to review their form-based presentation.
  4. Use the search field to narrow the results. Open Filter for dates, service, submitted form variables where present, and visibility.
  5. Combine the status with Everyone, Assigned to me, or Unassigned.
  6. Open the matching work order and inspect the submitted information before acting.
Services work orders with Active and Unassigned selected and a populated Drain Cleaning result
Active work can still be unassigned. This saved example appeared in Unassigned after its assignee was removed; its original assignment was restored after the walkthrough.
Services work orders with Active and Unassigned selected and a populated Drain Cleaning result

Active work can still be unassigned. This saved example appeared in Unassigned after its assignee was removed; its original assignment was restored after the walkthrough.

A count on a status tab and the filtered rows answer different questions. The example has three active service jobs, while the additional Unassigned filter leaves one visible result. Clear the service, date, assignment, and visibility filters before treating a missing row as a missing order.

Form-answer filters depend on the selected service and the answers actually stored with its orders. In this example the service filter worked, but the drawer reported no filterable variables for the inspected service. It did not produce a populated answer-filter example.

Update the operational stage​

Open a service order and use its available status action. Accept moves a requested job into active work. Completed is an action for finishing an active job; seeing that button does not mean the job is already complete. Decline has a confirmation explaining that the request moves to Cancelled.

Check the order identity and the current stage before selecting an action. Acceptance and completion can initiate customer email updates. A status change does not itself collect payment or prove that an invoice is paid.

The Requests workspace also supports status changes for selected rows. Review the selected jobs and destination together. Its Undo window can reverse the local move before the delayed write; do not assume the same Undo behavior applies to every action on an individual order page.

The walkthrough inspected three active service jobs and one completed job, along with the detail-page controls. It did not accept, complete, decline, or bulk-move jobs, so it does not demonstrate a delivered status email. Rentals, Stints, and Menus have their own lifecycle controls; follow the relevant Rentals, Stints, or Menus guide instead of applying service-specific steps to them.

Work Order Assignment​

Owners and managers can assign active app-account team members. A terminal-only employee does not become an assignable app user simply by appearing in the staff roster. See Team for membership and access setup.

  1. Open the work order and select Details.
  2. Open the Assigned to picker.
  3. Select one or more team members, or deselect a member to remove them.
  4. Choose Done to close the picker and save changes. Check the success or error message.
  5. Return to Requests and use Assigned to me or Unassigned to confirm the result.

Changes are saved when the picker closes. Newly added people other than yourself can receive an assignment notification. Removing someone does not send the same new-assignment notice. Assignment is therefore an operational change, not a harmless preview of a staffing plan.

In the example, removing the signed-in owner put Drain Cleaning into Unassigned after a full reload. Re-adding that same owner restored the assigned result. No other team member was added or notified. Multi-person assignment and another person's notification delivery were confirmed in the implementation, rather than exercised in this walkthrough.

Members with access restricted to assigned work see only their permitted jobs. Assignment does not grant management rights or make an otherwise inaccessible business available. If someone is absent from the picker, check their active membership and app-account access before creating another staff record.

Put the job on a shift​

Choose Schedule shift to open the team schedule with work-order context. The first assignee and an available job date can prefill the scheduling handoff. Review the person, date, times, and draft before saving or publishing. An assignee alone is not a booked shift. See Shifts for draft schedules, publication, and time records.

Customer Updates​

Choose the channel according to who needs the information. A saved visit note, a customer conversation, a team conversation, and a status email serve different purposes.

Save instructions for the job​

Open Details → Notes, write the operational instructions, and choose Save Notes. Reopen the order to verify the saved text before relying on it during a visit.

Saved drain-camera visit instructions covering the cleanout inspection, laundry access, rear entrance, and existing repair context
The visit plan survived reopening the work order. Saving these notes did not send a customer message or change the job status.
Saved drain-camera visit instructions covering the cleanout inspection, laundry access, rear entrance, and existing repair context

The visit plan survived reopening the work order. Saving these notes did not send a customer message or change the job status.

Keep the next action concrete: what to inspect, the access arrangement, and any restriction on the visit. Do not treat Save Notes as evidence that the customer received an update. Use Forms for structured answers and customer notes for standing context that applies across jobs.

Use the correct conversation audience​

The Chat area separates Customer and Team only. Check the audience before composing. When no conversation is linked, the panel offers a start-conversation action; the presence of this action does not prove that chat has been enabled for the deployment or that a customer account has been linked successfully.

Customer conversations require a verified linked customer account and an available chat service. Team-only conversations are for internal coordination. If the service cannot connect, follow the displayed error and retry after the connection issue is resolved. Do not assume a message was sent because the panel opened.

The walkthrough inspected the audience choices and start-conversation state without creating a conversation or sending a message. It therefore does not demonstrate customer receipt, a chat reply, or attachment delivery.

Check status emails and notifications separately​

Service-request creation, acceptance, and completion have email-event support. Quote and invoice communications also have their own actions and delivery states; see Invoices and quotes. Delivery still depends on the recipient details and email service. A saved operational status is not a delivery receipt.

Notifications shows notifications for this work order addressed to the signed-in user. It is not a complete customer email history. Send queued emails is an explicit delivery action, not a read-only refresh. Use it only after checking the order and recipient context, particularly when investigating a possible duplicate update. It was not invoked in the walkthrough.

Troubleshooting​

  • An order disappeared: confirm the business, order type, status, and all filters. Check assignment-based access with a manager.
  • The header says “Filled a work order request” on an active job: use the actual status badge and available action. That header description alone is not the lifecycle stage.
  • A team member is missing: check active membership and app-account access. Terminal-only staff are not equivalent to assignable app users.
  • Assignment did not save: inspect the error, reopen the picker, and confirm the saved selection. Only owners and managers can change it.
  • Notes changed but no customer received them: saving notes is not sending a message. Choose the correct customer-update channel.
  • Notifications is empty: it only shows matching notifications for the current user; emptiness does not establish whether an email was delivered.
  • A job has an assignee but no shift: use Schedule shift and review the schedule. Assignment and scheduled time are separate records.

Continue with Customers, Calendar, Shifts, Expenses, and Invoices for the records around the job.

Find jobs as the list grows​

Requests now filters and pages work orders on the server for the selected business. Set the status, search and assignment filters before interpreting the board. More results load as you scroll; the initially visible cards are not necessarily the whole result set.

If a job appears missing, check the active business, filters and your assigned-work access first. A completed status change should update its counts and placement. Read the available Undo action promptly if you moved the wrong job; navigating between tabs is not a reason to submit the same change again.

Edit a placed order with customer approval​

For a supported work order, use Edit details to revise editable form answers. For example, correct a requested room count or arrival instruction after discussing it with the customer.

  1. Open the correct work order and choose Edit details.
  2. Change the offered fields and add a note explaining the revision.
  3. Read the final action. Send for approval leaves the edit pending for the customer; Save changes applies directly when the flow permits that mode.
  4. Review the before/after values and pending state on the order.
  5. While an edit is pending, Edit again starts from that pending proposal and sending replaces it. Withdraw removes the pending proposal.
  6. Check the customer's decision. A declined proposal does not become the saved answer; a later approved revision supersedes that earlier decline.

Files, signatures and place fields are not editable through this answer editor. Editing answers is also separate from changing an invoice, collecting more money or rescheduling a shift. Check each affected operational record after approval.

These controls were reviewed in the implementation. No customer proposal, approval email or live order edit was sent for this documentation refresh. Customers can follow Orders for their side of the review.