---
title: "How it Works | OperationsLens"
description: "A look at how OperationsLens turns customer emails and calls into orders, answers, and invoices — the data flow, the knowledge layer, integrations, security, and rollout."
url: https://operationslens.ai/how-it-works/
lang: en
---

How it works

# How it Works

The data flow, the knowledge layer behind it, how it connects to what you already run, and how a rollout actually goes.

-   [01 One loop](https://operationslens.ai/how-it-works/#loop)
-   [02 knowledge layer](https://operationslens.ai/how-it-works/#knowledge)
-   [03 Integrations](https://operationslens.ai/how-it-works/#integrations)
-   [04 Security](https://operationslens.ai/how-it-works/#security)
-   [05 Deployment](https://operationslens.ai/how-it-works/#deployment)

01 · Data flow

## One loop, not three tools

Work arrives as a message and leaves as an order, an answer, or an invoice — the same system carries it the whole way. An email or phone call becomes an order in your ERP. Questions about that order go through Customer Desk. What gets delivered is checked against what gets invoiced, with any deviation surfaced before it goes out.

1.  Arrives
    
    ### Email or call
    
    “Please send 12 pcs of ART-4410 to Vantaa by Thursday.”
    
2.  Step 1
    
    ### Order Intake
    
    Becomes an order draft in your ERP.
    
3.  Step 2
    
    ### Customer Desk
    
    Questions about that order, answered from it.
    
4.  Step 3
    
    ### Invoice Check
    
    Delivered vs. invoiced, deviations surfaced first.
    
5.  Leaves
    
    ### Order · answer · invoice
    
    In your ERP, with its source attached.
    

![An Order Intake ticket: the incoming message, what the agent made of it, and the order draft](https://operationslens.ai/_astro/order-intake-ticket.BSiCFxAn_Z2nJtHj.webp)

Order Intake — the message, what the agent made of it, and the draft waiting for a person.

02 · Shared memory

## The knowledge layer

Every answer is only as good as what the system actually knows. Products, price lists, customers, terms and practices sit in one shared layer underneath all three modules — it's why Order Intake reads an order correctly, why Customer Desk can answer without someone opening the ERP, and why Invoice Check catches what's missing.

01 Order Intake

02 Customer Desk

03 Invoice Check

knowledge layer shared by all three

-   products
-   price lists
-   customers
-   terms & practices

03 · In and out

## Integrations

Orders and questions arrive however your customers already work — email forwarding, a phone call, a dropped file, or a direct API connection. On the other side, OperationsLens connects through Fyrn to the ERPs Nordic SMEs actually run: Netvisor, Procountor, Oscar, and Lemonsoft.

Arrives as

-   Email
-   Call
-   File
-   API

![OperationsLens](https://operationslens.ai/images/logo-light.svg) reads · drafts · checks

Writes to, via Fyrn

-   Netvisor
-   Procountor
-   Oscar
-   Lemonsoft

Nobody has to adopt a new interface as their everyday tool. OperationsLens works around the process you already run and automates the steps that create the most manual work.

04 · Control

## Security

Your data is hosted in the EU and handled under GDPR. Every action a human should see, a human sees — nothing books itself into your ERP without review where you've asked for one. Every step is logged, so any order, answer, or invoice can be traced back to the message that started it.

-   01
    
    ### EU hosting & GDPR
    
-   02
    
    ### Human review
    
-   03
    
    ### Audit trail
    

![An Invoice Check deviation, with how the number was checked and a confirm step](https://operationslens.ai/_astro/invoice-check-deviation.BTveZfqG_Il3HJ.webp)

Invoice Check — how the number was checked, the rows it came from, and a person confirming.

05 · Rollout

## Deployment

Rollout starts narrow: one channel, one team, one module — proven before it expands. Each additional module reuses the context already in the system, so it connects faster than the one before it. You stay in control of what goes live and when.

1.  Step 1
    
    ### Connect
    
    One channel, one team, one module.
    
2.  Step 2
    
    ### Expand
    
    Module by module, reusing what the system already knows.
    
3.  Step 3
    
    ### Scale
    
    More channels, languages, teams and ERPs, on your schedule.
    

## See it run on one of your own orders.

[Book a 30-minute walkthrough](https://operationslens.ai/contact/) [View pricing](https://operationslens.ai/pricing/)