Turn the request into identified items
Zild supports implementing WhatsApp quoting workflows connected to WinThor. Begin the pilot with a defined set of customers, products and commercial terms, and have the responsible team validate available operations in the installation. The agent organizes the request, queries the ERP and prepares a quote under configured rules.
A message such as “I need ten boxes of the same material” does not yet define an order line. Confirm customer, product code, packaging, quantity, unit, branch and delivery location. If multiple matches exist, present options or route for review. Do not guess important commercial data.
Prepare access and define available operations
WinThor connector Docs describe an HTTPS URL, user login and original password; Zild obtains a session token from that login. Ask the administrator for an integration user with permissions appropriate to the pilot. Credentials belong in connector configuration, not customer messages.
Confirm available reads and writes in the deployed version. Test customer, product, stock and commercial terms separately. Saving the connector does not prove every operation works. Start with quote preparation and review; enable writes only after checking the identifiers, responses and permissions required by the workflow.
Keep pricing under verifiable rules
Price should come from the authorized table and terms for the customer, branch, product, quantity and payment period. Record the query source and validity. The agent can explain the breakdown and request an exception; it must not invent a discount to finish a conversation. Route terms outside delegated authority to an approver.
Synthetic example excluding taxes, freight and other costs: an item sold for BRL 100 with BRL 70 cost has a 30% gross margin on revenue. A 10% discount lowers price to BRL 90 and margin to 22.2%: (90 − 70) ÷ 90. Margin and markup are not interchangeable. In the actual process, use finance-approved margin definitions and cost components and calculations from the responsible system.
Separate queried stock, reservation and delivery commitment
Queried stock can change before a customer accepts. Show when availability was checked and which terms still need confirmation. Physical stock, available balance and reserved quantity are different concepts; confirm which fields the integration returns.
Do not promise a delivery date solely because stock exists. Check fulfillment branch, picking, transport and operating restrictions through the defined workflow. If the customer changes quantity, packaging or delivery location, revalidate affected terms. Commercial approval does not replace logistics confirmation.
Preserve versions and prevent duplicate orders
Link the conversation to the customer and quote identifier. Each material change should produce a distinguishable version with items, terms, validity and approval owner. Acceptance must reference the correct version. A “yes” in an old conversation is insufficient to accept revised terms.
Define a stable business key for each create action in the integration layer according to actual available capabilities. After a timeout, query the result before retrying. Confirm the identifier returned by the ERP and distinguish prepared, reviewed, sent, accepted and converted states. WhatsApp delivery confirmation is not commercial acceptance or order creation.
Evaluate commercial quality and operating effort
Test ambiguous products, incompatible units, customers without valid terms, discounts beyond authority, changed stock, expired quotes, duplicates and ERP outages. Compare items, quantities, price, margin, version and created-record counts against expected results. Use authorized contacts and test data.
Measure cost per correct quote, preparation time, human reviews, discrepancies and rework after acceptance. Track the handoff to an order without attributing every conversion change to AI. Before scaling volume, also validate templates, contact permission and WhatsApp channel costs with its administrators.
Build an assessment using your numbers
Gather this information to scope the work with Zild. During the conversation, we assess integrations, owners and how to measure outcomes.
- A financial process and its owners
- Current costs, volume and review time
- The correct outcome and approval limits
Describe the process in the form; samples and documents can be prepared later without confidential data.
The form opens with this guide’s title. You can edit everything before sending.