Technical overview
Xillix combines custom NetSuite reporting work with three distinct Luxon products. This public overview explains the product boundaries and the technical questions that must be answered without exposing private infrastructure details.
NetSuite reporting
A dashboard may use one approved saved search or combine several approved reporting outputs. The route depends on the customer environment and the question the screen must answer.
Agree on the decision, audience, KPI meaning, and acceptable refresh timing before choosing a visual.
Inspect the saved searches, reports, exports, fields, timestamps, and business rules the customer can make available.
Document status definitions, joins, filters, historical comparisons, and exceptions with the customer reporting owner.
Present the approved result in a browser-based dashboard or display format and validate it against source reporting.
Luxon products
The product pages describe current user-facing behavior. Exact integrations, storage, providers, and access controls are confirmed for the selected deployment.
Use: employees ask questions against approved internal content and review source references where the configured content supports them.
Technical path: approved documents or content are prepared for retrieval, relevant material is selected for a question, and a response is generated for the user.
Use: website visitors ask questions based on approved customer-facing content and can follow configured next steps.
Technical path: an embedded website client sends a visitor question to the configured service, which retrieves relevant approved content and returns the response.
Use: teams combine AI-assisted conversations with human review or handoff where the configured workflow supports it.
Technical path: conversation state, approved knowledge, routing rules, and agent actions are brought together for the scoped use case.
Architecture decisions
The same answer is not correct for every Xillix service. The table marks the decisions that shape the final design.
| Decision | Reporting projects | Luxon products |
|---|---|---|
| Source of truth | Customer-approved saved searches, reports, exports, fields, and business definitions. | Customer-approved documents, website content, knowledge, and workflow configuration. |
| Refresh or update behavior | Depends on the approved source, access method, data volume, and operational need. | Depends on how approved content is supplied, indexed, or synchronized for that product. |
| User surface | Browser dashboards for wall displays, monitors, tablets, or manager workstations. | Internal question-and-answer interface, website widget, or conversation workspace. |
| Human review | Customer owners validate KPI definitions, mappings, and results against trusted reports. | Users review important answers and teams define when a conversation needs human handling. |
| Security controls | Access, hosting, retention, logs, backups, providers, and contractual controls require a deployment-specific review. | |
Practical limits
A customer environment may require a saved search, scheduled export, approved API path, or another reporting method. Discovery determines what is usable.
Refresh timing is set by the approved source and business requirement. Some decisions need frequent updates; others do not.
Source citations, mappings, and customer validation improve reviewability. They do not remove the need to verify important business or AI-assisted outputs.
Evaluation input
A useful technical conversation starts with the expected user, approved data, decision cadence, access boundaries, and evidence needed to trust the result.
Share the product or reporting objective, the approved inputs you expect to use, and the controls your organization needs to review.
Contact Xillix