Connect an immediate need with an available interpreter.
Bring immediate requests, interpreter availability, the waiting queue, video sessions and service history into one workflow.

The work, connected.
Interpreter on Demand connects the client journey with the interpreter console. Keep eligibility, waiting status, acceptance and session follow-up together, with a service model defined around your hours, audience and interpreter capacity.
A clearer way to manage the details.
A clear entry point
Check service access and guide the client through the camera and connection requirements.
Interpreter availability
Let interpreters declare their service status and receive relevant requests.
Queue and routing
Keep waiting requests visible and apply the allocation strategy agreed for the service.
Acceptance and connection
Coordinate the accepted request and the private client–interpreter video session.
Duration and exceptions
Define session limits, closing notices and handling for cancellations or connection failures.
History and service indicators
Follow session outcomes, waiting time and usage through authorized operational records.
From the first step to the next handoff.
Request the service
The client checks access and starts an immediate request.
Join the queue
The service identifies a qualified, available interpreter.
Connect the session
The interpreter accepts and joins the client in the video session.
Close and follow up
Record the result and retain the service information needed for review.
Service hours, languages, eligibility, session duration and routing are defined for your deployment. Access to an interpreter depends on the available service capacity.
Keep the next step in MigiHub.
Know the workflow.
Define the right fit.
Bring your requirements to a conversation about configuration, supported features and implementation.
Is Interpreter on Demand the same as booking?
Booking organizes a scheduled or future service. Interpreter on Demand starts with an immediate request and a queue that connects the client with available interpreter capacity.
Is an interpreter always available immediately?
The queue reflects the service model and current interpreter availability. Waiting, unavailable-service and cancellation paths are defined so clients receive an appropriate status rather than an unsupported promise.
Are sessions recorded automatically?
Session recording is off by default. Recording, retention and participant notices would require a separately agreed scope and explicit controls.
Let’s build around your operation.
Show us your current process, the people involved and the outcome you want to achieve.