Connect
Vigil links to the places your knowledge already lives, with the same access rights people have today.
The problem
The answer exists. Nobody can find it.
Every company has a few people everyone goes to with questions. When they are busy, on holiday or gone, work slows down or gets repeated.
The knowledge is there, spread across drives, wikis, tickets and inboxes, in several languages and years of versions. Vigil makes it usable.
One place to ask
Vigil lives where your team already works.
Slack, Microsoft Teams or email: whichever tool is the centre of your day, that is where Vigil answers. It reaches into every system behind it, so nobody has to know where the answer is stored.
MR
Marta R.09:41
@Vigil has anyone fixed the nesting crash on v12.3 for a customer before?
V
Vigil09:41 · App
Yes, twice. Both crashes came from sheet templates imported from v11 with an empty material field. Re-saving the template in v12.3 with a material assigned fixed it both times.
Ticket #4812 · March 2025Wiki › Nesting › Known issuesThread in #support-eu · Luca B.
MR
Marta R.09:41
Has anyone fixed the nesting crash on v12.3 for a customer before?
V
Vigil09:41
Yes, twice. Both crashes came from sheet templates imported from v11 with an empty material field. Re-saving the template in v12.3 with a material assigned fixed it both times.
Ticket #4812 · March 2025Wiki › Nesting › Known issuesThread in #support-eu · Luca B.
Hi Marta,
Yes, twice. Both crashes came from sheet templates imported from v11 with an empty material field. Re-saving the template in v12.3 with a material assigned fixed it both times.
Ticket #4812 · March 2025Wiki › Nesting › Known issuesThread in #support-eu · Luca B.
How it works
Four steps.
Organise
It reads documents, tickets and conversations and turns them into one searchable picture of what the company knows.
Answer
People ask in Slack, Teams or email, in plain language, and get an answer with its sources attached, so they can check it.
Learn
Corrections and new answers flow back in, so the next person gets a better answer.
Where it’s used
In practice.
Industrial software ↗
Support engineers find past fixes and customer-specific configurations in seconds, and new hires get up to speed without shadowing for months.
Precision manufacturing ↗
Operators and planners find the right specification, setup note or past job without asking around.
Machinery ↗
Field engineers get model-specific guidance and service history on site, and every repeat fix becomes shared knowledge.
Consumer technology ↗
Product and community teams find past decisions and their context as the company grows.
Deployment & data
The details.
- Where it lives
- Inside the tool your team already uses every day: Slack, Microsoft Teams or email. One place to ask, whichever system the answer is stored in. No new app to open.
- Typical sources
- Shared drives, wikis, ticketing and support systems, CRM, product documentation and email archives.
- Access
- Respects the permissions you already have: people only get answers from sources they can already open.
- Answers
- Every answer shows where it came from, so people can verify it and trust it.
- Hosting
- Runs in a European cloud or on your own servers, and can run on Altiera so no data leaves your environment.