The leadership view.
You are the GM, the COO, the operations director, the owner-operator who stopped sitting at the dispatch board every day. You are not closing a single ticket. You are running a department of departments. Dispatch (three to five seats), AR (two to four seats), AP and payroll, a parts manager, a service department of fifteen to thirty technicians, a delivery fleet of eight to fifteen drivers (or eighty, or three hundred), and a leadership bench that needs to trust what their teams see is consistent, auditable, and yours.
You also need to run multiple brands without doubling your headcount, and you need an IT lead who can sign off on the platform’s security posture without a six-week diligence cycle.
KozyOps was built for that. It runs today across 11 tenants in production, monitoring 1,847 tanks 24/7.
What the platform gives leadership
Configurable dashboards with department-level KPIs
The dispatch supervisor sees the desk’s queue, shift hand-off, and route status. The AR manager sees aging by team member and the collections counters. The parts manager sees the inventory request backlog. The service manager sees tech utilization. The GM sees the rollup, configured for the rows that matter on Monday morning.
Real-time employee roster
The Admin Dashboard shows who is on the clock, on any selected date, at payroll-grade resolution. Clock-in and clock-out events come straight from the field via KozyServiceman.
Multi-tenant, deployed per dealer
Every dealer on KozyOps gets their own database, their own S3 bucket folder, their own feature-flag set. No shared customer data. No shared anything. This is the deployment model, not a setting.
Multi-brand under one operator
Run multiple brands out of the same operation. Brand-account number generation, per-brand customer numbering, per-brand visual customization. Separate HOD licenses, separate Service Plan PDFs, separate Portal URLs (with light and dark logos, favicon, support contact). Consolidated leadership reporting across brands, brand-isolated customer-facing surfaces.
Multi-depot operations
Filter the dispatch board, the route board, and the will-call queue by depot. Assign drivers and trucks to depots. Run the same back office across two or three loading sites (or a dozen) without spinning up parallel deployments.
Real RBAC, not a flag
Eight built-in roles: SuperAdmin, Admin, Accounting, Office, PartsManager, Technician, Driver, Customer. Enforced server-side, not in the UI layer. Segregation of duties between AR and AP, between dispatch and payroll, between parts and accounting. A driver cannot see the AR ledger because the API refuses, not because the menu is hidden.
Audit logs the auditor and the IT lead can both use
- View logs: who opened which record.
- Record-level change logs: what changed, by whom, when.
- Dataset-level change history: across the platform’s resources.
When a number looks wrong and someone needs to know who touched it, the answer is on the screen. When IT asks for the access audit, it exports.
Hiring and onboarding workflow
Adding a seat to the dispatch desk, an AR clerk, or a tech is a matter of provisioning a role. The eight-level RBAC means a new hire gets the right access on day one without a custom permission build.
Platform settings, refreshed automatically
Runtime feature flags and settings refresh every minute. Turn something on for one tenant without redeploying.
Connect to your GL on your terms
Sage Intacct (deep), QuickBooks (lighter), or a generic export adapter. OAuth-based login for the accounting connection, no IT ticket required.
Communications you control
Twilio SMS conversations and OnSIP softphone integration both write back to the customer record. Outbound emails route through AWS SES with Handlebars templates you can customize.
What the IT lead will ask for
A growing operation has an IT lead, sometimes a small IT team. KozyOps is set up to answer their checklist:
- Per-tenant data isolation (separate database, separate S3 bucket).
- OAuth-based connections to third-party systems (Sage Intacct, QuickBooks).
- Server-side role enforcement, audited.
- Production error monitoring via Sentry.
- Eight-level RBAC with segregation of duties.
- Tenant-scoped feature flags refreshed every minute.
A more detailed security posture page is coming.
What it is not
A few things leadership asks about that are not in the platform today:
- Customer profitability analytics. Per-customer margin reporting is on the roadmap.
- Service job profitability analytics. On the roadmap.
- Fleet-fueling for commercial multi-location customers. On the roadmap.
- Full warehouse inventory management. The parts module handles parts requests and project parts. Full warehouse inventory is on the roadmap. If your parts manager needs depth here, ask us where the gap is on a call.
We would rather tell you these are coming than tell you they are here.