Blog

    Interpreter Scheduling Software That Learns From Feedback

    Requester complaints and interpreter ratings belong on the booking, not in a survey tool. How feedback and provider preferences shape the next assignment.

    Eclipse Team•Language Services Operations
    November 21, 2026
    6 min read

    Interpreter Scheduling Software That Learns From Feedback

    Most language service providers collect feedback somewhere. The problem is where. If requester comments live in a survey tool or a shared inbox, they never reach the screen your coordinators use to assign the next job. Feedback only improves quality when it sits on the booking, counts toward the interpreter's rating, and can turn into a preference that changes who gets offered the work next time.

    A complaint that went nowhere

    Tuesday, 4:40 p.m. A patient-access coordinator at a clinic emails your scheduling inbox. Yesterday's Spanish interpreter for an oncology consult arrived late and seemed rushed. The family noticed. So did the physician.

    Your coordinator replies with an apology, copies the email into a QA spreadsheet, and gets back to the queue. There are forty open requests for tomorrow.

    Two weeks later the same clinic books another oncology consult. The same interpreter is available, credentialed and close by — so the same interpreter gets it. Nobody did anything wrong. The complaint just lived in a different system from the assignment.

    That's the gap. Not a lack of feedback — a lack of connection between feedback and scheduling.

    Why it costs more than one bad session

    Requester trust. A requester who complains once and sees the same thing happen again stops complaining. They start shopping. In healthcare, legal and education work, the person who books interpreters often has a say when the contract comes up.

    Quality you can defend. Language access is a compliance obligation for many of the organizations you serve. When a client asks how you monitor interpreter quality, "we have a spreadsheet" is a weak answer. A record of every rating, every complaint and how it was resolved is a strong one.

    Fairness to interpreters. One frustrated requester shouldn't sink an interpreter across every account. And interpreters see things too — the requester who never shares prep material, the department that books 30 minutes for a 90-minute appointment. If only one side gets a voice, your quality data is lopsided.

    Coordinator time. Every complaint handled by email is a thread to chase, a note to copy and a decision to remember. Multiply that by every account.

    How it works in Eclipse

    Eclipse was built by interpreters, and the feedback workflow reflects that: it lives inside the booking, and it ends in a decision about the next assignment. Here's what your team actually does. (Prefer to watch? See the 2-minute walkthrough: Collect and review service feedback.)

    1. Decide who gets asked

    Go to Analytics & Alerts > Feedback and open Feedback Settings. Choose who is asked for feedback — requesters, interpreters or both — how often they're asked, which bookings to skip, and how many days the link stays valid (7 by default).

    Need different rules for one job? Change them on the booking's Feedback tab or in the Booking Form. Once a booking is closed, its feedback settings lock.

    2. Make it easy to answer

    After the session, the people you chose get the Booking: Feedback Request notification by email, SMS or in-app notification, depending on your notification setup. The link opens a short rating-and-comment form without signing in. It works once and then expires.

    Requesters and interpreters can also open the booking in their portal and select Leave Feedback on the Feedback tab. Interpreters who haven't responded are prompted the next time they sign in.

    Interpreters rate the booking's requester. The requester's company and department are saved with the feedback, so you can see patterns by organization, not just by person.

    3. Review everything in one place

    The Feedback page lists every rating and comment, with flagged complaints pinned to the top. Filter it down, and use the Feedback For column to see who each piece of feedback is about.

    4. Act on a complaint — and change the next assignment

    Open the row's actions menu and select Flag for Complaint. The booking's status shows Flagged for Complaint until you mark it resolved from the same menu, so nobody loses track.

    From that same menu, you can add the interpreter to the preferred or disfavored list for the people on that booking. That's where feedback meets Service Provider Preferences — and where the clinic in our story gets a different outcome.

    5. Let preferences do the filtering

    Service Provider Preferences live on a company, department or individual requester: preferred and disfavored interpreters, required certifications, tags and Exclude Tags. When a booking comes in, Eclipse merges everyone's preferences without duplicates. Assign Provider and Invite Providers open with those preferences already applied as filters. You can still change them for one booking.

    So the next oncology request from that clinic doesn't depend on someone remembering a spreadsheet row.

    6. Keep ratings honest

    Some feedback isn't fair — a rating about parking, or one meant for a different appointment. Select Hide and it stops counting in every average straight away: the interpreter's profile rating, the booking's rating breakdown and the rating in Assign Provider. Unhide it to bring it back. Only hidden feedback can be deleted.

    Hidden feedback still counts toward the negative-feedback warning in Assign Provider, so a coordinator sees the context before assigning.

    Where ratings show up

    • The booking's Feedback tab in Assignment Details.
    • The interpreter's profile: average rating, plus the feedback they've received and given.
    • The Booking Form: the requester's rating for the company, next to their name.
    • Assign Provider: each interpreter's rating, with a warning when there's negative feedback.
    • Reports.

    What to look for in any interpreter management system

    Use this list whatever you're evaluating.

    • Feedback tied to a booking. A rating that isn't attached to a specific assignment can't tell you what went wrong or for whom.
    • No-login, single-use links. Requesters won't create an account to rate a session. Email, SMS and app links that open a form — and expire — get answered.
    • Two-way feedback. Interpreters should be able to rate requesters. Otherwise you only hear half the story.
    • A visible complaint status. A flagged complaint should show on the booking until someone resolves it.
    • One step from complaint to preference. If acting on feedback means opening a different screen and retyping names, it won't happen at 4:40 on a Tuesday.
    • Ratings where you assign. Averages on a report nobody opens don't change outcomes. Ratings and warnings in the assignment screen do.
    • A fair way to exclude bad data. You need to remove an unfair rating from averages without destroying the record.
    • A vendor that doesn't compete with you. Platforms that also sell interpreting see your requesters' feedback about your interpreters. Eclipse has no conflict of interest: overflow is optional and opt-in, and Eclipse never competes with its clients for their work.

    Frequently asked questions

    Do requesters need an account to leave feedback?

    No. The feedback link opens the form without signing in. It works once and expires after the number of days you set in Feedback Settings — 7 by default.

    Can interpreters give feedback too?

    Yes. Interpreters rate the booking's requester, by link or from the booking's Feedback tab in their portal. The requester's company and department are saved with it.

    Does a complaint automatically block the interpreter?

    No — your team decides. From the feedback row you can add the interpreter to the disfavored list for the people on that booking. Until then, Assign Provider shows a warning when an interpreter has negative feedback.

    What if a rating is unfair?

    Hide it. Hidden feedback stops counting in every average immediately, and you can unhide it later. Only hidden feedback can be deleted.

    Does Eclipse support 300+ languages?

    Yes. Feedback and preferences work the same way for every language and service you schedule.

    See it on your own bookings

    Feedback that never reaches the assignment screen is just paperwork. See the Feedback module, how scheduling and matching use your clients' preferences, and how Eclipse supports healthcare language access.

    Ready to connect feedback to every assignment? Schedule a walkthrough.

    Tags

    interpreter feedback
    quality assurance
    provider preferences
    interpreter management
    requester experience
    language access
    Share this article