Blueprint / Scheduling and field work

Work order

Not shown in the Loom recording.

Why this block matters
  • Not shown in the Loom recording.
Areas in this block:
Not shown in the Loom recording.

How Well We Know This Block

A person sets it on a 5-step scale. Click a step to set it as Ivan (mock sign-in, top right).

1
Not Explored
Nobody looked into this block yet.
2
First Look
Someone read the vendors’ public pages for it once.
3
Vendors Compared
We know how each of the 4 vendors does it.
4
Plan Drafted
Our CRM plan for the block is written. Open points remain.
5
Full Clarity
We agree how we build it. No open points remain.
Now: Not Explored. Set by Ivan, 2026-10-28 07:08 UTC (mock).
Now: Not Explored. Set by Ivan, 2026-10-28 07:08 UTC (mock).
Now: First Look. Set by Ivan (mock).
Now: Vendors Compared. Set by Ivan (mock).
Now: Plan Drafted. Set by Ivan (mock).
Now: Full Clarity. Set by Ivan, 2026-10-28 07:12 UTC (mock).
Earlier settings (1)Earlier settings (1)Earlier settingsEarlier settingsEarlier settingsEarlier settings (4)
Not shown in the Loom recording.
1
Step 1

Our CRM and the 4 Vendors

One tab each, same layout. The number counts the lines, terms and notes in a tab.
FieldRoutes in Work order

FieldRoutes calls it: Appointment, Completion Info

From a read-only look at the FieldRoutes account on 2026-11-02 and its official manuals. Each line ends with its evidence: Observed in the account, Documented in a manual, or not tested. Capture numbers link to the screen below. All of FieldRoutes across the 20 blocks

In FieldRoutes the work order is not a separate document. It is the appointment itself: the visit record on the Customer Card holds a Completion Info block (technician, time on site, serviced interior) and the follow-up outputs (service notification, follow-up email, mail). Only one pending visit was opened, and it showed no notes, images or checklist answers. That these attach to the appointment is an inference from Customer Search columns (Appointment Notes, Appt Checklist Data) and the Employees with Images Saved audit, not something seen on a visit record. Technicians complete visits in the mobile app, so most of this block is shaped by Admin settings: Appointment Checklists, Mobile Default Settings (completion gates), Preset Notes, Diagram Markers, custom appointment fields and Form Templates. The research covered 34 screenshots here (11 placed here and 23 from other blocks). They show the settings pages, one pending appointment, the Customer Search appointment filters, completion-related reports and dashboard help. No visit was completed, no checklist was filled in, nothing was signed and the mobile app was never run as a technician, so the field side is configuration only.

In short

  • The visit record is the appointment. Its Completion Info shows technician, Time On Site and Serviced Interior. On the one opened pending visit these were placeholders (No Tech Assigned, 12:00 am - 12:00 am, No), not real work data (Observed, 448-customer-appointment-detail).
  • Appointment Checklists are the field checklist tool. The UI says they show to technicians in the mobile app before start or before completion. They can be required, need a signed agreement first, and need final approval by the technician or the customer. Each section is acknowledged by Initials or Single Tap (Observed as configuration, 151-settings-appointment-checklist-form). Runtime enforcement was not tested.
  • Completion can be blocked by office policy. The Mobile Service defaults include Block Completion if There is Balance, Require Products to Complete Appt, Require Interior Serviced Selection and Require Scanned Equipment Last Four Digit Confirmation (Observed as configuration, 183-mobile-service-default-editor). None of these gates was run.
  • FieldRoutes keeps two times on site. Reported time is what the technician enters, and the technician can adjust it in the app. Actual time is logged when the technician clicks check-in / check-out. The Average Time On Site report compares the two (Observed help text, 067-report-average-time-on-site).
  • Completion feeds customer output. A Service Follow-up Email, a separate block for incomplete services and caution statements are configured as Customer Communication groups (Observed, 300-communication-section-19-editor). The appointment has Print Notification, Send Follow-up Email and Send Mail buttons (448-customer-appointment-detail).
  • The research did not prove signatures, photos, offline work, checklist enforcement or edits after completion. The assessment rates field execution evidence as low for technician runtime (assessment).

Screens: 11 captures

Upload a screen

Each capture is a saved screen state from the FieldRoutes account on 2026-11-02. A screen shows what controls exist; it does not prove what happens when they are used.

Their words for this block 20

Appointment: The visit record. It is also the work order: completion data and outputs sit on it; notes and checklist answers are inferred to attach to it (see How it works). Observed, 448-customer-appointment-detail
Completion Info: Block on the appointment with Technician, Time On Site and Serviced Interior. Observed, 448-customer-appointment-detail
Time On Site: Reported vs Actual: Reported = entered by the tech, who can optionally adjust it in the app. Actual = logged at check-in / check-out. Help text says they can differ if the tech fills in data later (phone died, no service), forgets to check in or out, or is "pretending to be somewhere he is not". Observed help, 067-report-average-time-on-site
Serviced Interior: Recorded yes/no on whether the interior was serviced. It is not customer access permission. Observed, 448-customer-appointment-detail, 420-service-appointment-filters-lower
Appointment Checklist: Configured list of acknowledgements shown to technicians in the mobile app, before start or before completion. Observed (UI text), 150-settings-appointment-checklists
Acknowledgement Type: Initials / Single Tap: How each checklist section is confirmed. This is not a full signature. Observed, 152-settings-checklist-section
Final Checklist Approval By: None / Technician / Customer: who gives the final acknowledgement. Observed, 151-settings-appointment-checklist-form
Completed By / Serviced By: Two separate staff attribution filters on appointments. The UI does not explain which event sets which. Observed, 417-service-appointment-filters
Tech Completion Notes: Notes technicians write when completing a service. They have their own report. Observed, 101-report-tech-completion-notes
Default Completion Notes: Reusable completion text set on the Service Type. Observed, 540-service-type-editor-clear
Preset Notes: Reusable note texts. Each one is enabled separately as a Service, Invoice or Office note for Residential, Commercial, Multi-Unit and Structure properties. Observed, 193-mobile-preset-note-form
Service Notification: The visit output document. It is printed from the appointment, listed in the Service Notification Report and optionally printed with route sheets. Notifications pending approval are excluded from route sheet printing. Observed, 448-customer-appointment-detail, 520-daily-route-print-options
Service Follow-up Email: Email sent after a service, with technician, property and date placeholders. Its timing is set in a separate preferences group. Observed, 300-communication-section-19-editor
Incomplete Services: Service types inside a completed appointment that were not completed or were no-shows. They get their own follow-up email section. Observed, 301-communication-section-20-editor
Caution Statements: Rich text shown above the billing summary on service notifications and in follow-up emails. The existing wording does not prove safety compliance. Observed, 302-communication-section-21-editor
Diagram Marker: Reusable symbol (code, description, notes, icon) for site diagrams. Icon names such as Delete or Cancel are picture choices, not actions. Observed, 188-mobile-diagram-marker-form, 189-mobile-diagram-marker-icons
Custom Appointment Details / Custom Appointment Unit Details: Groups of extra custom fields at visit level and at unit level (multi-unit). Observed (name-only group dialog), 161-settings-custom-appointment-details, 163-settings-custom-unit-details
Form Template / Completion Letter: Signable document definition with an optional rich-text completion letter. False friend: a Form is not a Contract (see below). Observed, 327-form-template-editor; Documented, Contracts vs Forms manual
Reservice: Return visit (call-back). It can be chosen as the visit association on an appointment, and Tech Re-services ties it to the technician of the earlier service. Observed, 448-customer-appointment-detail, 102-report-tech-reservices
Employee Signature: Signature pad on the staff user card. It is separate from customer agreement signatures. Observed, 552-owned-user-picture

Where it lives in FieldRoutes

Menus, pages and settings where this block appears 17 menu paths

Connections to other blocks

How FieldRoutes does it

Visit completion record (observed state only). The Appointments tab lists visits by service type, date and status. The opened pending visit shows Edit and Cancel, who scheduled it and when, and a Subscription selector (a subscription, or Stand-Alone Service or Reservice). Completion Info has a disabled Technician selector (No Tech Assigned), Time On Site 12:00 am - 12:00 am and Serviced Interior No. Print Notification, Send Follow-up Email and Send Mail are visible. Service Notification Report and History are separate entries on the tab. None was used. These values are a pending visit's display, not worked time or a completed interior service (448-customer-appointment-detail, customer populated findings).

Checklist during a visit (configured, runtime untested). An office admin binds a checklist to a Service Type. The admin sets when it shows (Prior to Start / Before Completion), whether it is required, whether a signed agreement is required, whether it applies to Only Initial or All Appointments, who gives final approval (None / Technician / Customer) and which subscription flags exclude it. The admin can add an introductory paragraph. Each section needs a field acknowledgement (Initials or Single Tap) with optional title and text and placeholders for customer, agreement, service and pricing data. The UI says checklists display to technicians in the mobile app to capture additional customer signatures or technician acknowledgement of operational steps. Actual display, signature capture, enforcement and stored proof were not tested (151-settings-appointment-checklist-form, 152-settings-checklist-section, admin findings). Customer Search can later filter or show Appt Checklist Data: name, Required, When to Display on Mobile App, Display During Appointments, Customer Accepts Via, Checklist Acknowledged, Acknowledged On. This suggests acknowledgements are stored per appointment, but no real acknowledgement was seen (420-service-appointment-filters-lower). The Sales Service Report legend marks a "completed welcome checklist" with a caret (Observed, sales controls).

Completion gates (configured, untested). Mobile Service defaults can block completion when the customer has a balance (No / Yes / Residential Only / Commercial Only). They can also require products to be recorded, require an Interior Serviced selection and require confirmation of the last four digits of scanned equipment. Tech Collection Auto Apply applies a cash or check collection on the completed visit. It replaces the prior applied payment if the collection changes, and it requires the Apply Payments permission (tooltip). Max Over Collect, Enforce Payment Hold Date and Enforce Max Monthly Charge also apply to field collection. None of these was exercised in a live mobile workflow (183-mobile-service-default-editor). The Access Control profile has "Complete appointment when period is locked" and the Mobile permission "Mark Equipment as Manually Inspected", which allows inspection without a scan (Observed, admin controls).

Time on site (documented in help, no data). The Average Time On Site By Tech report uses only appointments completed in the date range. It groups them by technician and by planned appointment duration, so actual time can be compared with how long the tech was supposed to be there. Columns: office, tech ID, tech name, stops, appointment duration, average reported time and difference, average actual time and difference. The captured day had no data (067-report-average-time-on-site).

After the visit: customer output (configured, nothing sent). The Service Follow-up Email carries technician, property and date placeholders. A Service Follow-up Email Incomplete Services subsection covers uncompleted or no-show service types inside a completed appointment. Caution Statements appear above the service notification's billing summary and in follow-up emails. The first preference group sets follow-up timing (manual or approval-driven, or completion and delay-driven). A Follow-up PDF Attachment upload sits outside the numbered groups and was not used (300-communication-section-19-editor, 301-communication-section-20-editor, 302-communication-section-21-editor, admin controls, admin findings). The Service Type sets Send Followup Emails and Attach Follow-up Invoice Details. Per tooltip, the latter attaches invoice and service-notification PDFs to follow-up communication (540-service-type-editor-clear).

Bulk completion and route sheets (menu only). Route Actions on a day's route card offers Complete Entire Route (and Cancel Entire Route). Its invoice and notification effects are unknown and it was not used (516-daily-route-actions). Print Options for route sheets offers Route Sheet style None / Compact / Default / Expanded, Separate groups, Print Service Notifications (pending-approval notices excluded), Only customers without email / Only customers who prefer paper, Include Overbooked Services (checked) and a Technicians multi-select. The dialog was canceled without printing (520-daily-route-print-options).

Forms and signatures (documented, untested). Form Templates hold signable documents (existing rows include NPMA forms) with Page Size, Requires Approval, HTML content, a Completion Letter and signature placeholders for customer and employee. The official Contracts vs Forms manual says Custom Forms give up some automatic service, pricing and schedule fields that Contracts fill in. Classic signature fields can reuse one signature, while inline Contract occurrences each need completion. Forms need separate signature blocks, with employee signatures first. Mobile-uploaded diagrams and images can populate Forms, but equivalent technician upload is not documented for Contracts (Documented). Nothing was completed, approved, signed or sent (327-form-template-editor, official manual findings). Form Lookup (Reporting) lists forms by Date Added, Date Signed, Form State, Form Type and Created By. It rendered empty (reporting findings).

En-route message (configured, disabled). On My Way sends technician-triggered customer messages when the technician travels to an appointment. Live Technician View lets the customer see the technician's proximity. The page says SMS configuration is required, technicians must allow app location access, and Customer Portal is required for Live Technician View only. The captured page reports SMS configured and the portal on, yet both checkboxes and Save are disabled for an unexplained reason. Message placeholders cover customer, ETA, office, service, address, technician and live-view link. Nothing was sent (184-mobile-on-my-way).

Settings and controls

All settings and controls seen 59 rows

Appointment Checklists (150-settings-appointment-checklists, 151-settings-appointment-checklist-form, 152-settings-checklist-section)

ControlPurpose and limit
Filter by Name / GlobalFind a checklist by name and office scope
+ Add New ChecklistOpen the definition
Columns: Checklist Name / Service Type / No. of Sections / Global/OfficeOverview (no rows in the account)
Global / Checklist NameScope and identity
Service Type to Display ChecklistBinds the checklist to a service type
When to Display: Prior to Start / Before CompletionVisit stage where it appears
Checklist Required? Yes/NoMandatory completion; enforcement untested
Signed Agreement Required? Yes/NoAgreement prerequisite; exact rule untested
Appointment Types: Only Initial / All AppointmentsScope by visit kind
Final Checklist Approval By: None / Technician / CustomerFinal acknowledging party
Exclude Subscription FlagsExclude flagged subscriptions; no options in the account
Introductory ParagraphOptional, max 150 characters
+ Add Additional SectionAdds an acknowledgement section
Insert Placeholder selectorsCustomer identity, address, contact, agreement length, initial/recurring quote, sales rep, service name, initial subtotal
Checklist Section TitleOptional, max 50 characters
Acknowledgement Type: Initials / Single TapHow the section is confirmed
Additional paragraph/sentenceSection text, max 250 characters
Save / CancelNot executed

Mobile Service defaults that gate or shape completion (181-mobile-default-settings, 183-mobile-service-default-editor). The values shown are this account's settings, not product defaults.

ControlPurpose and limit
Tech Look Ahead / Look Back DaysMobile history and future window; data access limits untested
Block Completion if There is BalanceNo / Yes / Residential Only / Commercial Only
Max Over CollectCollection limit; unit and enforcement unverified
Enforce Payment Hold Date / Enforce Max Monthly ChargePayment constraint toggles
Technician Push NotificationsStaff notification toggle
Require Products to Complete ApptProduct record needed before completion
Enable ReschedulingTechnician can move the visit
Tech Collection Auto ApplyApplies cash/check on the completed visit; needs Apply Payments permission
Require Interior Serviced SelectionMandatory interior status
Require Scanned Equipment Last Four Digit ConfirmationExtra scan confirmation

The Sales side of the same page (map code, flexibility, default services, payment and agreement prerequisites, contract-signed alert, default source, nearby distance, earliest spot) belongs to Mobile app and Scheduling and appointments.

Field dictionaries (192-mobile-preset-notes, 193-mobile-preset-note-form, 187-mobile-diagram-markers, 188-mobile-diagram-marker-form, 189-mobile-diagram-marker-icons, 194-mobile-spray-rigs, 195-mobile-spray-rig-form)

  • Preset Notes: Global, Search, + Preset Note; Preset Description (required), Notes (required), office scope; Toggle On / Toggle Off (bulk; exact set untested); twelve checkboxes, Residential / Commercial / Multi-Unit / Structure by Service Notes / Invoice Notes / Office Notes, all checked on a new form; save / cancel.
  • Diagram Markers: Global, Search, + Diagram Marker; Marker Code (required), Marker Description (required), Marker Notes; Most Used / Not Most Used (app ordering untested); office scope; Icon Image chooser (pest, treatment, finding and interface symbols); "Show tech name and license # on diagram" (tooltip: always show the viewing user's name and license; not toggled); save / cancel. Actual diagram drawing and output were not tested.
  • Spray Rigs: Visibility, Search, + Spray Rig; Spray Rig Description (required), Spray Rig License Number (required), visibility. No assignment to a technician, vehicle or chemical use was seen. See Chemical use and state reporting.

Custom fields on the visit (161-settings-custom-appointment-details, 162-settings-custom-appointment-group, 163-settings-custom-unit-details, 164-settings-custom-unit-group)

  • Custom Appointment Details and Custom Appointment Unit Details: Global, Visibility, Search, empty table, + New Group of Custom Fields; Group Name, cancel, save. The field editor appears only after saving a group, so field types, validation, requiredness and mobile rendering were not seen.

Customer Communication groups tied to completion (300-communication-section-19-editor, 301-communication-section-20-editor, 302-communication-section-21-editor)

GroupContent
19 Service Follow-up EmailRich text with technician, property and date variables; timing set in group 0
20 Service Follow-up Email Incomplete ServicesRich-text subsection for uncompleted or no-show service types
21 Service Notification Notes / Caution StatementsRich-text caution above the notification billing summary and in follow-up emails
Follow-up PDF AttachmentChoose File / Upload / reference link; not uploaded

Form Templates (326-form-templates, 327-form-template-editor, 328-form-template-html)

  • List: Global filter, Visibility, Search, + Form Template, edit; columns Name, Page Size, Signature Requirement, Requires Approval, Global, Visible.
  • Editor: Name (required); Page Size Letter / Legal (Legal preselected); Requires Approval No / Yes; office scope; Hidden / Visible; save / cancel / html; Choose File; Placeholders in Use; iframe preview; read-only Stylesheet; Completion Letter rich text (Format, Bold, Italic, Strikethrough, Lists, Link, Line); HTML content, preview, delete; a notice that base64 images over 200KB will not be saved; Form Content Placeholder Key (office, customer, bill-to, unit, date variables and customer/employee signature-field markup).
  • The list shows Signature Requirement as a column, but the new editor has no separate selector for it.

Skip Reasons (346-skip-reasons, 347-skip-reason-editor): Global, Visibility, System, Search, + Skip Reason; Skip Reason (required), office scope, Hidden / Visible, System No. The system reasons Auto-Skipped, Prepay Upsell and Unspecified have no edit control. The consequences of a skip were not exercised.

Appointment Reservice Reasons (155-settings-reservice-reasons): scope, visibility and System filters, search; the editor needs a Reservice Reason.

Route sheet Print Options (520-daily-route-print-options): Route Sheet None (selected) / Compact / Default / Expanded Style; Separate groups (unchecked); Print Service Notifications (unchecked; pending-approval excluded); Only customers without email / Only customers who prefer paper (unchecked); Include Overbooked Services (checked; output inclusion, not permission to overbook); Technicians multi-select (Office, Tech and Sales labels); Print / Cancel / close.

Customer Search, Service Appointment filters on completion (417-service-appointment-filters, 418-service-appointment-filters-middle, 420-service-appointment-filters-lower)

  • Scheduled By / Completed By / Serviced By (separate; the technician selector holds more than technician-role accounts).
  • Status: Pending, Completed, Not Serviced, Canceled, Rescheduled, Auto-Skip, Skipped, Opted-Out.
  • Feedback Rating (seven comparisons, number of stars).
  • Show Tech Notes No / Yes (report display, not a new note).
  • Serviced Interior: N/A / Include / Exclude / Only Serviced Interiors.
  • Images Uploaded: N/A / Include Appts With or Without Uploaded Images / Only Without / Only With.
  • Appt Checklist Data: Appointment Checklist Name, Required, When to Display on Mobile App, Display During Appointments, Customer Accepts Via, Checklist Acknowledged, Acknowledged On.
  • Appt Custom Fields / Unit Custom Fields (empty options).
  • Target Issues / Excl. Target Pests; Include / Exclude Flags (Appointment Flags).

Reports about completed work

ReportControlsEvidence
Tech Completion NotesStart/End Date, Refresh, Export to CSV; result blank101-report-tech-completion-notes
Average Time On Site By TechDate, Offices, Employees, Advanced Filters (not opened), Refresh, Export to CSV, search, sortable columns067-report-average-time-on-site
Tech Re-servicesStart/End Date, Months of Historic Data (default 3), Offices, Refresh, Export to CSV; shows "Total services resulting in a reservice: 0" and empty Tech Re-service Rates and Re-services sections102-report-tech-reservices
Customer FeedbackStart/End Date, Rating (1-5 or all), Favorite, Refresh, Export to CSV; result blank075-report-customer-feedback
Audit: Employees with Images SavedShared Audit dates, Refresh, Export to CSV; 0 "Appointments", no table477-audit-employee-images
Tech CollectionsStart/End Date, include zero collected, Exclude Initial Appointments, include zero invoice/customer balances, Appointment Breakdownreporting findings
Form LookupDate Added, Date Signed, Form State, Form Type, Created By, Actions, search; emptyreporting findings

Dashboard completion metrics (vendor definitions, not checked against records)

  • Completion %: status of scheduled appointments in the period that remain on a route, excluding cancellations and reschedules. Serviced = completed, Pending = not yet completed, Not Serviced = No Show. The handling of mixed-service appointments is not stated (393-dashboard-metric-help-5).
  • Completed Meas. SF: completed measured subscriptions in the chosen dates by service type, with calendar-year wording. Outputs: Completed Services (count), Completed Meas. SF and Total Completed Meas. SF (plus add-ons) (409-dashboard-metric-help-21).
  • Completed Meas. LF: the same in linear feet: Completed Services, Completed Meas. LF, Total Completed Meas. LF. It was read from its own help dialog (411-dashboard-metric-help-23).
  • On the subscribed side, "Inactive" measurement includes skipped and opted-out services, not only inactive subscriptions. The LF help mislabels one output and refers to square footage in its last sentence (dashboard).

Staff signature (552-owned-user-picture): the Picture tab has Choose File, an Employee Signature "Sign Below" area, a signature-local Clear / Save and the whole-card Cancel / Save. Nothing was signed. The Service Type has an Employee Signature No / Yes setting whose exact use is unknown (540-service-type-editor-clear).

What the research did not prove

  • No visit was completed. Completion Info was seen only on a pending visit with placeholder values. Real time on site, serviced interior results, technician assignment on completion and edits after completion are unknown.
  • Checklist display, enforcement of "Required", the signed-agreement prerequisite, customer approval and stored proof were not tested. The checklist list was empty in the account.
  • Mobile completion gates (balance, products, interior, scan) and Tech Collection Auto Apply were not exercised. Offline work, sync, retry and conflict recovery are unknown.
  • Photo upload, signature capture, diagram drawing and marker placement were not tested. The Audit "Employees with Images Saved" panel counts "Appointments", so its meaning is unclear.
  • Custom appointment and unit fields: only the name-only group dialog was seen. Field types and mobile rendering are unknown.
  • Completed By vs Serviced By: which event sets which is not explained.
  • The Tech Completion Notes, Customer Feedback and Form Lookup results were blank. Average Time On Site and Tech Re-services showed no data for the day.
  • Complete Entire Route: invoice and notification effects are unknown and it was not used.
  • On My Way and Live Technician View are disabled for an unexplained reason.
  • The Form Templates editor has no Signature Requirement selector although the list shows one. Signature order, generated output and mobile image upload are documented only.
  • Follow-up email timing, the PDF attachment and actual delivery were not tested.

Ideas for Our CRM

Agent proposals, not decisions
  • Proposal: keep the visit record and the work order as one object, as FieldRoutes does, with a clear Completion block (technician, reported time, check-in/out time, interior, notes).
  • Proposal: store both reported and actual (check-in/out) time on site, and show the difference, since FieldRoutes treats the gap as a quality signal.
  • Proposal: make visit checklists configurable per service type with timing (before start / before completion), required flag and approval party, and store acknowledgement time per appointment.
  • Proposal: make completion gates (open balance, products recorded, interior answer, device scan) explicit office policies, each with an audited override permission.
  • Proposal: define one "completed by" and one "serviced by" meaning in writing, to avoid FieldRoutes' unexplained pair.
  • Proposal: acceptance test before choosing: a technician's full day on a supported device with poor connectivity, required checklist steps, signatures, findings, device and treatment records, and office follow-up (from the assessment's acceptance questions).

Official FieldRoutes manuals

Screenshots kept in other blocks that also matter here 23
Research sections used for this page 31

The original research reports are kept unchanged in the archive. These are the sections that speak about this block:

2
Step 2

How This Block Connects

Click a block for its vendor terms.
Scheduling andappointmentsgets a workorderInvoicing andbilling termsis invoicedasInspection reportsand auditshas formsWork orderSet to Not Explored by Ivan (mock).Set to First Look by Ivan (mock).Set to Vendors Compared by Ivan (mock).Set to Plan Drafted by Ivan (mock).Set to Full Clarity by Ivan (mock).
Solid arrow: a source shows this linkDashed arrow: our hypothesis, no source yetThe word on an arrow says what one block does to the next.
3
Step 3

Inbox: New Items for This Block

Items from Slack, uploads and agent research wait here. Accept moves an item to its place.

Add from here

Planned: post in Slack and mention the agent, and it files the post here. Today the copy of Slack keeps the text and file names only.

Upload a screen or note

Ask the agent to research

For example: how does PestPac bill a customer with 12 sites?Ask

Mock: no agent runs in this static page.

Nothing waits in this inbox.

Where this block is stored: How it works, part 2.