08:40The plant floor
Orders, rates, dispatch updates and payment promises move through your groups all day. DataLense keeps track of every one, so nothing depends on someone remembering.
Orders come in on WhatsApp and get typed again into the ERP. The dispatch sheet lands in another group. Payment promises sit in a personal chat, and the status lives in someone's memory. DataLense keeps track of all of it.
Link a number by scanning a QR code. Dealers, stores and sales keep using the same numbers and groups, and nobody types anything twice.
Approve a report layout once. Every later dispatch sheet or order list is read by code into records, never guessed by AI.
Ask the way you'd ask your manager. Every fact links to the message, sheet or ERP record behind it.
West region dealers
Marco, Aisha, Rivera Hardware, +14
Rivera Hardware, Valencia
Need 40 boxes PVC-25 by Friday. Same 30-day credit?Aisha (stores)
Stock_pending_03-Oct.xlsx
Excel, 48 KB
Records from the file
Read by code| Item | Party | Pending |
|---|---|---|
| PVC-25 box | Rivera Hardware | 40 |
| PVC-32 box | Okafor Traders | 120 |
| Elbow 25mm | Al Noor Sanitary | 600 |
Which dealer orders are still waiting to be dispatched?
Three, totalling 760 units. Rivera Hardware's 40 boxes of PVC-25 are promised for Thursday12.
Al Noor Sanitary, Dubai
Rate for 32mm elbow?
Costa Pipes
Payment done, pls check
Factory QC
Batch 1142 cleared
Okafor Traders
Thanks, received
Every number and group in one inbox, with the customers still waiting and how long they've waited. Status stops living in one person's phone.
Daily dispatch report
Shared in 2 groups, approved by Sofia on 12 Sep
Dispatch sheets, order lists, stock reports, even a photo of a delivery note. Approve the layout once and every later copy becomes records by itself.
Daniel Rivera
Rivera Hardware, Valencia · Dealer
One history per customer, however many numbers they use, kept in your workspace. When a salesperson moves on, the history doesn't go with them.
Which customers complained about delivery delays this month?
Four customers raised delays. Al Noor Sanitary waited 9 days on order SO-22311, and Costa Pipes asked twice about the São Paulo truck2.
Ask what's pending, at risk or overdue. Answers come only from your chats, sheets and ERP, and every fact links back to where it came from.
Customers who write after lunch and after 6 pm wait four times longer than the morning.
Customer messages and replies against last week, and the hours when follow-ups slip. Counted from your messages, with no AI needed.
Every request signed with HMAC-SHA256. The last 100 kept for 30 days.
New orders and changes go to your CRM, Zapier or n8n the moment they happen. Read-only access for AI assistants like Claude, too.
Pick a role. These are questions DataLense answers today, each with the source behind it, plus one from where we're heading.
See the whole business without calling around.
Which customers complained about delivery delays this month?
Four customers raised delays. Al Noor Sanitary waited 9 days on order SO-2231, and Costa Pipes asked twice about the São Paulo truck. Both are now marked delivered.
Conversations come in from messaging, transactions from your ERP, and DataLense joins them into one picture. Answers and events flow out to the tools your team already uses. All integrations
Where conversations happen
DataLense
Inbox, people, records, answers
Where transactions are recorded
Webhooks
CRM, Zapier, n8n
MCP
Claude, Cursor, VS Code
Where this goes
Every business keeps two sets of books. The ERP knows what was invoiced. The conversations know everything that decided it: the enquiry, the rate, the promise, the delay. DataLense is building the system of record for that second set, and then the intelligence that acts on it.
Not another app to check. DataLense comes to you on WhatsApp, with what changed and who needs a call.
1. FindAvailable now
Everything your team says and shares in chat, searchable next to your ERP, without anyone changing how they work.
One inbox across every number
Every WhatsApp and Telegram chat and group, with one history per customer.
Sheets become records
Dispatch sheets, order lists and delivery notes read into records by code, linked to their source.
Answers with sources
Ask about orders, customers and payments; every fact links back to the message or record.
2. FlagPartly available now
The right person hears about the exception, instead of everyone hearing about everything.
Who is waiting
Customers still waiting for a reply, across every number, sorted by how long. Available now.
Promises tracked
Dispatch dates and payment promises made in chat, checked against your ERP and flagged before they slip. Coming.
The owner's brief
A short daily summary on WhatsApp: pending orders, dispatch due, payments overdue. Coming.
3. RecommendComing next
When something needs a decision, DataLense says what it would do and shows exactly why.
Which order to chase
The follow-ups that matter most today, with the messages and records behind each one.
Customers drifting away
Dealers whose orders slow down or whose complaints repeat, while there is time to act.
4. Draft for approvalComing next
Commercial commitments always need a person. DataLense does the typing; you do the deciding.
Replies with the facts
Draft replies that already include live stock, the agreed rate and the real dispatch date.
Orders into your ERP
A confirmed order in a dealer group becomes a draft sales order in ERPNext, Odoo, QuickBooks, Xero or Tally, posted when you approve.
Payment reminders
Polite reminders for overdue payments, with the invoice and amount, sent only after you approve.
5. Act within your limitsLater
For the routine you choose, DataLense acts on its own, within limits on amounts, customers and hours, with a full log and an off switch.
Rules you set
Which customers, which actions, up to what amount, at what hours.
Everything logged
Every action linked to its source and reversible, with a person approving anything outside the rules.
Business and personal chats live on the same phone. Each chat gets its own setting, and the cautious one is the default. AI stays off for a new workspace until you switch it on.
Messages are stored and counted for reply times and volume. Nothing is sent to AI and no files are read.
How we protect your dataCosta Pipes, São Paulo
Dealer
Payment done for invoice 2231, pls check
Received, thank you!
The infrastructure, standards and practices DataLense is built on. They describe how we build, not third-party certifications.
Read the security detailsDataLense captures the orders, rates, dispatch updates and payment promises that small and mid-sized businesses handle on WhatsApp and Telegram, keeps them next to the ERP, and shows what is pending, at risk or overdue, with the message behind every fact. It is built for manufacturers, distributors and traders worldwide, and is a product by CloudLense.
Your ERP records an order once someone types it in. Everything around it happens in chat: the enquiry, the agreed rate, the promised dispatch date, the delay, the payment follow-up. DataLense keeps that part too, so you can see what was promised, what is still pending and who is waiting, without phoning anyone.
Today DataLense reads the sheets and lists shared in your groups into records by itself and keeps them next to your ERPNext or Odoo data, so status and history are in one place. Turning a confirmed chat order into a draft order in your ERP, posted when you approve it, is the next step we are building, starting with ERPNext, Odoo, QuickBooks, Xero and Tally.
Only where you decide it may, and not today. The plan is a ladder: find, flag, recommend, draft for your approval, and only then act on routine work within limits you set, such as which customers, which actions and up to what amount. Commercial commitments always need a person's approval, every action links to its source, and there is always an off switch.
Because they will not move. Dealers, customers and the shop floor already work in WhatsApp groups and on personal numbers. DataLense works with the numbers and groups you already have, so nobody has to install anything or change how they order.
The conversations, orders and customer history captured from the numbers you connected stay in your company's workspace, with one profile per customer across numbers, so the history does not leave with the person.
In minutes. Sign in at my.datalense.app, which creates your workspace, and link a WhatsApp number by scanning a QR code. Import recent history and you can see what is pending on day one. There is no IT project and nothing to install.
Link one WhatsApp number and every order, promise and pending follow-up starts landing in one place. The follow-ups you approve come next, built on the history you keep from today.
