Explore automation examples, catch up on the client briefing, and join our next conversation. This Hub is open to everyone—no account needed. Your company’s work and support requests stay inside your deverus workspace.
Workflow AS is in client use today. Expanded capabilities continue to land as they are validated.
The gallery explains examples discussed at our September briefing. Availability depends on your company’s setup and the work involved.
Tuesday, November 3, 2026 · 11:00 a.m. Mountain. Progress, automation examples, and your questions.
Tuesday, November 3, 2026 · 11:00 a.m.–12:00 p.m. America/Denver (Mountain)
10 a.m. Pacific · Noon Central · 1 p.m. Eastern
Join the deverus team for a walkthrough of Workflow AS inside the admin, the new AI admin module, security updates, and other improvements underway. We’ll distinguish what’s available now from what’s still being tested, with time for your questions.
Add the session to your calendar or open Google Meet. Reserve your spot below.
These examples explain the process—not a one-click installation. Client-reported means a client described using it; discussed examples are possibilities to scope; in testing is not general availability.
Search an authorized federal source using agreed criteria. Prepare eligible no-record results; route possible matches to a researcher.
Human checkpoint Possible records and ambiguous name matches
Before using it: Requires source access, approved search rules, and qualified review of uncertain matches.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Collect the facts and prepare review notes so a reviewer can focus on exceptions.
Human checkpoint Reportable or ambiguous records
Before using it: Company policies and qualified human judgment govern reportability; this is not a universal screening decision rule.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Retrieve permitted information from a supported county source and prepare it for the screening workflow.
Human checkpoint Exceptions and unsupported sources
Before using it: Source availability, permitted access, and result handling must be checked for each courthouse.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Review a pending queue, group items by age, and prepare a list of what needs attention.
Human checkpoint Priority and client-specific rules
Before using it: Agree aging thresholds and ownership; missing dates and conflicting statuses require review.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Use agreed turnaround information to prepare updated estimated completion dates.
Human checkpoint Missing source data / exceptions
Before using it: Missing or unreliable source information must be reviewed; an estimate is not a completion guarantee.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Gather onboarding details and coordinate repeatable setup steps and handoffs.
Human checkpoint Approvals and exceptions
Before using it: Define the checklist, then approve sensitive settings and account activation.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Compare required information against the company’s approved hold-release conditions.
Human checkpoint Mismatches and high-risk cases
Before using it: Exceptions and uncertain matches stay with a reviewer. Rules require company-specific validation.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Collect permitted information from supported sources and bring it into an agreed process.
Human checkpoint Unsupported sources and ambiguous records
Before using it: Access rights, source coverage, and interpretation need validation before use.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
The September briefing described Cerebrum and Argus connection work in testing.
Human checkpoint Provider access and mapping
Before using it: Provider access, mapping, and readiness must be confirmed for each environment. No general release date is promised.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Describe the systems and information to connect. Scope the exchange, map fields, test, and review before activation.
Human checkpoint Permissions, mapping, test approval
Before using it: Provider permissions and supported interfaces determine what can be connected.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Prepare monthly invoices from approved billing inputs, with authorized delivery as part of the agreed process.
Human checkpoint Review before send if required
Before using it: Reconcile amounts, verify recipients, and apply the company’s review policy before sending.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Gather the error and relevant configuration context to help investigate an integration problem.
Human checkpoint Credential resets and client-specific config
Before using it: People approve credential changes and other sensitive configuration actions.
Based on the September 16 client briefing. Scope and availability need confirmation for your company.
Support investigations using relevant knowledge and configuration context, including a staging settings check.
Cerebrum and Argus connection work. Availability and setup still need confirmation for each client.
A clearer route for enhancement requests through Zendesk. Submission details will be shared when ready.
These are dated meeting updates, not a live deployment dashboard. For help with your company’s work, use your existing deverus support channel or your Workflow AS workspace.
The briefing story stays available below: how requests enter Workflow AS, how automations and integrations are scoped, and how unresolved work reaches human review.
Support, automations, configuration, and integrations—starting inside your deverus workspace, with context carried through each handoff.
Reserve your spot for the Workflow AS follow-upTuesday, November 3, 2026 · 11:00 a.m. Mountain · 10:00 a.m. Pacific · Noon Central · 1:00 p.m. Eastern
deverus clients already use Workflow AS for automation and support.Progressive rollout as capabilities are validated. Human review remains part of the process.
Your company’s operational assistant. Start with what you need, in your own words.
Turn repetitive work into a scoped automation, with testing and approvals.
Assess the connection, create the integration, and review its statistics.
Handle supported work; carry unresolved requests into human-reviewed specialist investigation.
From courthouse information to client setup and aging pending items—start with the process your team wants to improve.
Many automation patterns are already running in client operations.Explore the examples above; they are not a complete inventory or a count of automation runs.
Connect the retrieval work to the screening process, using supported courthouses and information sources where access is available.
Examples identified by Shawn as existing automation areas. The steps shown illustrate how a request could be scoped; they are not live execution records.
Integration requests go to Integration AI to assess requirements, create the integration, and provide statistics on its operation.
Define which orders, status updates, or results need to move between the systems, and in which direction.
Illustrative statistics view—not live data. Exact measures and controls depend on the implemented integration.
Follow a support request from the first question to its recorded outcome.
Describe the issue in the in-app conversation. Workflow AS gathers the details needed to understand what happened and what you need.
This development path extends the supplied support diagram; it is not a statement that every stage is already available or automated.
The design brings documentation, previous investigations, and conversation history into the support process.
Relevant guidance and technical references inform the investigation.
The goal: preserve collected information when another team becomes involved.
Prior outcomes feed the learning loop shown in the process design.
The intended benefit is less repeated investigation and better-informed future assistance—not a promise of automatic resolution.
We’re opening a dedicated path on our Zendesk board for the improvements you need—with AI-assisted development helping us explore and build the right solution. Until that board is live, use the on this portal.
Tell us what your team is trying to accomplish, what gets in the way, and what a useful improvement would look like.
Review needs specific to your configuration, reports, integrations, or operating process.
Assess ideas that could benefit multiple clients and inform platform priorities.
We’re exploring how you could offer Workflow AS to your own customers—adding automation services alongside your screening relationship.
Help customers coordinate repeatable new-customer or employee onboarding tasks, documents, and handoffs.
Help their teams track screening progress and organize follow-up on missing information.
Explore connections between the applications they use and the services you provide.
Identify one repetitive process. Together, assess feasibility, define responsibilities, and explore a focused offering.
What would you improve in your business—and what could you help your customers improve?