Interpreter requests across disconnected tools
Healthcare and legal teams often need an interpreter while already helping a patient or client. Reach connected organisations with professional interpreters across more than 250 languages.
Requests were spread across calls, emails, admin teams, billing tools and separate portals. Staff lost time moving between them, while administrators had limited visibility into usage and team activity.
Designing for frontline staff and administrators
I designed the request and session journeys alongside the organisation workspace and reusable product patterns.
Frontline staff wanted the shortest useful route to an interpreter. Administrators needed user management, activity tracking, reporting and reassurance around sensitive work. Giving both groups the same interface would make their jobs harder.
Simplifying interpreter requests and live calls
I prioritised language selection and audio or video requests. Staff could move into interpretation without working through organisation settings first.
The flow covered the request, finding an available interpreter, connection and the live session. Clear controls and status feedback mattered because staff were managing another conversation at the same time.
Sessions, team activity and reporting
Administrators could set up a workspace, invite staff and review sessions, usage and reports. The saved session information connected the frontline interaction to the wider organisation workflow.
The workspace needed denser information than mobile. I kept shared foundations while giving tables, reports and management actions the space they needed.
Adapting the workflow across devices
Reach had to work in hospitals, legal offices, field environments and remote settings. I designed for mobile, tablet and desktop so teams could use the device available to them.
Security and compliance signals helped make the sensitive nature of the service visible. The interface still needed to keep the main action easy to find.
Connection and session feedback
I used Lottie for loading, connection, session, confirmation and completion feedback. Jitter supported motion videos and reusable GIF, SVG and JSON assets for product, web and marketing.
Those details helped users understand whether a request was being processed, a call was connecting or a session had finished.
Connection time and enterprise design lessons
Organisation count describes platform scale.
Reach helped teams connect with professional interpreters in 30 seconds or less and reduced administrative friction across devices.
The lesson for me was to keep each workflow focused. Staff needed quick access during a live situation; administrators needed the context to manage the service around it.
