From the first order to the next reorder.
In plain words: your customers order by WhatsApp and by purchase order. KeelSG is built to turn those orders into draft orders your team confirms, and keeps every buyer on one customer record so your team knows who to follow up and when. Two modules, one system: Orders and Customers.
Taking pilot customersOrders is in pilot: entered by hand today, with automatic reading not switched on. The Customers module is available today.
- Every order in one listWhat needs review, and what is waiting on whom
- Your SKUs, units and price listsCustomer, tier and default prices, applied by rules
- A person confirms every orderThe AI never confirms, prices or messages a customer
- One record per customerEvery order, call and deal on the same customer
Four ways an order goes wrong.
If two of them happen in your business, keep reading. It does not matter what you sell. What matters is that customers order by message and by purchase order, and somebody retypes it.
An order arrives on WhatsApp, and somebody types it again into a spreadsheet or an invoice.
Every retype is a chance to turn a 12 into a 21, or a carton into a piece.
Purchase orders arrive as PDF and Excel files, each in the customer's own layout.
So somebody reads each one line by line and keys it in again.
The right price depends on who is ordering, and the person keying it in has to remember.
Tier prices and special customer prices live in one person's head, or in a spreadsheet only they understand.
An order goes missing between the chat, the inbox and the warehouse.
Then the customer asks where it is, and nobody can find the message it started from.
- You take a handful of orders a week. A spreadsheet is faster and cheaper. Come back when retyping orders is somebody's whole morning.
- You want the AI to confirm orders or reply to customers by itself. It will not. It is built to read and draft, and a person confirms. We would rather you found that out here than in month three.
- You need accounting, tax invoices or payments. KeelSG does not do those. Its operations are orders and customers. Orders export in four formats for the systems that do the rest.
From the message your customer sent to an order your team confirmed.
Built to read the order for you.
A WhatsApp message in plain English, or a purchase order as a PDF, XLS or XLSX file. Reading is built to pick out the items, quantities, units and delivery date, match the sender to a customer, and build a draft order with every line shown beside the words it came from.
- WhatsApp text and PDF, XLS and XLSX purchase orders
- Sender matched to a customer, or held for a person to pick
- Duplicates flagged and linked, never thrown away
Hi, pls send 20 ctn rice 5kg and 12 btl soy sauce 1L for Thu. Thanks
- Jasmine rice 5kg20 ctn
- Soy sauce 1L12 btl
- Requested dateThursday
Needs review
Every line is priced from your own lists.
Your SKUs, the units you sell them in, and your default, tier and customer prices. Each line takes the customer's own price first, then their tier price, then your default. The AI never sets or changes a price, and a price override needs a second person to approve it.
See catalogue and pricing
- Customer priceUsed
- Tier priceSkipped
- Default priceSkipped
Priced by rule, not by the AI
A person confirms it, and the order is on record.
Your team checks each draft, asks the customer when something is unclear, and confirms. Each step after that is recorded with who made it and when. A short WhatsApp update to the customer is built, and is switched on once WhatsApp is available.
See the order desk
Two lines matched. Delivery date read as Thursday. Nothing is confirmed until you confirm it.
One flow, from order to customer
An order arrives, becomes a confirmed order, and the buyer is already a customer whose history drives the next follow-up.
The buyer is already a customer.
Orders and Customers are one system, so there is no second customer list to keep in step. Customers is the CRM side of KeelSG: leads, deals, activities, campaign planning and dashboards. It is live today, and confirmed orders land on the same customer records.
See CustomersAvailable today
Customers today
- Accounts and contacts: the customer records your orders land on
- Leads, deals and a sales pipeline in your own stages
- Calls, meetings, notes and tasks on the customer
- Segments and campaign planning, with the audience previewed
- Lead scores worked out from your own criteria, with every factor shown
- Dashboards and reports that show their arithmetic
Arrives with Orders
Customers, with their orders
- Every order on the customer's timeline, next to calls and deals
- Order value on the customer record for the last 30, 90 and 365 days
- Customers grouped by tier, with their buying patterns
- A list of customers who look due to reorder, with the numbers behind it
- Orders linked to deals, so sales and orders tell one story
Reorder suggestions are a list for your team to act on. Nothing is sent to a customer from them. The assistant that drafts follow-ups is built and stays off until we have set up and checked the AI provider for your workspace. It drafts for a person to approve, and it does not send.
The controls underneath.
Access is enforced at the database, privileged actions are recorded where nobody can edit them, and you configure how long each class of data is kept. We are Cyber Essentials certified (ICT Vendor), and keelsg.com has had an independent penetration test. That test covered the site as it stood on its dates, before the order features were added. The security page sets out both, with their scope and dates.
See how access and records workEnforced at the database
A user who types another record's ID into the address bar is denied at the server.
A reason for every field
Each personal data field carries a recorded purpose, basis, retention class and visibility.
An audit nobody can edit
Admin changes, AI actions, exports, deletions and two-step sign-ins each write an append-only event.
Your data is yours. Take all of it out, any time, in four formats.
KeelSG keeps its own records and works with nothing else connected to it. Customer records export today, and orders export the same way once the Orders module is live for you. A system that only works when it is plugged into four other products is not independent, it is a hostage arrangement.
The Four Formats
All four carry the same permitted records and the same fields, each with a documented schema, so the file opens in whatever your accountant, your analyst or your next system expects.
Export whatever you are looking at
Filter a set of records on screen, choose CSV, XLSX, XML or TSV, and take it. All four carry the same permitted records and the same fields, each with a documented schema, so the file opens in whatever your accountant, your analyst or your next system expects.
Every export leaves a record
Who asked for it, which filters were applied, which fields, how many rows, which format, a checksum, when it was created and when it expires. The audit record does not contain the personal data itself. If somebody walks out with a customer list, that is a question with an answer.
Exports are made safe to open
Cell content starting with an equals, plus, minus or at sign is neutralised so a spreadsheet cannot execute it, while the value stays readable.
Open Interfaces
For Customers, if you do want it to talk to another system. Which systems, in which direction, carrying which fields, is scoped and built with you during setup. In its first version, Orders connects to nothing outside the product.
Integrity
There is no logo wall here. Anything we have not built and verified end to end for a real customer is not a claim we will make on a website.
Straight answers
Before you ask for a pilot.
Is the Orders module available today?
It is in pilot, and we are taking pilot customers. Today your team enters each order by hand. A pilot already gives you one list of every order and why it waits, the customer's own price applied, a second person on any price change, and a checked order from draft to fulfilled. Reading orders automatically from WhatsApp and from files is built and not switched on. The Customers module is available today.
Does the AI confirm orders or reply to customers on its own?
No. It is built to read a message or a purchase order and propose a draft. A person on your team checks it and confirms it. The AI does not confirm, cancel, set a price, create a customer or send a message. Customer updates are built to go out only when a person moves the order on, and only from templates you approved.
What kinds of orders is it built to read?
In the first version: WhatsApp messages written in English, and purchase orders as machine-readable PDF, XLS and XLSX files. It does not read voice notes, other languages, or scanned and handwritten documents. When it cannot read something, it is built to say so, and your team can still open a manual draft.
What does it not do?
We sell it for orders and customers. It does not issue tax invoices, take payments or keep your accounts, and it does not connect to accounting, ERP or inventory systems today. The product also has stock, delivery and quotation screens. They are outside the standard pilot, and are switched on only if your written quotation names them. Orders export in CSV, XLSX, XML and TSV for the systems that do the other jobs.
Why are orders and customers in one system?
Because the companies that order from you are the companies you sell to. A confirmed order lands on the customer's record, next to calls and deals, and the record shows what they buy and how often, so your team knows who is due a follow-up. Customers also covers leads, deals, activities, campaign planning and dashboards, and it is available today.
How much does it cost?
The Orders module is quoted for each pilot customer, in writing, before any work starts. We have not published a price. Book a free demo or ask about the pilot, and the quotation will say exactly what is included.
What support do we get?
Support runs Monday to Friday, 9am to 6pm Singapore time, by telephone and teleconference. Email is monitored 24 hours a day, 7 days a week. The three channels are email, telephone and this page. What sits inside your support scope, as opposed to new work, is written into your agreement before you sign it.
How is our customer data handled?
Access is enforced at the database, so a user cannot reach a record they are not permitted to see. Every personal data field carries a recorded purpose, basis, sensitivity, retention class and visibility. Privileged actions, AI actions, exports, deletions and two-step sign-ins are recorded in an append-only audit trail. You configure how long each class of data is kept, and you can export your records at any time in four formats.
What if a customer's message tries to trick the AI?
Text arriving from outside, in a customer message, a purchase order, an imported email or a note, is treated as data and never as an instruction. A message written to manipulate the AI into revealing something or doing something does not get to.
Thirty minutes, and you leave with three answers.
The Orders module is taking pilot customers. If the honest answer is that you do not need it yet, we will say so, and asking will have cost you nothing.
Bring three things
- A few real orders, as they arrive today.
- Your product and price list, in whatever form it is in.
- Who takes and confirms orders now.
Leave with three answers
- Whether the pilot fits.
- What we would set up, and how.
- What it would cost, written down.