Stock and price replies from Jurnal, approved by customer service
When a customer asks on WhatsApp whether something is in stock and what it costs, Sambung prepares the reply from today’s stock in Jurnal and your price list. Customer service approves or edits it, and only then is it sent.
Biissa team · Updated 16 November 2026
In short
- Before: customer service asks the warehouse in a group chat and looks up prices in a spreadsheet while the customer waits.
- With Sambung: the reply is ready, with stock from Jurnal and the price from your price list.
- Stock, prices and totals come from your systems, worked out by code, never guessed by the AI.
- Customer service approves or edits every reply before it is sent.
The job today
In wholesale, building materials and spare parts, many sales start with a question on WhatsApp: is it in stock, and how much for this many? Answering means checking stock with the warehouse and finding the right price for the quantity in a spreadsheet.
- The customer waits while the answer is put together.
- Prices get quoted from an old file.
- In busy hours replies slow down, and a slow reply can lose the sale.
How it runs with Sambung
This is an example, not a customer story.
A question comes in
The customer asks on WhatsApp
For example: “Is the 40 kg cement in stock? How much for 100 sacks?”
Before the AI reads it
Names become codes
The customer’s recorded name is replaced with a code, and the step is logged.
From your systems
The reply is prepared
Stock is read from Jurnal and the price for that quantity from your price list, and the total is worked out by code.
Before anything is sent
Customer service approves or edits
Anything the code could not settle, such as a product name with two matches, is flagged.
After approval
The reply is sent
It is logged with the stock and the price it used.
What code settles, and what a person checks
- Which product the customer means
- Settled byCode
- HowMatched to Jurnal, with a list of the names your team uses
- Stock
- Settled byJurnal
- HowRead from Jurnal when the question arrives
- Price and total
- Settled byYour price list
- HowThe price for that quantity, with the total worked out by code
- The wording
- Settled byThe AI
- HowWritten in your tone, from the facts above
- The final yes
- Settled byCustomer service
- HowEvery reply is approved or edited before it is sent
| Settled by | How | |
|---|---|---|
| Which product the customer means | Code | Matched to Jurnal, with a list of the names your team uses |
| Stock | Jurnal | Read from Jurnal when the question arrives |
| Price and total | Your price list | The price for that quantity, with the total worked out by code |
| The wording | The AI | Written in your tone, from the facts above |
| The final yes | Customer service | Every reply is approved or edited before it is sent |
What you need to start
- Jurnal (by Mekari) for stock, and your price list in Excel or Google Sheets.
- A WhatsApp Business number your customers already message.
- A person in customer service who approves the replies.
- A data processing agreement, signed by a director, before we read any customer chat.
Common questions
Does it answer customers by itself?
No. Every reply waits for someone in customer service to approve or edit it. The AI prepares the reply; a person sends it.
Where do the prices come from?
From your own price list for that quantity, with the total worked out by code. The AI does not set prices.
What if the stock in Jurnal is not up to date?
The reply uses what Jurnal shows when the question arrives, so it is as current as your Jurnal. Customer service can edit the reply before it is sent.
How do we start?
With a free first chat, then Cek Alur Kerja: a free workflow check of about 10 working days. A test on past questions from your customers comes before a 4-week pilot.