How to Automate Interpreter.io

A hearing does not start until the interpreter is in the room

Interpreter.io describes itself as an interpreter management solution, and that is close to literal. It is where a booking for a human interpreter is raised, offered, accepted and eventually billed. Courts run it, and so do hospitals, agencies, call centres, schools, nonprofits and government departments, sometimes under the name Interpreter IO.

A booking is a small and awkward object. It has a language, and often a dialect. It has a date, a time and a place, which may be a courtroom that was on the schedule months ago or a venue arranged this morning. It has a delivery method: onsite, telephone or video. And it has a person at the end of it who has to be right for that setting and free at that hour.

What the platform holds is the roster and the bookings: interpreter profiles, the credentials attached to them, and the assignments those interpreters are invited to and either accept or decline.

The booking desk finds out last that a hearing moved

A coordinator's day goes on finding out what changed.

The hearing on Tuesday was continued. The court knows, the clerk knows, and the interpreter who is forty miles into the drive does not. Thursday's booking still has nobody on it, because the two people on the roster for that language are already out. An interpreter answered an offer by text message on Saturday, so the record says pending while everyone involved believes it is confirmed. A session that ran a fortnight ago has never come back with the paperwork proving how long it lasted, so it cannot be billed.

Underneath all of it sits the roster. Credentials carry expiry dates, and somebody has to notice one approaching well before an interpreter is standing outside a courtroom.

Interpreter.io

A continued hearing caught the same day The court's published list read each afternoon against the bookings on the board, so a change at four reaches the desk that evening.

The hard bookings worked first Everything still unfilled in the next three days ranked by how difficult it will be to cover, each with an offer already drafted.

Timesheets chased with the details attached Sessions that finished but never came back with paperwork followed up automatically, so a fortnight-old assignment can still be billed.

Interpreter.io already tracks who is certified and who accepted

The platform covers the booking lifecycle properly, and a desk running this from a shared mailbox and a spreadsheet is doing the hardest available version of the job.

Credential management holds unlimited interpreter profiles carrying expiration dates and supporting documentation such as security clearances, and lets a coordinator filter the roster on those credentials when a booking calls for one. Booking templates can be configured differently for different court levels, with a central approval step where an organisation wants one. The lifecycle runs from inviting in-house, contract or agency interpreters through to assignment, with each invitation accepted or declined, and closes with the actual duration entered, comments added and documentary evidence uploaded. The invoice generator filters completed and cancelled assignments by client, interpreter, agency or language and exports them to Excel, and contract interpreters can pull their own billing report from their job dashboard. Reporting adds dashboards and charts on top.

Every one of those runs on what a requester booked and what an interpreter answered. The hearing itself lives somewhere else entirely: on the court's own published calendar, inside a case system the language services desk has no login for.

Tomorrow's bookings get tested against the court's own list

An afternoon sweep of the sources outside the platform changes what tomorrow morning looks like.

The court's published list read against every booking on the books, so a hearing continued at four in the afternoon reaches the desk that evening instead of at the courthouse door. Everything still unfilled across the next three days ranked by how hard it will be to cover, each one carrying a drafted offer to the interpreters who match, so the difficult bookings get worked first rather than last.

Expiry dates on the roster checked against what the issuing body currently publishes, so a difference surfaces weeks ahead. Sessions that finished without their paperwork chased with the assignment details already attached. Exported invoice runs set beside what each requesting agency has actually paid, so an ageing balance is visible without anyone building a report. The requester who books the same slot every week, and the one whose bookings are cancelled more often than they run, both plain on a Monday morning.

Reading, gathering and drafting run unattended. No interpreter is assigned, no booking is confirmed to a court, and no invoice goes out until a coordinator has looked at it.

Nobody gets sent to a courtroom by software alone

Send the wrong interpreter to a hearing and nobody involved forgets it. Send the right one to a hearing that was continued last Thursday and it costs a day that somebody has to pay for.

WebRun is an agent that drives a real Chrome browser, signed in as you. It opens Interpreter.io alongside the court's calendar, the credential registers and your inbox, reads what each one shows, and hands back the unfilled list, the expiry warning or the chase already drafted.

It runs on your schedule in your own private environment, sessions are not shared between tools, and a workflow can be held to a named list of sites. You can watch a run and stop it.

What each workflow opens is written on it.