Solution

A Solution captures one fix in a few lines of text: a symptom, its cause, and what resolved it. Most solutions start in records your organization already keeps: service tickets, emails with customers, and the notes Technicians write after a job. InSkill reads those records, finds the fixes that keep coming up, and turns each one into a solution for your team to approve. A solution is smaller than a Field Card, which adds photos and several causes, and smaller than a Task, which guides and records the work.

Once published, a solution is the copilot's approved answer. When a Technician asks a matching question, InSkill GPT gives the solution's verified wording instead of composing a new answer. See Using Solutions with InSkill AI.

Solutions are kept on a copilot's Solutions tab in the Copilots portal. For the tab and its controls, see Solutions.

Where Solutions Come From

Source	What goes in	How it becomes a solution
Field records	Service tickets, call logs, and job records	Imported with the type Ticket. InSkill proposes solutions from them.
Emails	Support and customer email threads	Imported with the type Email.
Field notes	Technicians' notes and visit reports	Imported with the type Report.
A conversation in the field	A fix a Technician has just worked out with InSkill GPT	The Technician says "Save solution". See About GPT Agents.
An expert	A fix someone knows but nobody has written down	Written by hand on the Solutions tab. See Creating New Solutions Manually.

From Raw Records to Solutions

Raw records are noisy. The same fault is reported many times in different words, and many records are about scheduling, shipping, or warranty rather than the fix. InSkill works through them in stages:

Import: the records are exported to an .xlsx or .csv file, one record per row, with an id and its content. An email's question and reply can go in separate content columns, such as content_description and content_reply. Filling in model, variant, or asset links a record to the machine it is about.
Filter: records with no reusable technical content are set aside: very short entries, administration and coordination, logistics and stock, and policy, warranty, claims, or pricing.
Score: each remaining record is scored on its reusable technical value, from a complete fix down to a partial clue.
Cluster: records about the same problem are grouped and their duplicates combined, so dozens of reports of one fault become one solution backed by all of them.
Propose: each strong cluster becomes a New solution, with its source records attached.
Approve and publish: a person reviews the wording, merges or deletes proposals, then clicks Approve and Publish. Nothing generated reaches a Technician until someone has approved it.

For the file format, the scoring scale, and the import settings, see Importing Solutions.

Solution Types

Type	Use for	What it holds
FAQ	A common question with a short answer	The question and its answer
Troubleshooting	One symptom and its fix	Symptoms and indicators, the cause, and the corrective action, with safety notes, tools, and parts when they apply
Procedure	A short, repeatable job	The steps of a maintenance, setup, or commissioning job. Work that needs recorded results or sign-off belongs in a Task.
Reference	Values and guidance to look up	Specifications, configuration settings, application guidance, and field-proven best practices

What Every Solution Has in Common

Status: each solution moves from New to Approved to Published, and Unpublish takes it out of use. See The Solution Lifecycle.
Sources: a solution generated from imported records keeps a link to each record behind it, so a reviewer can check the evidence. Solutions created in InSkill show User as their source.
Who sees it, and when: User Levels, Visibility (App, Web, and InSkill GPT Answers), and Dependencies control who sees a solution and for which machines it is used. A fix for one configuration is used only for assets that match it. See Dependencies.
Parts: part numbers linked to the fix are suggested when the fix is identified.
Language: solutions are translated automatically into each language enabled in Account Settings.

Keeping Solutions Useful

The Insights view shows where the solutions came from and which categories have few of them. Import more records for the thin areas. See Insights Tab.
When a solution needs photos or covers several causes, move it up to a Field Card. When it needs recorded results or sign-off, move it up to a Task.

To decide between a Solution, a Field Card, and a Task, see When to Use.