Talo Guide
\"The degreaser from last time\": quotes from a customer's own history
How to ask Talo to resolve an ambiguous order from a customer's history, apply their discount and VAT, and leave the quote as a draft.
About the screenshots in this guide
Every screenshot in this English guide is a real capture of Talo, currently shown with the Spanish interface (the English interface is on its way). Menus, buttons and labels in the pictures are in Spanish; the surrounding text describes what each one does in English.
A regular customer writes a half-detailed order: they name a product "like last time" instead of its exact reference, and don't always say how much of everything. If you keep each customer's order history in the project (a CSV, earlier emails, or notes), Talo can resolve the ambiguity with that history instead of guessing, and leave the quote ready for you to review before sending.
Steps
- In the customer's folder inside the project, keep their order history in a
file Talo can read: an orders.csv with date, product, quantity, and price is enough. Also keep their commercial terms (agreed discount, VAT, payment terms) in a terms.md or in the project's TALO.md.
- In
TALO.md, write down the rule you want the assistant to follow when an
order is ambiguous: for example, "if an order names a product ambiguously, resolve it with that customer's history; if more than one product could match what they're asking for, say so explicitly before preparing anything".
- Paste the customer's email or message into a project conversation and ask
for the quote: "prepare the reply with the quote, using this customer's history and terms; leave it as a draft, don't send it".
- Review the answer. If the history has two products that could match what
the customer is asking for, Talo should tell you explicitly, explain which one it picked (usually the most recent) and how much the quote would change with the other one, instead of silently picking one.
- Check the quantities too: if the customer doesn't say how much they want of
something, Talo should say what quantity it assumed (usually the one from the last order) and ask you to confirm it before sending anything.
- The draft stays in the conversation, with the full breakdown of the
calculation (subtotal, discount, taxable base, VAT, and total) so you can check it before copying it into your real email.
Tip
This recipe was actually tested with a synthetic customer who had two different degreasers in their history: Talo picked the one from the most recent order, explained the alternative with its different total, applied the customer's 8% discount and 21% VAT, and left the reply as a draft without sending anything. It also flagged, on its own, that the order didn't say how much of two other products was wanted, and that using the history's prices as list price could double the discount if those prices already had it applied. Full detail in docs/evidence/casos-de-uso-2026-10-17/ inside the repository.
Keep in mind this depends on the history actually being in the project as a file: if it only lives in your head or in an external system Talo can't read, there's nothing for it to resolve. And, as with any draft, reviewing the numbers and sending it is still on you.