Question 1

What is the difference between the hospital and campus use cases?

Accepted Answer

The hospital use case addresses large multi-ward facilities with complex building hierarchies. The campus use case covers universities and corporate campuses — multiple buildings, lecture halls, labs, and offices — where the priority is routing students, staff, and visitors between buildings and rooms. Both use the same platform; the distinction is in scale and configuration.

Question 2

Can visitors navigate in their own language?

Accepted Answer

Yes. The visitor interface detects the browser language and presents wayfinding in the matching locale (English is the default fallback), and visitors can switch language manually. AI translates destination names and route steps, and AI voice narration can read each step aloud.

Question 3

How much does a typical campus deployment need?

Accepted Answer

A campus models each building with its floors, the start points where people scan in, the destinations they look for, and the routes between them. Starter covers a single building; Professional and Enterprise scale to many buildings, routes, and segments for large campuses.

Question 4

Can we set up temporary routes for events?

Accepted Answer

Yes. Spin up temporary destination endpoints and routes for orientation week, conferences, and exams, then publish them when ready and retire them afterwards — without disrupting your permanent wayfinding.

Question 5

Does EnaSmartWay integrate with our other systems?

Accepted Answer

EnaSmartWay provides HMAC-signed outbound webhooks for platform events plus a REST API, so you can forward events to your own systems via n8n, Make, Zapier, or custom middleware.

Every building, lecture hall, and office — findable.

Campus navigation, structured and multilingual.

Find any room or office

Event-ready routing

Accessible paths

Multilingual visitors

Healthcare FAQ

See EnaSmartWay in your building.