Conversational artificial intelligence
SANIA uses language models to understand naturally phrased requests and generate conversational answers.
- Natural-language questions
- Answers built from context
- Different engines possible by configuration
TECHNOLOGY
An architecture that connects AI, business content and screens
SANIA combines a visible interface in the physical space with conversational artificial intelligence and the organization’s own knowledge.
PRINCIPLE
Technology should remain at the service of the use case
For visitors, the experience should remain simple: ask a question and receive a relevant answer. Behind that interaction, SANIA connects the interface, voice or touch input, the conversational engine and the business information supplied by the organization.
The architecture can evolve according to the project. The goal is not to impose a single model, but to select components that fit the actual environment.
Organization-specific knowledge
Relevance also depends on the business information made available. SANIA can use a knowledge base populated with different documents and content supplied by the organization.
- Specific business information
- Client-provided documents and content
- Updates according to the organization’s processes
Voice and touch
Interaction can be voice-based and, depending on the configuration, touch-based. The interface should be chosen according to noise, hardware, traffic and audience needs.
- Voice interaction
- Touch interface depending on configuration
- Ergonomics adapted to the site
Compatible screens and kiosks
SANIA can be deployed on different compatible screen and kiosk formats. Hardware selection depends on location, readability, acoustics and installation constraints.
- Multiple formats
- Deployment in physical spaces
- Hardware selected according to the project
Sandisplay integration
SANIA integrates with the Sandisplay digital signage ecosystem. This makes it possible to design projects where broadcast information and conversational interaction are considered coherently.
- Digital signage + conversation
- ALLSAN ecosystem
- Coordination according to the chosen configuration
Specific integrations
When a project needs to exchange data with a third-party system, that function must be assessed separately. A technical possibility should not be confused with a native SANIA feature.
- Third-party system assessment
- Specific connection or development when required
- Scope defined before deployment
EVOLVING ARCHITECTURE
Choose the right configuration instead of multiplying components
Multiple LLM engines can be used depending on the project configuration. This makes it possible to adapt the solution to identified objectives and constraints without presenting one model as the answer to every need.
ALLSAN has worked in digital signage and interactive solutions since 2007. This real-world screen experience complements SANIA’s AI layer: placement, readability, interaction, maintenance and content consistency remain essential to deployment.
REAL-TIME PIPELINE
How a SANIA interaction is built
A deliberately simplified view of a question’s journey without exposing proprietary implementation details.
Visitor
The visitor asks a question.
Voice or touch
The interface receives the interaction.
Context
The request is interpreted with session context.
LLM
The conversational engine determines how to build the answer.
Knowledge
The knowledge base can provide relevant business information.
Tools
A configured function, API or webhook can be called if needed.
Avatar + voice
The answer is delivered back through the SANIA experience.
KNOWLEDGE & TOOLS
AI that can answer, retrieve and act within a defined scope
Technical capabilities are enabled according to the actual requirements of the project.
Document retrieval / RAG
SANIA can retrieve relevant information from documents and knowledge-base content.
Function calling
The LLM can select a configured tool when an intent needs an action or external information.
APIs & webhooks
HTTP endpoints can be called to exchange data with an external system included in the integration.
Client-side actions
An application can expose actions that SANIA may trigger within the boundaries defined for the project.
SPECIFIC INTEGRATIONS
Connectable does not mean connected to everything by default
The ability to call an API, webhook or function does not mean that every CRM, ERP, booking, payment or business system is already natively connected.
Each third-party connection must be defined, secured, tested and integrated for the relevant project. This keeps platform capabilities clear without promising an integration that has not been built.
YOUR PROJECT
Request a demoLet’s discuss your technical environment
Existing screen, dedicated kiosk, network constraints, business content or integration needs: a demonstration helps identify the most relevant SANIA configuration.