Fluent AI Update: Q3, 2026

Quotes built by the agent are created in Epicor Kinetic, which stays the system of record for the transaction. What your sales team needs alongside it is account context: history, relationships, and open opportunities. That is the split worth understanding before you decide whether your ERP's built-in CRM covers your sales process or whether you need a dedicated CRM such as SugarAI.

Configurable approval workflows route exceptions and sign-offs based on rules you define, rather than depending on someone noticing an email. The practical gain is exception handling: approvals that fall outside the standard path get routed automatically instead of stalling. Bring your current approval bottleneck to the session and ask how it would be modeled.

No. Fluent adds an automation layer on top of Epicor Kinetic rather than replacing or rebuilding it. Your ERP stays the system of record and your existing workflows continue to run. This is the practical difference between adding automation and starting an ERP migration, which is a multi-year commitment most manufacturers are not looking to repeat.

Ask this directly during the webinar if you operate under regulatory requirements. Manufacturers in medical device, firearms, and other controlled sectors need to show who or what approved a document and when. Any approval automation used in a regulated environment has to produce a record that satisfies an auditor, so confirm the logging detail before you enable it in production.

Timelines depend on how your approval rules and pricing are currently configured. The webinar covers how to enable what shipped this quarter, which is the right starting point for scoping your own effort. Existing Fluent customers should ask about their specific environment, since configuration depth varies more than the software does.

Support depends on your Kinetic version and whether you run cloud or on-premise. Confirm your specific configuration with TCP before planning a rollout, since prerequisites differ across deployments. Bringing your version number to the session is the fastest way to get a definitive answer rather than a general one.

The session covers what is being coded now for Q4 and where to submit what you want built after that. Many of the Q3 improvements came from customer requests, so the roadmap input channel is a real one. If you have a workflow that still requires manual handling, the session is the place to raise it.

The quoting agent builds quotes inside Epicor Kinetic, so it works from the pricing structure already configured there rather than a separate rules engine. Your price lists, customer-specific pricing, and discount logic stay where your team maintains them today. This matters because duplicated pricing rules are the most common source of quote errors in manufacturing.

Reps spend less time assembling quotes and chasing approvals, and more time on the account conversation. The operational gain is in the handoffs: a quote that needs an exception moves forward on defined rules instead of waiting in an inbox. Quantify this against your own quote turnaround time before and after, since that is the number your team will feel.

Customer-specific part numbering is a standard requirement in manufacturing and distribution, where the same item carries a different number for every account. Any quoting automation has to resolve the customer's number to your internal SKU before it prices the line. Ask about your specific mapping setup during the session, since implementations vary by how the cross-reference is stored.