From first message to order, one record.
In SilverCheckout, an order moves from first message to confirmation on one record. The customer sees every step in the conversation; your team sees the same record on the panel.
The example order's states in order: draft, cart, link, paid, recorded, being prepared.
ExampleThe states of order #1042. The last one is your order system's own status, read back into the conversation.
One example sale, step by step.
Built on SilverReply. The SilverOps team keeps the books.
The product is found inside the chat.
Customers write in their own words; products and stock come into the chat.
Example. Business: an olive oil producer. Customer: a restaurant. Product names, prices, times and numbers are illustrative.
- Customer: Hi, is the new harvest in? We need 5-litre tins for the kitchen.
10:42
- Business: Hello, it is. There are two options for kitchen use:
- Early harvest extra virgin, 5 L tinTRY 1,850.00
- Extra virgin, 5 L tinTRY 1,450.00
10:42
Example business
Olive oil producer
ItemAmount
Total
10:42Catalogue searched: 2 products. Stock checked: early harvest 5 L, 38 units; extra virgin 5 L, 112 units. Example.
Step 1 of 6
10:42
The product is found inside the chat.
Customers describe what they want in their own words. Matching products come from your catalogue and the stock figure from your own system, and nobody is sent to another page.
10:42 Catalogue searched, stock checked: 38 units. Example.
10:44
Questions get the business's own answers.
Delivery, invoicing, returns: the answers come from the knowledge base SilverReply uses, which holds the business's own information, so nothing is written twice.
10:44 Knowledge base entry used: Delivery. Example.
10:46
The cart is built from what the customer types.
The customer types "four tins". Product, quantity and total go straight onto the receipt, and nobody copies the order into a notebook later.
10:46 Cart: 1 line, TRY 7,400.00. Example.
10:47
The payment link arrives in the thread.
A link carrying the cart's total lands in the same conversation. One step replaces the IBAN messages and the wait for a transfer slip.
10:47 Link sent, order #1042 opened. Example.
next day 09:30
An unfinished order isn't forgotten.
An order that stops at payment is followed up. The reminder goes out in the same conversation, with the same cart, so the customer never starts over.
Reminded the next day at 09:30, paid at 09:41. Example.
09:42
Confirmation and the record flow from one place.
Once payment lands, confirmation follows, the order is written to your order system and stock updates. The order number and its status stay in that same conversation.
09:42 Stock down from 38 to 34, order #1042 written. Example.
Read the statement
Example. Business: an olive oil producer. Customer: a restaurant. Product names, prices, times and numbers are illustrative.
Conversation
- 10:42 · Customer: Hi, is the new harvest in? We need 5-litre tins for the kitchen.
- 10:42 · Business: Hello, it is. There are two options for kitchen use: Early harvest extra virgin, 5 L tin, TRY 1,850.00; Extra virgin, 5 L tin, TRY 1,450.00.
- 10:44 · Customer: How long does delivery to Istanbul take?
- 10:44 · Business: Orders placed before 15:00 go out the same day. Delivery to Istanbul usually takes 1 to 2 working days.
- 10:46 · Customer: Four tins of the early harvest, please.
- 10:46 · Business: Your cart is ready: 4 × early harvest 5 L, TRY 7,400.00 in total. Delivery is free. Confirm and the payment link comes straight here.
- 10:47 · Customer: Confirmed.
- 10:47 · Business: Here's your payment link: Payment link · Order #1042 · TRY 7,400.00
- 10:49 · Customer: I'll pay this evening, once accounts have signed it off.
- 10:49 · Business: Of course. Your cart and the link will be right here.
- Next day · 09:30
- 09:30 · Business: Good morning. Yesterday's order for 4 tins is still open. Same link, and we can still change the quantities if you like.
- 09:41 · Customer: Accounts have signed it off, paying now.
- Payment received · 09:41
- 09:41 · Business: Payment received, thank you.
- 09:42 · Business: Order #1042 has been recorded and is being prepared. Your order number and its status stay in this chat.
Receipt
| Item | Qty | Unit price | Amount |
|---|---|---|---|
| Early harvest extra virgin, 5 L tin | 4 | TRY 1,850.00 | TRY 7,400.00 |
Delivery: Free
Total: TRY 7,400.00
Status: Paid, 09:41; being prepared
Record
- 10:42Conversation opened.
- 10:42Catalogue searched: 2 products. Stock checked: early harvest 5 L, 38 units; extra virgin 5 L, 112 units.
- 10:44Knowledge base: "Delivery" entry.
- 10:46Cart created.
- 10:47Payment link created: #1042.
- 10:49Unfinished order queued for follow-up.
- 09:30Reminder sent.
- 09:41Payment confirmed. Written to your order system. Stock updated: 38 → 34.
- 09:42Written to your order system; stock 38 → 34.
The square in the stamp is the punch of the first coins, struck in Lydia, Anatolia.
Double entry.
Every state is written twice: once in the conversation the customer sees, once on the panel your team sees. Both tell the story of the same order.
| What the customer sees | State | What your team sees |
|---|---|---|
| What the customer seesAn answer to the question and two product options | Draft | What your team seesThe conversation opened, the catalogue searched, the stock checked |
| What the customer seesA summary of the cart: product, quantity, total | Cart | What your team seesThe cart lines and total, taken from the conversation |
| What the customer seesA payment link carrying the cart's total | Link | What your team seesOrder #1042, awaiting payment |
| What the customer seesA message saying the payment arrived | Paid | What your team seesPayment confirmation and its time |
| What the customer seesThe order number | Recorded | What your team seesThe entry written to your order system, stock updated |
| What the customer seesThe order's status, in the same conversation | Being prepared | What your team seesThe status coming back from your order system |
Mid-sale, a person.
Some sales are for your team to close. Here the customer asks for a price at volume, and SilverReply hands the conversation over to your sales team. They see the whole conversation and order #1042; the customer gets the answer in the same conversation.
- 16:28 · Customer: One more thing: we're thinking 40 tins for the holiday. Can we talk price at that volume? Panel: Handover reason: a price question at volume. Example.
- 16:28 · Business: At that volume our sales team should take it from here. They have the whole conversation and will reply in this chat shortly. Panel: Handed to: sales team. Context: order #1042, the delivery question, the 40-tin request.
- 16:34 · Sales team: Hello, sales team here. We're preparing a quote for 40 tins delivered before the holiday; you'll have it in this chat today. Panel: Replied by: sales team.
Example. In this conversation the handover reason is a price question at volume.
Each line, a different author. One record.
Here is the example order on your team's panel.
Panel · Order #1042Example
| Time | Who | What happened |
|---|---|---|
| Yesterday 10:31 | SilverGrow | A new-season follow-up went to a restaurant that ordered last season. |
| Yesterday 10:42 | Customer | "Is the new harvest in?" |
| Yesterday 10:42 | SilverReply | New-harvest question answered; two products suggested from the catalogue. |
| Yesterday 10:44 | SilverReply | Delivery question answered from the knowledge base. |
| Yesterday 10:46 | SilverCheckout | Cart created: 4 × early harvest 5 L. |
| Yesterday 10:47 | SilverCheckout | Payment link sent: TRY 7,400.00. |
| Today 09:30 | SilverCheckout | Unfinished order followed up. |
| Today 09:41 | SilverCheckout | Payment received, written to your order system, stock updated. |
| Today 14:05 | SilverCall | The customer rang to ask how invoices are issued; answered from the same knowledge base, call summary added to the panel. |
| Today 16:28 | Sales team | The 40-tin enquiry taken over, with the whole conversation. |
SilverReply, SilverCall and SilverGrow share this panel and this knowledge base, and the same SilverOps team installs all four.
Layers.
SilverReply carries the conversation. SilverCheckout keeps the order. The same team installs both.
Order and payment
SilverCheckout
Builds the cart inside the conversation, sends the payment link into the same conversation, follows up unfinished orders and records every order.
Conversation
SilverReply
The AI sales and front-desk system from SilverOps. It greets customers on WhatsApp and website chat, answers from the knowledge base and hands the conversation to your team when needed.
Your systems
stock and orders
Supply product and stock details, take the order and send its status back.
No receipt goes out behind the stockroom's back.
An order taken in the chat is written to the business's own stock and order systems. Product and stock details come from there, the order goes there, and its status comes back from there into the conversation.
The loop:
- Product and stock details come into the conversation.
- The cart is built; once payment lands, the order is written to your order system.
- Stock goes down in your stock system.
- The order status returns to the conversation.
Read, written, returned.
SilverCheckout reads from the business's own systems, writes to them and carries the status they return into the conversation.
Read
- products
- prices
- stock
Written
- the order record
- payment confirmation
Returned
- order status
Which systems it connects to is decided on the discovery call, and the SilverOps team builds the connections. If those systems are missing or scattered, the same team builds the ERP and stock side too.
Installation.
The SilverOps team keeps the books from the first line.
- Discovery call
- the SilverOps team and yours
- Covers how your orders travel today, the channels, the stock and order systems and the payment step. Price comes after this call.
- Installation and integration
- the SilverOps team
- The knowledge base and catalogue are prepared, the cart and payment step are set up, and your stock and order systems are connected.
- Operation
- the SilverOps team
- Installation doesn't close the books; the same team runs the system.
Three of the questions.
How do you take orders over WhatsApp?
The order is taken inside the conversation: the customer writes what they want, the cart is built in the chat and the payment link arrives in the same thread.
How does an order from WhatsApp reach a stock or ERP system?
Once payment lands, the order is written to your order system and stock updates; the same order appears on the panel too.
How is selling inside the chat different from an online store?
In an online store the customer comes to the shop and finishes the payment alone; selling inside the chat closes the sale in the conversation the customer is already having.
The record opens with a conversation.
Our team first maps out with you how your orders travel today; which systems it connects to follows from there.