ERP & CRM questions, answered

Through Epicor Kinetic’s own system interfaces for reading and writing records, plus browser-based screen automation for anything those interfaces don’t cover. On the read side it can pull up jobs, quotes, POs, routings, part records, and job costing in plain English, in seconds. On the write side, every change goes through the approval gate: Epic One previews exactly what it’s about to modify, an authorized person on your team approves it, then it executes, verifies the result, and logs the whole thing. Nothing writes to Kinetic on its own.

Yes. E2 JobBoss² doesn’t need an API integration at all. Epic One operates it the way a person would, through dedicated login credentials, reading fields on screen, navigating between screens, and holding a session over time the same way a staff member does. That means it works with JobBoss² as it exists in your shop today, without a vendor-side integration project or a request to your ERP provider to expose new endpoints.

Yes. Epic One connects to CRMs like Salesforce, HubSpot, and NetSuite’s CRM module alongside your ERP, so a question about a customer can pull from both at once: their open quotes and job history from the ERP, and their contact history, deal stage, or account notes from the CRM. It can also work with customer-facing portals your team logs into for account or order status, the same way it works with your ERP screens. See the full integrations list for specific systems.

Reading is unrestricted, within your own login’s permissions: purchase orders, work orders, routings, part records, quotes, invoices, customer and vendor records, shipments, and job costing are all instantly askable. Writing, meaning anything that changes a record, like updating a due date, closing an operation, or creating a PO, only happens through the approval gate. Epic One can propose the write and show you precisely what will change, but a person has to say yes before it touches the record.

No. Your ERP stays the system of record, and nothing about how it works changes. Epic One sits on top of it as a layer your team talks to instead of clicking through screens to find the same information. Your existing reports, workflows, and the ERP itself keep running exactly as they do today; Epic One just makes what’s already in there faster to get to and act on.

Epic One never executes a change silently. It builds the proposed update, shows the exact before-and-after to a person your company has authorized to approve it, and waits. Nothing happens until that person confirms. Once approved, Epic One executes the change, verifies it landed correctly, and writes an entry to the audit log. If it isn’t approved, nothing in Epicor moves.

Yes, over text message. A machinist or floor lead can text Epic One a question, like the status of a job or a part spec, and get an answer sourced from the ERP without opening a terminal or logging into anything. It works the same way for reporting an issue or asking for something to get relayed to the office. No app install and no workstation required.

They carry over unchanged. Epic One connects using each person’s own ERP or CRM login, so it can only see and do what that individual’s existing permissions already allow. Nobody on your team gains access they didn’t already have, and your admin keeps controlling access the same way, through your ERP’s own user setup.

There’s no server for your team to stand up and no phased rollout to plan around. Once your instance is set up and connected to your ERP, most shops get their first real answers, like a live quote status or an overdue PO list, within the first week. Teaching it a specific process or turning on write access for a workflow typically comes after that, once your team has seen it work on read-only questions.

Each customer gets a dedicated server, so your data is never pooled with another company’s. ERP and CRM credentials are stored encrypted, every write goes through the approval gate described above, and every action, read or write, is logged to an audit trail your company can review. AI processing runs on Anthropic’s commercial API, which doesn’t train on customer data. See the full security details.

Yes. Have someone on your team record themselves doing the process once, in the ERP, screen and all. Epic One turns that recording into a written, numbered procedure with screenshots, the kind of document you’d hand a new hire. From there, it can also learn to run that same procedure itself, rehearsing it in a sandbox and running the first live attempt under supervision before it’s trusted to do it unsupervised.

Epicor Kinetic and E2 JobBoss² are the deepest integrations today, alongside CRMs like Salesforce and HubSpot and ERPs including NetSuite, SAP Business One, Dynamics 365 Business Central, Acumatica, Infor CloudSuite, and Sage. If your shop runs something that’s not on that list, tell us what it is when you request your instance. Most of the time, if your team can log into it, Epic One can be taught to work inside it too. Full breakdown on the integrations page.

The same approval gate applies, just across multiple records at once. Ask it to update a batch of due dates or close out a set of completed operations, and it runs a dry run first, showing you the full list of records and exactly what will change on each one. Once you approve the batch, it executes the updates, verifies each one landed, and logs the entire run, so a bulk change is never a black box.