After SAP Bought Its Field Service Software, Coresystems Turns to AI

Coresystems AG was founded in 2006 to build modules for SAP Business One before developing pioneering field service management software that SAP acquired in a 2018 carve-out, making it a standard part of SAP’s own portfolio. The Swiss vendor remained independent and has since assembled a new AI-driven service operations portfolio: InsightLoop and InsightLoop Ticketing for medium and large service organizations, and Coresuite Designer AI for SMEs running SAP Business One. The lineup marks a renewed presence in the SAP ecosystem, this time centered on generative AI and service process automation rather than the field service software SAP now owns.

AI Built Into Service Knowledge and Support Workflows

InsightLoop is aimed at organizations handling at least 5,000 service calls a year. The product aggregates product documentation, service records and past resolutions into a single system, with the stated goal of improving first-time fix rates and reducing downtime for technicians and agents working a case.

InsightLoop Ticketing applies the same AI-first approach to support intake. Coresystems built the ticketing tool with AI embedded in the core architecture, handling triage as each ticket arrives. Every incoming request is automatically analyzed, classified and enriched with customer context and business rules, then paired with an AI-generated response draft before an agent opens the ticket. Agents still control what goes out, but the triage and drafting work happens ahead of them.

The two products connect. InsightLoop Ticketing can run standalone or link to InsightLoop for predictive support, AI-guided troubleshooting and broader service automation. Many established ticketing vendors have added generative AI features onto platforms originally built for manual triage. That industry backdrop frames how an AI-first ticketing architecture gets evaluated.

Extending the SAP Business One SME Toolset

Coresuite serves a different segment: SMEs running SAP Business One that need tools for process optimization and automation. Within that suite, Coresuite Designer has long been the tool customers use to build invoices, delivery notes and other standard documents inside SAP Business One.

Coresuite Designer AI turns that tool into a cloud-native, SaaS-ready product. A user describes the document they want in plain language, and Designer AI generates a complete template, including headers, line items and totals, with formatting and metadata fields applied automatically. Adjusting layout, fonts, spacing or color works the same way: describe the change, and the tool updates the template.

The tool runs entirely in the browser, so no desktop installation is required. Designer AI sets up the necessary data sources and registers databases against the connected SAP Business One system, then deploys the finished template directly into SAP Business One’s Fat Client or Web Client, ready for rendering, batch printing or email delivery. SAP Business One customers have historically relied on separate reporting or print-layout tools for this kind of document work, a market context into which this browser-based, natural-language design tool now enters.

What This Means for SAPinsiders

• AI moves earlier into the ticket lifecycle. Support teams evaluating tools like InsightLoop Ticketing should expect SLA and routing rules to shift toward pre-triaged, AI-enriched tickets instead of manual intake. That changes what agents actually do when a ticket first lands on their screen.
• Independent vendor status shapes evaluation criteria. SAP customers who use SAP’s own field service management, which traces to Coresystems’ 2018 carve-out, face a separate decision if they also consider Coresystems’ newer independent AI tools. Integration paths and roadmap alignment need assessment on their own terms.
• Document design shifts to natural-language workflows. As template creation in SAP Business One moves from desktop layout tools to browser-based, AI-generated design, admins may need updated governance over who can create or edit templates that deploy directly into production. Removing the desktop step also removes a review checkpoint some teams relied on.