Services
What kind of work needs an owner?
Choose the place where the work begins. Both paths lead to a managed operation that Gridex prepares, runs, reviews, and maintains for your team.
Calls need to be answered, understood, routed, scheduled, supported, or handed back cleanly.
In pilot · not operating for customers Open this service › The work moves across systems Managed Workflow OperationsDocuments, records, follow-ups, schedules, and exceptions need to keep moving between tools and people.
Operating work · service line in validation Open this service ›If the work begins with a call
Start with the phone job you need to understand.
These are five ways into the same Managed Voice service and the same Agent. Each page answers a different operating question before asking you to evaluate Gridex.
Responsibility split
The service starts after you choose the work.
The tools and business decisions remain yours. Gridex owns the operating burden between an approved brief and a finished result.
System access, approved policies, owners for exceptions, and decisions that must stay human.
Useful handoffs, briefs, records, updates, and a clear path when the operation cannot finish safely.
How Gridex handles discovery, approval, testing, launch, QA, and change control
Current service and evidence status
Gridex is a managed service, not software. Nobody on your team logs into a Gridex tool. Managed Voice Operations is being built around one Agent and one maintained knowledge system to answer inbound calls, work out what the caller needs, and then act on it — route or transfer, book the appointment, answer an approved support question, collect the facts, or tell the right person it happened — and deliver the result into the systems a team already uses. Managed Workflow Operations runs recurring cross-system work today: records updated, follow-ups chased, exceptions routed to a person, outputs delivered on a schedule — including stabilising an automation that works in a demo and fails in production. The Voice Demo is in pilot as of 2026-08-11. Managed Voice is not yet operating for customers; demo calls are product tests, not customer production. No customer result or tested third-party integration is published.
Both lines are designed to be run the same way: scope the work, build it, test it against real and deliberately awkward inputs, launch it narrow, review the output, route exceptions to a person, and keep it running as tools and rules change. The Voice Demo is in pilot as of 2026-08-11. Managed Voice is not yet operating for customers; demo calls are product tests, not customer production. No customer result or tested third-party integration is published. Managed Workflow Operations follows this method today and is in validation.
A practical starting point
See the Voice service, or test the shared Agent.
Looking for older CMMC, AI compliance, insurance, or exclusions material? Open the Research Archive.