Digital Reconciler
The Digital Reconciler's console: import the statement (OFX/CSV), see the matches the agent PROPOSED with the evidence that supports them (accept or reject), the named pending items for what didn't match (it never disappears), and close the day with a signature (hash). The settlement only becomes i…
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Export
Form fields
DemandaDemanda cujo caminho real está sendo reconstruído.
Tipo de eventoO que aconteceu: mudança de status, troca de responsável, comentário, anexo.
DescriçãoO que foi registrado no evento, do jeito que quem mexeu escreveu.
Status anteriorDe onde a demanda saiu. É o par com o status novo que desenha o fluxo real.
Status novoPara onde a demanda foi. Transição que não está no fluxo desenhado é desvio de processo.
Responsável anteriorDe quem a demanda saiu. Muita troca aqui é sinal de repasse.
Responsável novoPara quem a demanda foi.
Visível ao clienteSe o evento aparece no portal do cliente. Evento interno não deve vazar para lá.
Start here
O que esta tela responde
How your process REALLY HAPPENS — reconstructed from the requests' history, not from the flowchart someone drew. It shows the paths actually taken, the time in each transition and where work stalls.
What this screen is
The discovery of the REAL AS-IS flow from the history operations have already recorded — without importing any tool's log, because the log is already ours. Once a request type is chosen, the screen reconstructs each case by its status path and shows: the VARIANTS (distinct paths) with the % of cases that followed each one, the AVERAGE TIME per transition, the BOTTLENECK (the handoff that consumes the most time, by evidence) and the CONFORMANCE — how much of what actually happened matches the designed flow (TicketWorkflow) and where there was deviation. The entire calculation record stays open.
How to
What this screen answers
A handful of paths usually covers most cases, and the rest is a tail of variants that appear once or twice. That tail is rework, deviation and "everyone does it their own way" — that is where the money is, not in the main path.
What this screen answers
It compares what happens with the flow declared in Request workflows. High divergence can mean two opposite problems: the team bypassing the process, or the process designed for a reality that no longer exists. It's worth investigating which before correcting.
Rules
Nada é digitado nem estimado aqui
Everything comes from the status changes that have already been recorded. That is why the quality of the picture depends on the team really moving the requests: whoever only changes the status at the end of the month produces an apparently instantaneous process.
Frequently asked questions
Which question this screen answers
Which path work REALLY takes — not the designed one, the one travelled. Once a request type is chosen, the screen reconstructs each case from the status history operations have already recorded (no log is imported: the log is ours) and answers: which VARIANTS exist and what % of cases followed each one, how much time each transition takes on average, which handoff is the BOTTLENECK by evidence, and how much the real flow CONFORMS to the one designed in TicketWorkflow. The calculation record is open on every number.
Was this article helpful?
In the same module: Where work gets stuck14
Process AS-ISHow the process works TODAY, in three layers: the record of what it receives and delivers, the map of who doe…Agile CoachAn assessment of the team, made only with numbers the team has already recorded — with the calculation trail …Value ChainThe org chart shows WHO reports to whom. The value chain shows HOW work flows through the company until it be…Customer 360The single view of the customer: contracts, finance, support, visits, and conversations in one place. It's co…Service orderThe record of the field service: customer, scope, parts, hours, and signature. A closed service order is the …MCP ServerExposes Tenka's tools to external AI agents via the MCP protocol. What an external agent can do is exactly wh…Context mapYour company is an open system: it takes in people, resources and demands, and gives back deliveries, results…Operação assistidaA IA acompanha a operação em tempo real e sinaliza o que exige ação. Ela SUGERE; a execução com efeito — muda…
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.