Clear questions.
Useful answers.

Yes. Dispatchers can search for an existing customer and property before creating new records, helping reduce duplicate household and business profiles.

ScreenOps links customers and properties to openings, measurements, configurations, documents, field work, and warranty records when those records exist.

Yes. The field flow uses large touch targets, staged data entry, attached media, and responsive layouts intended for landscape and portrait tablet use.

Yes. Configuration and estimate stages are connected so options can be adjusted before the customer accepts the work.

No. Measurements must be reviewed and confirmed by a qualified person before they drive estimating or production.

The workflow is designed to preserve measurement versions so revisions remain traceable instead of silently replacing field history.

Authorized users can revise configuration choices and present updated options. Discount, custom-price, or low-margin exceptions can require manager approval.

Estimate approval feeds the document workflow so quotes, contracts, orders, invoices, and warranty documents can use the same customer and job data.

Inquiry claims, guarded server transitions, conflict checks, and idempotent scheduling work together so multiple dispatchers cannot safely create duplicate active visits for the same inquiry.

Yes. Dispatch can assign multiple technician-role users and identify a lead technician when the work needs a crew.

Authorized managers can review team routes, while technician access is scoped to the work assigned to that user.

Ordered stops remain available in ScreenOps. Road-aware routing and in-app navigation depend on configured map, routing, and device-location services.

Production assignment is limited to users with fabricator responsibilities, while owners and authorized operations leaders can manage the queue.

Fabricators can request more information, returning the question to the technician or user responsible for the production task.

Not yet. Inventory is limited operational support for ScreenOps workflows and should not be marketed as a replacement for a mature enterprise warehouse or accounting system.

Yes, when enabled. The workflow can record usable remnants and scrap events, but companies can leave that layer off if it adds unnecessary process.

No. Inventory and procurement are operational support tools. Teams review demand and purchasing decisions instead of relying on opaque automatic purchase orders.

The receiving workflow can preserve ordered, received, and remaining quantities so the team can see what is still outstanding.

The default technician view is restricted to that user's own assigned work. Authorized managers and dispatchers can use team views.

Field Work supports installs, repairs, warranty visits, pickups, and drop-offs scheduled by Dispatch.

Employee self-service is scoped to the signed-in employee. Managers can review their team, and authorized owners can review the organization.

Workforce availability and schedule exceptions are intended to stay visible when dispatchers assign work, including when an employee is off shift.

Customer card and bank payments depend on the company's configured Stripe connection. ScreenOps platform subscription billing is a separate Mosari billing relationship.

Owners can enable supported offline payment types so staff can record the method and payment state without pretending it was processed online.

Yes. Authorized owners, managers, and leads can save their own dashboard layout and lock it when they are finished arranging cards.

No. Reporting surfaces follow role and permission boundaries so staff only receive the views their responsibilities require.

No. Owners can adapt optional handoffs, but ScreenOps preserves the core record chain and required accountability for customer, job, pricing, approval, and production decisions.

No. Assistive suggestions may help teams work faster, but people remain responsible for pricing, measurement approval, purchasing, production, and accounting decisions.

Settings includes QuickBooks Online, ScreenOps Payments / Stripe, customer email, transactional SMS, a Slack workspace redirect, and DocuSign. These are configuration options; provider approval, plan access, and a completed connection are required for the related service.

No. External Google and Outlook calendar OAuth are not included in the current public product claim.

Yes. Openings can retain their own location, dimensions, photos, configuration, and measurement history within the customer property.

Approved work can carry opening specifications into production and material-readiness workflows when the company uses in-shop fabrication.

Yes. The job record can distinguish replacement, repair, and installation scope while preserving the opening and service history.

Door configuration, notes, photos, and selected hardware can remain connected to estimating, production, and field work.

Yes. Companies can use an onsite repair path or route the work through pickup and shop production when configured.

Yes. Pickup, drop-off, and installation visits can remain tied to the customer, property, and originating work.

Yes. The property hierarchy can represent structures, areas, and individual openings so measurements and work stay attached to the right location.

Yes. Consultation, measurement, production, pickup, installation, service, and closeout records can remain connected across scheduled visits.

Yes. The scope can distinguish repairs, panel replacements, fabrication, and installation while keeping the work tied to the enclosure structure.

Property, visit, and job notes can carry the approved access and scope context into assigned field work.

Yes. Different opening types can be organized within the same property structure and carried into the project scope.

Measurements, estimates, documents, and work records are designed to retain their history instead of silently replacing the earlier project context.

Yes. Each opening can retain its dimensions, photos, notes, and selected configuration for estimating and production.

The property and opening history can preserve earlier measurements and service records for qualified staff to review on future work.

Yes. When configured, approved demand can connect to procurement and receiving before the installation is released.

Assigned field work can carry approved property, access, scope, document, and photo context into the installation visit.

Yes. Product options, site notes, photos, documents, and approved scope can remain connected to the property opening and job.

Warranty and service work can remain tied to the customer, property, installed scope, and available closeout history.

Yes. Customer records can connect to multiple properties so each site retains its own openings, jobs, documents, and service history.

Documents, notes, status, and approved scope can remain linked to the customer, site, estimate, and installation record.