Let teams mark “no buyer agent” and “no listing agent” on work orders and scheduling—with a clear trail in client records

Objective

Provide an explicit, durable signal when a job truly has no buyer-side agent and/or no listing-side agent so automations, QA, and downstream CRM pushes do not treat intentional blanks as data errors.

Background

• Silent blanks currently force teams to guess whether information is missing or intentionally absent, which breaks handoffs to integrations that expect structured contacts.
• People records on inspections continue to flow through attik-backend/src/routes/inspection.ts, while contact-centric automations (for example buyer/listing identification) also touch helpers such as attik-backend/src/util/functions/actionFlows/sendBlippReviewRequest.ts.
• Scheduling and work order UIs share the same people editor components as the internal quote experience, so any new flags need consistent behavior across booking surfaces.

Scope

Frontend

• Add controls in scheduling and work order flows that set the explicit “no agent” states while keeping the audit story visible in contact panels and history.

Backend

• Persist the new semantics on inspection or people entries, and ensure APIs + integrations respect the flag instead of emitting validation errors.

References

• attik-backend/src/routes/inspection.ts
• attik-backend/src/util/functions/actionFlows/sendBlippReviewRequest.ts

Transcript notes (Apr 16 feature sync)

• This was called out as one of Southeast's more important active workflow needs because they are already operating with these profiles and working around the gap manually.
• The transcript adds downstream nuance beyond the UI flag itself: teams need intentional blanks to be understood by QA and CRM/integration workflows rather than being treated as missing data.
• There was also discussion that invoice and HubSpot-related handling currently depends on clean interpretation of these cases, so the explicit no-agent signal should help reduce manual reconciliation and false error handling.