Quote / confirm order
Price an order from Inchat's own fixed sample catalog, using the prebuilt Factory WhatsApp order template's questions, then optionally record it and send a receipt.
Quick start
- Go to Automate → Workflows, click New workflow, and pick the prebuilt Factory WhatsApp order template.
- Its Ask a Question steps already save the product, quantity and destination where this step reads them.
- It already has both Quote / confirm order steps: a preview, then one with Confirm the quoted order on.
- Between them, a question shows the quote summary and asks the customer to confirm.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- A hand-built Ask a Question step cannot feed this one — its Variable box turns dots to underscores. Use the prebuilt Factory WhatsApp order template.
- Turning Confirm the quoted order off still speaks to the customer when the catalog cannot price the answers — the toggle only silences a clean quote.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Quote / confirm order under Add Steps.
Before you start
- An owner, admin or agent can add this step and save the workflow. Only an owner or admin can publish it, and publishing is what makes it run on live conversations.
- Building and running workflows depends on your plan; see pricing.
- A set of earlier Ask a Question steps that collect the product, an optional complement, a quantity and a shipping destination into
order.productId,order.complementId,order.qtyandorder.destination. - This step reads those fields; it does not ask for them itself.
Set up
- Build the ordering questions first: Ask a Question steps that save into
order.productId,order.complementId(if the product needs one),order.qtyandorder.destination. - A hand-built question cannot do this — its Variable name box turns every dot into an underscore, breaking the path this step reads. Start from the prebuilt Factory WhatsApp order template, whose questions already write the right paths.
- The template already has Quote / confirm order after them with Confirm the quoted order left off, to compute the total for a confirmation message — the totals are then available as
{{quote.grandTotal}}and similar fields. - Next comes a question that shows the computed quote and asks the customer to confirm.
- Then comes a second Quote / confirm order step, this time with Confirm the quoted order turned on, on the path where they agreed.
- Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.
Fields
- Confirm the quoted order
- Off: only compute the quote and make its numbers available to later steps under the Quote group in the Variable menu. On: also record the order and send the customer a receipt.
- Default: off
How it works
- The step reads
order.productId,order.complementId,order.qtyandorder.destination— whatever earlier steps, typically a run of Ask a Question steps, saved there. - It prices them against a fixed, built-in catalog of products, complements and shipping zones.
- This catalog is not something a workspace configures; it is the same one for every workspace running this step.
- With Confirm the quoted order off, a successful quote is written to the run as the product name, quantity, destination, shipping cost and grand total.
- A ready-made summary line is written too, all readable by later steps and conditions.
- Nothing is sent to the customer in that case.
- That silence only holds when the quote actually computes. An answer combination the catalog cannot price sends the customer a message regardless of this toggle — see the next point. The toggle only silences the success path.
- With Confirm the quoted order on, the same computation runs, and the order is additionally recorded as a line-item intent.
- A receipt confirming the recorded order is then sent to the customer through the ordinary send path.
- Recording the order always saves it inside Inchat first. Forwarding it onward to a connected order-management system happens only for a workspace that has that connection enabled; a workspace without it still has the order saved here, just not pushed anywhere else.
- Several answer combinations are ones the catalog cannot price: required fields still missing, an unrecognised product or destination, a quantity too small or oddly shaped, a product and complement that cannot be paired.
- None of those fail the step.
- The customer instead receives a message naming the problem and pointing at Need a person, sent regardless of the Confirm the quoted order toggle, even with it off.
- Need a person is a menu option this text assumes exists. It is the label the prebuilt "Factory WhatsApp order" template's own Ask a Question steps use, not something this step adds on its own.
- A hand-built flow whose questions have no option by that name points the customer at a button that is not there.
- Recording the order can itself fail — a write error — even when the quote computed cleanly. That failure also reaches the customer as an apology naming that a teammate will follow up, rather than silence.
When it fails
- The required answers are missing — no product, quantity or destination on the run yet, including a preview run placed right after only the first question or two.
- The step still reports success internally, but sends the customer the catalog's own "required" message together with the Need a person hint, with Confirm the quoted order on or off, and with nothing recorded.
- The product, complement or destination named does not exist in the catalog, or the product and complement cannot be paired, or the quantity has no matching price break.
- The same pattern applies — a specific message naming the problem, plus Need a person, nothing recorded.
- Recording a confirmed order fails — a write problem after the quote already computed successfully: the customer is sent an apology saying a teammate will follow up, and the step reports failure.
- This step has no failure branch of its own; whatever happens, the run continues to the next step in the flow. The customer-facing message above is this step's way of surfacing a problem, not a branch an author configures.
- The reason, when one is logged beyond what the customer saw, is in the workflow's Activity tab, under Execution log, on this step's line.
Limits
- The catalog is fixed and built into the product — a small, specific set of products, complements and shipping destinations. It is not a per-workspace product catalog like the one Send Products (WhatsApp catalog) reads from Commerce Manager, and a workspace cannot add its own products to it.
- It only ever prices the four fields it reads — product, complement, quantity, destination — it has no concept of multiple line items in one order.
- With Confirm the quoted order off, a cleanly computed quote sends nothing to the customer. Pair it with a Send a Message step that reads the quote fields if the point is to show them a confirmation prompt.
- A quote the catalog cannot price sends a message regardless of this toggle. A preview run placed after only some of the ordering questions are answered can speak to the customer before you meant it to.
- An unrecognised answer combination is never a silent failure to the customer — they always get a specific message and the Need a person hint.
- But it is also never a branch a workflow author can react to differently — the same message shape covers every kind of mismatch.
- The Need a person hint in that message names a menu option, not a feature of this step. It only exists where the ordering flow's own Ask a Question steps define an option with that exact label, which is true of the prebuilt "Factory WhatsApp order" template and not guaranteed anywhere else.
Best practices
- Add a Need a person option, with that exact label, to every question in the ordering sequence — this step's own error text assumes it exists, but nothing creates it for you outside the prebuilt template.
- Without it, a mismatched answer points the customer at a button they cannot find.
- Only place a preview (commit off) step after all of the ordering questions have been answered.
- Placed earlier, it still speaks to the customer with the catalog's "required" message and the Need a person hint, not silence.
- Read the quote's ready-made summary line, available in the Variable menu's Quote group, rather than rebuilding the same numbers by hand.
Use cases
- A pre-built ordering flow: ask product, complement, quantity and destination, quote the total, confirm, and record the order once the customer agrees.
FAQ and troubleshooting
- Does this step work with our own product catalog?
- No — it prices against a fixed, built-in catalog, not one your workspace configures. Send Products (WhatsApp catalog) is the step that reads your own Commerce Manager catalog.
- What happens if the customer's answers don't match anything in the catalog?
- They receive a message naming the problem and a Need a person option — nothing is recorded, and the step does not fail the run.
- Does turning off Confirm the quoted order still tell the customer the price?
- Only for a quote the catalog can actually price. Then it computes into fields for later steps to use and says nothing itself, and you need a Send a Message step after it to show the customer anything. A quote the catalog cannot price — missing answers, an unrecognised product, a bad pairing — sends the customer a message either way. This toggle only silences the success path.
- If the order is recorded here, does it show up in our other order-management system?
- Only if this workspace has that connection enabled. The order is always saved inside Inchat regardless; forwarding it onward depends on that separate setup.
Reading this with an AI assistant? Plain Markdown version.