The Telecom Kiosk with a Face — and an Engine

Most conversations about avatar kiosks focus on how realistic the digital face looks. But realism alone does not make a kiosk useful. A photorealistic avatar that cannot scan a document, validate an ID, process a payment, or hand off to a human is just a screensaver with lip-sync. The real question is: what does the kiosk need to do, and does the platform underneath it support every step?

Azimut SDK runs on more than 1,500 self-service kiosks, including telecom kiosks that handle SIM registration, KYC (know your customer) checks, document capture, bill payments and top-ups. Looking at that workflow through the lens of avatar kiosks, something becomes clear: the hardest problems are underneath the face. The avatar is the interface. The SDK is the infrastructure.

What an avatar kiosk actually requires

When a customer walks up to a telecom kiosk to replace a lost SIM or register a new number, the interaction is not a single step. It is a sequence:

• Greet and identify intent — The avatar asks what the customer needs. The application routes the intent to the correct journey.
• Verify identity — The avatar guides the customer through face capture. The SDK drives the camera; your identity provider performs matching and any liveness checks.
• Scan documents — The avatar coaches placement. The SDK drives the ID scanner and returns the captured data for validation.
• Explain failures — The avatar turns a structured reason from the KYC service into plain language.
• Select a plan — The avatar recommends options from the live product catalogue.
• Process payment — The avatar confirms the amount. The SDK drives the payment terminal and reports the outcome.
• Issue the SIM or eSIM — The SDK drives the SIM dispenser or printer; your carrier systems activate the service.
• Escalate — The avatar summarises the case and hands off to staff.

An avatar without this stack is just a display, not a kiosk.

Why the platform underneath is what makes this real

The challenge with avatar kiosks in regulated environments such as telecom, banking and government is not generating a convincing face. It is connecting that face to every device and system it needs to serve a customer end to end.

Azimut SDK is hardware-agnostic by design. It connects supported ID scanners, passport readers, cameras, payment terminals, receipt printers, SIM dispensers and biometric devices through one JSON API, so an avatar layer can rely on capabilities that already exist. Behind the kiosk, Azimut middleware translates each request for the operator’s systems — modern REST services as well as legacy SOAP/XML billing, message queues and SFTP document archives — so the avatar can work with the back end the operator already has.

The avatar doesn’t have to be a separate kiosk product either. With Weave, an operator’s existing Android, iOS or web app runs natively on the kiosk, so an avatar feature built into the app reaches phones and kiosks together.

Telecom onboarding is one of the strongest use cases for avatar kiosks because it combines everything a plain touchscreen handles poorly: document-heavy flows that confuse first-time users; regulatory steps that need explanation, not just a form; errors such as glare or the wrong document type that need human-readable feedback; plan choices that benefit from a recommendation; and compliance requirements that need an audit trail.

A customer whose ID card was rejected does not need a better error code. They need something to say: "The card is too far left — please move it toward the centre of the scanner." That is what the avatar does, and it is only possible because the platform is already running the scanner and surfacing a structured reason.

The gimmick test

Avatar kiosks that fail share a pattern: the avatar greets users with scripted lines but cannot reach any back-end system, cannot complete a transaction, cannot explain why a step failed and has no human fallback. The ones that succeed are built the other way round: the workflow comes first, the device and system integrations second, and the avatar becomes the interface for something that already works.

Ask which peripherals the platform supports, how it reports document failures, how it connects to legacy systems, and whether it can run consistently across hundreds of kiosks. Those answers decide whether an avatar kiosk is a service tool or a trade-show novelty.

The next telecom kiosk will have a face. What matters is what runs behind it. See the full stack on the telecom self-service page.