A digital human kiosk and AI receptionist.
Build a virtual receptionist, hotel concierge or museum guide that visitors can talk to. IAMX connects a digital human to configured voice, knowledge and tools. Choose a browser avatar or Unreal MetaHuman, then test the kiosk screen, sound and network at your location.
Design the visitor journey first
- Define the job
Choose the questions the kiosk should answer, the actions it can perform and when it should refer a visitor to staff.
- Configure the experience
Prepare a voice, knowledge base, scene and animations. An inactivity action can welcome visitors or present a campaign when no one is interacting.
- Connect only the needed systems
Tools can call configured services. Camera, identity and device integrations require their own setup and operational controls.
- Validate on the kiosk hardware
Test microphone placement, room noise, speakers, network recovery, screen layout and the rendering machine under realistic conditions.
Brand communication between conversations
Timed actions can combine a character animation with music, a recorded explanation or a video. For example, after a configured inactivity delay, the character can present a short campaign. Interactions and the rule’s repeat settings determine when the next action may run.
These are configurable product capabilities, not a claim that every kiosk includes a complete banking, payment or identity workflow out of the box.
Match the delivery to the site
| Option | Deployment consideration |
|---|---|
| GLB character | Browser rendering can suit a branded or stylized avatar. Check the target device’s graphics performance. |
| Unreal MetaHuman | Run Unreal on the kiosk or provide a streamed scene from a rendering host. |
| Knowledge and tools | Use approved information and explicitly configured service integrations. |
| Camera and identity | Available capabilities depend on the selected plan, integration, hardware and deployment requirements. |
Discuss the complete installation
For an enterprise kiosk, define the number of locations, operating hours, expected concurrency, languages, hardware and external integrations. This allows the deployment and support scope to be assessed together.
Start with a task visitors can complete
Hotel, campus and clinic visitor information
For hotel reception, a university campus or hospital information desk, prepare approved opening hours, service descriptions and directions. Keep healthcare guidance administrative, with a clear route to staff; this is not a medical-advice workflow.
Museum guides and showroom product advisors
Prepare museum exhibit explanations, car showroom specifications or real-estate project information in a reviewed knowledge base. Test the virtual guide’s spoken explanations, animation and demonstrations on the actual visitor display.
A connected service workflow
Enable only the external tools needed for the task. The connected application must validate requests and return useful errors; identity, payment or account access requires a separately scoped integration.
Multilingual tourism and event guidance
For tourism information or a trade-show assistant, choose providers that support visitors’ languages. Test venue names, directions and specialist terms. Language availability and pronunciation depend on the selected services and voice.
These are configuration examples for planning a kiosk, not reports of completed customer deployments. Use the Knowledge Bank guide and Tool Registry guide to prepare the content and permitted actions.
Run a pilot at the actual installation
| Area | What the pilot should establish |
|---|---|
| Microphone and speakers | Can visitors be heard at the intended distance during normal room noise? Does the microphone pick up the kiosk's own speech? |
| Touch and framing | Can a visitor find and use the microphone control? Are the face, text and action media readable at the display's mounted position? |
| Visitor transitions | Test the end of one conversation, the start of the next and the intended handling of visible messages and any stored visitor information. |
| Connectivity | Test a network interruption and recovery with your selected speech services and renderer. Define what staff should do when the experience is unavailable. |
| Operational ownership | Assign responsibility for content updates, device startup, monitoring, support and any camera or identity workflow. |
Record the observed results against your own acceptance criteria. A quiet desktop demo does not establish performance in a busy lobby or exhibition hall.
Digital human kiosk FAQs
Do I need a GPU server?
A GLB avatar renders on the kiosk device, whose graphics performance must suit the model. A MetaHuman runs in Unreal on the kiosk or a separate rendering host. Streaming moves rendering to that host and adds network requirements.
Does an IAMX plan include kiosk hardware?
The public conversation plans cover their stated usage and feature allowances. Screens, microphones, rendering infrastructure and deployment support need to be planned for your installation; confirm the full scope with IAMX.
Can it operate without an internet connection?
Do not assume the cloud workflow works offline. Hosted conversation, speech, knowledge and external tools depend on their configured services. Discuss any local or offline requirement before selecting the deployment.
Are identification and payments ready out of the box?
No. These workflows depend on the selected plan, hardware, connected services and application rules. Agree the integration and test it end to end before offering it to visitors.
Build a character people can talk to.
Start with a model, give it a voice and knowledge, and test the complete experience before publishing.
Maintained by IAMX · Updated · Platform facts and requirements