Use the documents people already maintain.
Index PDFs, Word (.docx), plain text, and Markdown. A configured worker watches for changes. OCR and image descriptions can be enabled for scanned pages and illustrations.
How it works
How a question finds its source.
Retrieval-augmented generation (RAG) means the assistant looks up relevant material when someone asks a question. Xillix configures that process around your team and its approved sources.
Inside the platform
What happens between the file and the answer?
Find both a phrase and what it means.
Semantic search finds passages related to the question. Keyword search helps with exact terms, and version-aware retrieval helps distinguish editions of a guide.
Match the model to the question.
The platform defaults to GPT-6 Luna for everyday questions. Configurable routing can select GPT-6.1 Sol for explicit English requests to reconcile guidance or compare multiple documents. Admins can also select a fixed model.
Decide what the document owner sees.
Customer instances have separate storage and configuration. Admins can review usage and feedback, export reports, and set up scheduled digests or alerts when email delivery is enabled.
A typical pilot
1. Define the job
Pick the audience, a document owner, and representative questions. Include a few the assistant should refer to a person.
2. Prepare the sources
Select current versions and identify duplicates or conflicting instructions. Index the approved material so relevant passages can be retrieved.
3. Review answers and citations
Ask the questions in the words employees use. Check whether each citation supports the answer, then adjust the sources or retrieval settings with the team.
4. Agree on ongoing ownership
Decide who approves new versions, how changes are tested, and who handles questions the documentation leaves open.
LuxonLeadAssist / Developer example
How does a website answer become a sales preview?
The public buyer demo sends one question and receives an answer and a sample handoff. You can inspect the same fields in the recorded response.
answer- The text the visitor sees first. The public demo answers from a short set of approved Xillix product and pilot facts.
handoff.questionhandoff.answer- The submitted question and reply used in the sales transcript. Compare them with the buyer’s exchange to catch a missing or swapped message.
handoff.pagehandoff.notification- The product page and sample email body. In the recorded example, the email names the fictional contact and includes a conversation identifier. The full exchange is in the sales record.
Talk to Xillix
Tell us about your team.
Which question comes up most often, and where do people look for the answer today?