From complexity to one clear flow.

AI and automation connect people, processes and systems, with review points and a clear direction.

Let’s talk See the flow

Flow in action.

An illustrative document workflow.

A request moves through systems, automations and review points. See how each step connects to the next.

One mesh. Three connection points.

The request arrives.
Documents arrive with the data defined for the process. Missing information needs to be checked.
Documents and information
The routine moves forward.
Rules guide the routing. Questions and exceptions go to human review.
Rules and automation
The team reviews.
Records help assess the delivery and decide the next step.
People and records

Every step has a next step.

The process moves forward.
The full picture stays in view.

Requests, rules and people connected in one design. See how the process finds its next step.

An illustrative document workflow.

Orchestration

5 main steps / 01

Select a node to understand its role in the process.

Human assessment

Request → Check → Rules → Routing. When needed: Rules → Human review → Routing.

Receive request

One intake point brings the request together and connects the first check.

01Orchestration

Organize the intake.

Requests, documents and information enter the same flow. Each step connects clearly to the next.

From request to review

Define the next step.

Process criteria guide the destination. The main path moves forward; anything that needs assessment goes to a person.

One decision, two possible paths

Give exceptions a path.

Questions and incomplete information have a review point. After a person assesses them, the request rejoins the routing flow.

Review is part of the flow

02Execution

Prepare for review.

An agent organizes the intake. Document processing prepares information for review, keeping each task connected to its process step.

Agent and document processing

Connect the routine.

An API can retrieve information. A robot can carry out a data entry routine. Execution depends on the access available in each system.

API and interface automation

Review before proceeding.

Criteria guide the routing. When an issue needs assessment, a person decides and reconnects the request to the flow.

Human review and routing

03Governance

Define what can flow.

The design specifies which information each task needs. Purpose and access guide how data is used in document processing, queries and data entry.

Scope, purpose and access

Set boundaries for AI.

The model, instructions and context are part of defining the process. Usage limits and review criteria guide where AI can act.

Model, instructions and criteria

Review and keep a record.

Issues have a person responsible for assessing them. The design also provides for recording the decision before routing.

People and records

[data-functioning] [data-functioning-interactive] { display: none !important; }

The process tasks

Request → Check → Rules → Routing. When needed, human review reconnects the request to the flow.

Organize intakeAgent / Receive request
The agent organizes the initial information for review, within the defined scope.
Define instructions, context and limits for organizing the intake.
Read documentsDocument AI / Check data
Document processing prepares information for review. Questions and incomplete data remain subject to assessment.
Specify which information document processing may receive and prepare.
Query systemAPI / Check data
An API connection can retrieve the information needed when the system provides this access.
Define the data needed and the intended access for the query.
Enter dataRobot / Check data
Automation can carry out a defined routine through a system interface when that is the available form of access.
Set limits on the information the routine may record and its destination.
Check informationAgent / Check data
Prepared and retrieved information supports the check, within the criteria defined for the process.
Specify the model, context and review criteria for checking information.
Apply rulesAgent / Define destination
Rules indicate routing or the need for human assessment. The decision follows the process criteria.
Define the criteria that guide the decision and when a person needs to assess it.
Assess issuePerson / Human review
A person assesses the issue before the request returns to routing.
Identify who assesses the issue and what must support the decision.
Route requestAutomation / Route request
The result is sent to the next defined destination, after the main path or human assessment.
Plan for recording the decision and defining the routing destination.

The path stays connected.
The criteria stay visible.

Let’s talk

Where the flow
can go next.

Three areas of work to organize decisions, connect workflows and evolve systems.

AI governance

Define criteria for using AI, with clear responsibilities and review points.

Guidelines and responsibilities
Usage and review criteria
Decision traceability

View deliverablesHide deliverables for AI governance

What we can define together

An inventory of AI applications and uses.
Guidelines and a responsibility matrix.
Human review points and records.

The scope and acceptance criteria are defined with the team responsible.

Process automation

Connect steps, information and systems around the needs of each workflow.

Workflow mapping
System integration
Exception handling

View deliverablesHide deliverables for Process automation

What we can define together

A process map and routing rules.
A workflow with permissions, approvals and exceptions.
Acceptance testing and operational guidance.

The scope and acceptance criteria are defined with the team responsible.

Legacy modernization

Plan the evolution of existing systems, accounting for dependencies and continuity.

Environment assessment
Integrations and interfaces
Incremental evolution

View deliverablesHide deliverables for Legacy modernization

What we can define together

A map of systems, interfaces and data.
Integration or reconciliation within the agreed scope.
Reconciliation and recovery testing.

The scope and acceptance criteria are defined with the team responsible.

We start with your team’s problem.

The first step is to choose a process and understand its context.

AI already
at work.

Public and private sector cases show where automation and AI are already making a difference.

Cases independent of DezoTech. Metrics reported by the institutions and their suppliers, within the scopes indicated.

Cases 1 of 7

[data-social-proof-interactive], [data-proof-controls], [data-proof-hint] { display: none !important; }

Public · Brazil

ALICE

Preventive analysis of public procurement

Financial benefits from preventive actions informed by ALICE.: R$ 1.25 bn
Automated reading of public procurement documents.: AI + data
Alerts support preventive action by the CGU.: People

2024 results

Source: CGU · 2024 results

Public · Canada

CRA

Digital verification and GenAI assistance

Fewer security codes sent by mail with digital verification.: 65%
Successful digital verifications by the December 2025 briefing.: 2.75 m
Questions to the GenAI chatbot between April and October 2025.: >1.85 m

December 2025 briefing

Source: CRA · Dec 4, 2025 · English

Public · Brazil

Victor

Sorting appeals by topic

To match appeals to topics of general repercussion.: 5 s
The previously reported time for this same step.: 40 min
The remaining steps continue to involve people.: People

Report published in August 2026

Source: STF · Aug 19, 2026

Private · Latin America

Nubank

AI in customer service and internal search

Shorter chat response time, according to the OpenAI case study.: 70%
Chats managed by the assistant per month in the report.: >2 m
People using internal search monthly in the report.: >5,000

OpenAI implementation case study

Source: OpenAI · Nubank case study

Private · Brazil

Sem Parar

AI supporting human customer service

Shorter average handling time with the copilot.: 9.3%
Customer service recommendations since launch, in the report.: >35,000
Copilot deployment across the entire operation.: Dec/2024

Report published in May 2025

Source: Microsoft · May 26, 2025

Private · Brazil

DB / Rands

Automated document reading

Shorter document processing time in credit analysis.: 80%
Of work saved per month in the process described.: ≈166 h
Of execution time per document in the automation.: <2 min

Report published in December 2024

Source: Randoncorp · Dec 11, 2024

Private · International operations

DHL

Mobile robots in order picking

More items picked per hour with support robots.: Up to 180%
Productivity increase range published in the study.: 30–180%
Physical automation in the picking step.: Robots + people

Publication updated in June 2023

Source: DHL · Jun/2023 · English

Open “View metrics” to explore the details. Use the arrows or swipe to see the other cases.

Watch a workflow
become clear.

From receiving a request to routing it, try a workflow with rules and human review.

Local simulation with three fictional requests.

Receive
Gather the three sample requests.
Check
Identify missing documents.
Route
Separate direct routing from review.

Demonstration log

0/3

Document workflow / local example

Ready to start the example.

Ready to begin. Move through the steps at your own pace.

Exceptions also
have a path.

A workflow is clearer when it shows what can advance and what needs a person.

Select a step or a request. For PED-1043, you can add a sample document and confirm the review.

Explore the issue

The demonstration uses sample fields and rules. It does not use AI to read documents or connect to external systems.

Request routing

Fictional data

Received: —
Routed: —
For review: —

Select a step to understand its role in the workflow.

Main path and returnRouting to a person

Requests → Check → Routing. When needed, the check routes a request to a person, who reviews it and returns it to the workflow.

One point of entry.

The example brings together three fictional requests. Start the demonstration to follow their arrival.

Sample requests

PED-1042 · Purchase of supplies

Unit: Administration
Document: Sample document A
Status: Waiting to start

[data-demo-live], [data-demonstration] a { display: none !important; }

The complete example

Three requests are received and checked. PED-1042 and PED-1044 have documents and move on to routing. PED-1043 has no document and goes through human review. Once its document is added and checked, it can also move to the next step.

Which of your team’s workflows can we understand first?

Shall we begin?

Tell us how things work today and what needs to improve.

Let’s talk View demonstration

From complexity to one clear flow.

Flow in action.

The request arrives.

The routine moves forward.

The team reviews.

The process moves forward.The full picture stays in view.

Orchestration

01Orchestration

Organize the intake.

Define the next step.

Give exceptions a path.

02Execution

Prepare for review.

Connect the routine.

Review before proceeding.

03Governance

Define what can flow.

Set boundaries for AI.

Review and keep a record.

Where the flowcan go next.

AI governance

What we can define together

Process automation

What we can define together

Legacy modernization

What we can define together

We start with your team’s problem.

AI alreadyat work.

ALICE

CRA

Victor

Nubank

Sem Parar

DB / Rands

DHL

Watch a workflowbecome clear.

Demonstration log

Exceptions alsohave a path.

Request routing

One point of entry.

Sample requests

PED-1042 · Purchase of supplies

Shall we begin?

The process moves forward.
The full picture stays in view.

Where the flow
can go next.

AI already
at work.

Watch a workflow
become clear.

Exceptions also
have a path.