FAQs
Frequently Asked Questions
Have questions about Lowki.ai? We've got answers. Browse our most common inquiries below.
Lexi processes sales orders and invoices directly into Epicor Kinetic using generative AI. It reads customer emails, extracts key information, and prepares everything for your ERP — driving up to an 80% increase in order processing throughput.
Lexi is built end-to-end around the order entry workflow, not just data extraction. It's natively integrated with Epicor Kinetic, has been hardened in live production for over 20 months, and links ERP entries back to the original email conversation and attachments — giving your team full visibility and quick access when working from shared inboxes.
Lexi uses Epicor Kinetic's REST API so data passes through your existing business logic. It works within your current validations, rules, and processes rather than bypassing them.
Lexi runs as a Docker container on infrastructure managed by lowki.ai, with enterprise-grade security practices and GDPR compliance. Your order data is processed to fulfil your orders and is never used to train external AI models. We're happy to walk your IT and information security teams through our architecture in detail.
The original email and its attachments stay in your Exchange Online mailbox where they belong. Lexi adds a link from the Epicor order straight back to the email — so when a customer rings up about their order, you're one click away from their original message instead of hunting through someone else's filing system. The link keeps working as long as the email stays within the same mailbox, so your team is free to file it into whatever folders, sub-folders, or archives suit how you work.
Access follows your existing Exchange Online permissions: only users with rights to the mailbox can open the linked email from Epicor, so Lexi doesn't change who can see what. The link itself will become inaccessible if your retention policies delete the email or if it's migrated out of the mailbox — so it's worth aligning email retention to how long you want to be able to trace orders back to their source.
Lexi is designed with human-in-the-loop review at its core. Anything Lexi can't confidently process — unfamiliar customers, ambiguous part numbers, missing fields — is flagged for your team to review.
Lexi is offered on monthly billing across four tiers — PAYG, Production, Growth, and Scale — with pricing based on the number of order lines processed. All tiers include onboarding training and business-hours email support. Full pricing is available on our pricing page.
Implementation is typically completed within a day. This includes setup, Epicor integration, testing, and onboarding your team. Most customers are processing live orders by the end of day one.
Lexi has demonstrated 98% customer matching accuracy, 97% ship-to address accuracy, and 95% PO number accuracy in production environments processing more than 40,000 orders. It is designed to work out of the box with minimal setup.
No. Lexi is designed to deliver value from day one without the need for template building or ongoing training.
Today, Lexi is focused on sales order automation. We have also implemented accounts payable invoice logging and matching, with plans to expand further into finance and other back-office processes.
Lexi currently integrates with Microsoft Exchange Online. If you use another email platform, talk to us — we're actively expanding integrations.
Yes. Because Lexi works through Epicor's REST API, your existing Method Directives and Data Directives still apply. That helps ensure processing stays aligned with your current business rules and system behaviour.
Yes. We are exploring dashboards to give teams better visibility of processed orders and activity. In the meantime, your IT team can surface this data using Epicor BAQs and dashboards filtered by the integration user account.
Lexi was created to solve a real operational problem: too much time spent on manual order entry. It was built to free up teams for higher-value work while improving speed, consistency, and visibility.