Home Demo
Prepare migrations and modernizationsSecure maintenance and application changesAlign Business and ITPreserve expert knowledge
Features
Building the RepositoryUseSteering
Approach
Controlled AIAuditability
IntegrationSecurityHosting
🇫🇷 FR Contact Us
Application maintenance scenario

The same maintenance need. Two levels of context.

An existing business application is already running. A change request arrives. The same AI agent then handles it without, or with KONTEX.

Delivery disputes

OrderCare

Open disputes
128
Average delay
39 h
ERP export
8 PM
OrderClientDelayStatus
CMD-58291 Novalys Pro 52 h Open
CMD-58267 HelioNord 31 h Waiting carrier
CMD-58198 Artemis Lab 64 h Escalated
App Existing application

OrderCare is an existing business application for managing delivery delays and related disputes.

= Shared starting point

Both treatments start from this exact same application.

Events

Incoming ticket: Change

OC-1842

Maintenance
Request

Add a commercial gesture for delivery disputes > 48 h.

  • The advisor must be able to propose it from the dispute screen.
  • Requester: B2B support
  • Priority: next sprint
Maintenance Incoming ticket: Change

The maintenance change ticket is given to the same AI agent in both paths.

= Shared starting point

At this stage there is no divergence: same application, same ticket, same AI agent.

Without KONTEX
With KONTEX
Events

Specifications

Ticket
Requested action

commercial gesture from the dispute case

Trigger
Selected dispute case
Interaction
Commercial gesture action available to the advisor
Input
Amount and comment
Tracking
Processing status shown on the case

Specifications

Ticket + context
Target decision

controlled credit-note proposal

Eligibility
Delay strictly above 48 h
Business action
Credit-note proposal on a case
Control
Manager approval based on threshold and contract
Contracts
Contractual exclusions checked
Traceability
Decision historized
Integration
Event ready for ERP export
KONTEX MCP

KONTEX brings useful elements before specification, not after coding.

REG Business rules

48 h threshold, caps, exclusions

HIST Customer history

Past gestures and similar decisions

DEC Existing decision

Propose before approval

ERP Billing ERP

Expected event format

Without KONTEX
With KONTEX
Events

Implementation

Repo
LitigationView.tsx
  1. // action from the dispute case
  2. function onCommercialGesture() {
  3. openAmountModal(selectedCase.id);
  4. saveGestureAmount(selectedCase.id, amount);
  5. markCaseAsCompensated(selectedCase.id);
  6. }

Guided implementation

KONTEX MCP
CreditNoteAction.ts
  1. // business rules retrieved before coding
  2. const decision = CreditNotePolicy.evaluate({
  3. delayHours, contract, history
  4. });
  5. // conditional approval from contract and cap
  6. await ApprovalFlow.requestIfNeeded(decision);
  7. // decision recorded for auditability
  8. await AuditTrail.record(decision);
  9. // event matches the ERP-FIN format
  10. emit(BillingExportEvent.from(decision));
KONTEX MCP

KONTEX sends the files, rules, and contracts directly tied to the specification.

GIT Screen file

LitigationView

CODE Business rule

CreditNotePolicy

CODE Workflow

ApprovalFlow

LOG Traceability

AuditTrail

ERP API contract

Billing / ERP

Without KONTEX
With KONTEX
Events

Test checklist

Main path

  • Action displayed in the dispute case

  • Amount and comment entry

  • Status update after validation

The visible journey is tested.

Enriched checklist

KONTEX

  • Action displayed in the dispute case

  • Amount and comment entry

  • Status update after validation

  • Strictly greater than 48 h threshold tested

  • Customer cap and manager approval verified

  • Frame-contract exclusion simulated

  • Decision traceability checked

  • BillingExportEvent verified toward ERP

KONTEX adds the business cases that make validation safer.

KONTEX MCP

KONTEX provides the edge cases, incidents, and dependencies to verify.

TEST Edge cases

48 h delay, cap, contract exclusion

RISK Past incidents

Untraced credits, rejected exports

REG Business rules

Manager approval, frame contract

ERP ERP dependency

Expected billing event

Without KONTEX
With KONTEX
Events

Delivery disputes

OrderCare

Prepare gesture
Open disputes
128
Average delay
39 h
ERP export
8 PM
OrderClientDelayStatus
CMD-58291 Novalys Pro 52 h Open
CMD-58267 HelioNord 31 h Waiting carrier
CMD-58198 Artemis Lab 64 h Escalated

Commercial gesture

Novalys Pro - CMD-58291
Amount
EUR 120
Refund message
Hello, we will issue a EUR 120 refund following the delivery delay on order CMD-58291.

This message will be added to the support reply.

Cancel Submit

Delivery disputes

OrderCare

Prepare gesture
Open disputes
128
Average delay
39 h
ERP export
8 PM
OrderClientDelayStatus
CMD-58291 Novalys Pro 52 h Open
CMD-58267 HelioNord 31 h Waiting carrier
CMD-58198 Artemis Lab 64 h Escalated

Commercial gesture

Novalys Pro - CMD-58291
Amount
EUR 120
Message
Hello, we propose a EUR 120 credit following the delivery delay on order CMD-58291.

This message will be added to the support reply.

Eligibility
Confirmed delay: 52 h
Frame contract
2024 B2B frame contract - cap respected
Approval
Not required
Customer history
No similar gesture in 90 days
Credit status
Waiting for ERP transfer
Cancel Submit
App Same commercial gesture window

Both treatments open the same window in OrderCare. With KONTEX, business indicators are added directly inside the form.

= Comparison

What to compare: the extra information added inside the With KONTEX window.

KONTEX does not replace the AI agent.

It gives it the context that makes its work reliable.

Sounds familiar?

Let's chat about what KONTEX would bring to one of your systems, with your own tickets and your context.

Contact Us