Lingfaro

How Lingfaro dispatch works: client and interpreter view

The full lifecycle of a Lingfaro request: posting, offer dispatch, acceptance, session, attestation, and invoice — the same flow from two perspectives.

2 min read

The mechanics are the same for both sides. What differs is what each side sees.

From the client’s view

  1. Post the request. Language, modality, time, location, optional context. The form rejects patient identifiers at the keystroke.
  2. Watch offers go out. Vetted interpreters who match the request receive an offer with a rate and an expiration window. You see the count: “12 offers out, 0 accepted.”
  3. Acceptance. First qualified interpreter to accept gets the job. You receive a confirmation with their credentials. The request status flips to “confirmed.”
  4. Session happens. Either party can flag an issue. After the session ends, both sides confirm duration. This is the attestation step.
  5. Invoice. Once both attest, the invoice is finalized at net-30 terms with your organization. Funds settle automatically via Stripe on payment.

From the interpreter’s view

  1. Offer arrives. With the rate posted up front. Not a fishing call, not a “let’s discuss”: a number you can accept or decline in one tap.
  2. Accept or decline within the window. Most offers expire in 5-15 minutes depending on urgency. Acceptance is final and binding; the job is removed from other interpreters’ queues.
  3. Show up. Do the work. All the context you need to plan (location, modality, language pair, specialty) is in the offer.
  4. Attest at session end. Confirm duration on your phone. Disputes go to operator review rather than silently absorbing your time.
  5. Payout. Direct deposit to your linked bank account on a regular weekly/biweekly cycle after the client pays the invoice. No invoicing on your end. The system generates and tracks it.

Frequently asked

What happens if no interpreter accepts within the offer window? +
The request automatically reaches a wider pool of interpreters at a higher rate. If that pool doesn't fill, it widens again, and finally goes to dispatch-team manual assignment. The client sees each escalation in real time and can cancel at any point. Typical fill time on common languages is under 8 minutes.
Who sees the patient's name or any clinical details? +
Nobody. The dispatch flow never accepts patient identifiers. Our PHI scanner blocks them at the form level. Interpreters receive language, modality, time, location, and a brief context (which the scanner has already verified is PHI-free). Clinical detail flows through your existing systems on arrival.
Tags product how-it-works

Ready to post your first request?

Post your first request