Questions about Opryx Dispatch, answered.

Dispatch is for property managers, owner-operators, landlords, and property-management organizations that coordinate maintenance across in-house technicians, outside vendors, or a combination of both.

It's designed for teams that want to reduce manual intake, routing, scheduling, follow-up, and cost tracking without replacing their entire property-management system.

No. Dispatch is focused on maintenance operations. It works alongside the systems you already use rather than requiring you to replace your accounting, leasing, or core property-management platform.

Today, onboarding runs on structured CSV imports with column mapping and a dry-run preview. Direct property-management-system integrations are under evaluation.

Nothing needs to be installed. A tenant opens a secure link in a modern browser on any phone or computer and reports the issue through a guided chat experience. The tenant site is fully mobile-responsive, and tenant sign-in works through a magic link delivered by email.

A vendor doesn't need an account to begin. The vendor receives a secure link through which they can accept work, provide an estimated arrival time, choose one of the tenant's offered scheduling windows, update the job, and report itemized parts and labor.

Vendors who work with your organization regularly may optionally set up a self-service account.

Yes. Dispatch supports organizations that use internal maintenance teams, outside vendors, or both. Routing is configured per maintenance category (internal-first, external-first, or excluded) and respects trade coverage, skills, and license validity on the internal side, and vendor category and region assignments on the external side, with per-property emergency vendor routing.

Dispatch starts with the tenant's own description instead of asking them to repeat it. It asks only the follow-up questions still needed to classify the problem, determine location and severity, and check relevant safety conditions. Tenants can add photos during the conversation, and Dispatch uses those images as additional triage context.

The resulting request reaches the office structured by category, severity, responsibility, and supporting evidence, with uncertain or higher-risk cases sent for human review.

Yes. A tenant can attach photos during the maintenance conversation without leaving the intake flow. Dispatch analyzes the image as part of triage, and the photo plus the AI-generated description remains visible on the work order for office staff and technicians.

Life-safety cases are not left solely to a generative AI model. A deterministic rules layer evaluates known hazards such as fire, suspected gas leaks, carbon-monoxide concerns, and active flooding before, and independent of, the normal AI workflow, and the tenant always has one-tap emergency options in the chat.

When a life-safety condition is detected, Dispatch provides immediate, location-aware instructions such as evacuating, calling 911, or contacting the applicable gas utility's emergency line for that property. It also creates an emergency work order instantly and immediately alerts the designated emergency contacts for that property.

Low-confidence or higher-risk cases go to a human review queue. You control the routing and approval rules, and consequential actions remain visible and auditable.

Autonomous where it should be. Accountable where it matters.

No. You define the routing, approval, escalation, and cost-review rules. Dispatch handles routine coordination while preserving human intervention for exceptions and higher-risk decisions.

Significant actions are logged and reviewable, and consequential routing and vendor-selection decisions stay under human review inside the rules you configure.

For internal work, Dispatch evaluates technicians by trade, skills, license validity, and actual calendar availability, and estimates how long the job will take from your organization's own completed-job history. It then offers the tenant real appointment slots at intake time instead of creating more phone calls for the office.

For externally routed work, the tenant provides two acceptable availability windows. The selected vendor accepts one of them through the secure vendor link and provides an expected arrival time, cutting out the three-way phone tag among tenant, office, and vendor. The tenant is notified of the confirmed window.

The tenant's entry preference is captured during scheduling. The tenant can authorize entry or provide availability windows for when someone will be present, creating a record of the authorization associated with the work order.

The tenant portal shows the current open or closed status of each request. Branded emails are sent automatically when work is scheduled, rescheduled, completed, or cancelled, including the arrival window when applicable. That reduces the need for tenants to call the office just to ask where the request stands.

Yes. The tenant can write from the portal, office staff can reply from the work order, and internal technicians can read and respond from the field. Unread indicators show what is new, email notifications prompt the right side when a reply arrives, and the conversation remains attached to the work order as a time-stamped record.

Technicians can work from a phone to review their queue, open property navigation in Google Maps, see tenant photos, log truck-stock or purchased parts, attach receipt photos, and message the tenant. Grab Work lets a technician already onsite claim another open job at the same property or take over a teammate's not-yet-started ticket, with the change communicated automatically.

Yes. Alert routing can be configured by category and property for events such as emergencies, owner-approval decisions, tenant messages, review queues, and possible liability reports. Email and text recipients can be targeted so the right people are notified without sending every event to everyone. Sensible defaults remain in place when no custom rule exists.

Yes. Eligible work can be sent as an RFQ to multiple vendors. Their responses remain attached to the work order so your team can compare and award the work. You control when competitive bidding applies.

A property can have its own approval threshold or inherit a portfolio default. When a vendor quote or office estimate crosses that threshold, the owner receives a secure email link to approve or decline the work and provide a reason. Dispatch holds the work from dispatch until the decision is made, sends a reminder after three days, and escalates to the office after seven days. No owner portal or app is required.

Dispatch builds a vendor scorecard from actual work-order history, including response time, completion time, cost efficiency, quality, callbacks, and tenant satisfaction. Vendors can be compared side by side, and low-sample records are flagged so a small number of jobs is not mistaken for a reliable trend.

The scorecard supports routing decisions; it does not remove operator oversight.

Dispatch records cost at the work-order level, including truck-stock parts, purchased parts, receipt images, labor, vendor finals, and pending costs where applicable. Spend analytics compare properties over 30, 90, or 365 days using confirmed versus pending spend, work-order counts, average cost per job, and top cost category, with drill-down by unit and category.

No, by design. Dispatch captures and organizes maintenance costs. Your accounting or property-management system remains responsible for billing tenants, owners, or other parties.

Each customer receives a dedicated environment on AWS: its own database, its own isolated network, and its own branded subdomains with separate staff, tenant, and vendor sites. Customers are architecturally isolated from one another.

Yes. Opryx supports OpenID Connect and SAML identity providers, and has been validated with Microsoft Entra ID, Okta, and Google Workspace.

Configuration is self-service through the application's settings workflow after deployment, so you don't need to choose your identity provider before onboarding.

Yes. SCIM 2.0 provisioning synchronizes users (create, update, deactivate) and groups from your directory, with group-to-role mapping in the application. It's been validated with Microsoft Entra ID and Okta.

Identity stays customer-managed: SSO and MFA run through your identity provider, and access is role- and scope-based with least-privilege defaults. Authorization is enforced server-side on every request, sensitive actions leave audit trails, and traffic is encrypted in transit, including mutual TLS between services inside each environment. Every customer runs in a dedicated environment.

Opryx supports guided CSV imports for properties, units, tenants, leases, vendors, and historical work orders.

The import process includes column mapping and a dry-run validation preview, so you can review exactly what will be created before committing the import.

Yes. Historical work-order imports give Dispatch useful context for vendor performance, recurring issues, callback history, and job-duration estimates. Recommendations strengthen as that history accumulates.

Not today. Current onboarding uses structured CSV imports.

Opryx is evaluating direct integrations based on customer demand. Tell us which system you use and what you'd need exchanged.

Yes. Dispatch v1 is complete and available for new customer deployments, with a full live demonstration environment where you can see it on an operation shaped like yours before committing.

Pricing depends on the size and operating model of the property portfolio. Contact Opryx to discuss your organization and receive current pricing information.

Opryx offers a focused live demonstration showing a maintenance request from intake through triage, routing, scheduling, and follow-up.