Web request Waiting
Refrigerator Not cooling since last night · model and address provided · morning preferred.
Interactive workflow demo
Job Dispatch + Work Orders
Watch incoming service requests get classified, completed with the right details, assigned by clear rules, and turned into visible work orders — including a missing address the system resolves by texting the customer back before dispatch.
Simulation mode Field Services
Three service requests arrive before the dispatcher has finished coffee.
Two requests are ready. The third is missing a service address, so the system should ask the customer for it, wait for the reply, and only then create the work order.
Watch the handoff happen
Run the workflow. The active source, decision, output, and exception will highlight together.
Ready
01
Service requests
What came in
Phone note Waiting
Dishwasher Leaking during cycle · address provided · customer available after 1 PM.
Text Waiting
Dryer Dryer tumbles but no heat. Please come today if possible. No address included.
02
Dispatch logic
How work gets completed + routed
- 01 Read refrigerator request
Capture issue, equipment, address, and preferred timing.
- 02 Create first work order
Package the complete request for the morning field queue.
- 03 Read dishwasher request
Preserve the customer’s after-1-PM availability constraint.
- 04 Create second work order
Route the request with the timing constraint attached.
- 05 Read dryer request
The appliance problem is understandable, but the request is missing the service location.
- 06 Identify the recoverable gap
An address is required for routing, but this does not need a dispatcher yet — it is a simple factual question for the customer.
- 07 Text the customer for the address
Send one specific clarification instead of handing an incomplete request to a person.
- 08 Receive the customer reply
Capture the service address and gate code from the response.
- 09 Finish the dryer work order
Merge the original dryer issue with the newly supplied location before assignment.
- 10 Publish the dispatch-ready queue
All three complete work orders move forward with the customer constraints attached.
03
0 ready Work orders + messages
What moves forward
Work order #2418 Refrigerator · morning
Issue, model, address, availability, and routing notes are packaged for the assigned technician.
Work order #2419 Dishwasher · after 1 PM
The availability constraint travels with the work order instead of living in a separate note.
Clarification text Address requested
“I can help get this scheduled. What address should the technician come to?”
Customer reply 418 Juniper Mesa Rd · gate 0314
The reply supplies the route-critical facts the original request was missing.
Work order #2420 Dryer · today
The original dryer issue and the newly supplied location are merged before assignment.
Queue status 3 dispatch-ready
All three jobs now contain the route-critical information the field team needs.
Validated results will appear here as the workflow progresses.
04
0 exceptions Clarification + audit
What happened + how the gap was resolved
Every action will be recorded here as it happens.
Follow the highlight across all four panels. The point is to show exactly where information moves, where rules apply, and where a human still owns the judgment call.
The point is the handoff, not the shiny robot
What actually changes
The automation is useful because the work moves cleanly from request to action — with less manual handling and clear human boundaries.
Before Manual handoffs
- Requests arrive through multiple channels
- Dispatch retypes details into work orders
- Missing fields trigger callbacks or incomplete jobs
- Technicians can receive assignments without route-critical context
After Connected handoffs
- Requests are checked for dispatch-critical fields
- Complete jobs become structured work orders automatically
- Simple missing details can be requested directly from the customer
- Jobs enter the field queue only after the information required to route them is present
MethodMade Studio
What does your dispatcher have to chase down?
MethodMade can connect intake, clarification, work-order creation, scheduling, and status around the tools your field team already uses.
Keep exploring
See another handoff in action.
Different problem, same idea: make the work visible, connect the handoffs, and keep judgment with a person when it matters.
Next up in the showroomBack office
Browse the showroomSwipe, drag, use ← →, or tab into a card.
1 / 16