Features

Client and consumer self-service portals

Clients request service, follow it and review invoices. Consumers keep their preferences and see their schedule. Both can start a request without a login.

3 min read Updated

Book a demoContact sales

See it on fetchfido.ai

The Client portal and the Consumer portal let the people who ask for and receive interpreting follow their own work without writing to a scheduler.

Client portal

A client is the school, hospital, business or program an organization serves. Client users sign in to a portal with a dashboard, a schedule, locations, consumers, finances, History & Logs and settings.

Request service

  • Submit a request for one or more consumers, with a location, a schedule, the provider qualifications needed and any documents.
  • Save a draft and finish later, or publish.
  • Duplicate an earlier request to start the next one.
  • Click an empty day on the schedule to start a new request.

Follow every request

A request moves from Submitted through Under Review to Approved, and the client receives an email, text or in-app notice at each change. A client can place a request on hold, cancel it or reopen it. On each assignment, a client sees who is assigned, is notified when providers accept, change or withdraw, and can message the scheduler or ask for a change or a cancellation.

Manage consumers and locations

A client keeps its own list of consumers and locations. Each location has its own address and contact, and either list can be exported. Client users can also keep preferred and restricted providers and provider requirements, and new requests start pre-filled with them.

Review the billing

Finances holds invoices and pro forma statements. A client can view and download invoices, send a message, open a question, acknowledge receipt and open the organization's payment link or instructions. A client accepts or rejects a pro forma statement with an optional reason, and approves or declines expenses the organization shares. A client never sees what providers are paid.

Consumer portal

A consumer is the person receiving the service, often a Deaf, DeafBlind or hard of hearing person an interpreter is booked for.

  • A profile in the consumer's own words. Communication modes, about-me notes, access instructions, and language and time settings.
  • Preferences that travel. Preferred and restricted provider lists and requirements for the providers who work with them follow the consumer from request to request.
  • A schedule. Confirmed work, open requests and the providers on each job.
  • Requests. When the organization turns it on, a consumer submits a request to a client they are linked to, and can place it on hold, cancel it or ask for a change.
  • Notifications. Choose email, text or in-app notices.
  • Guardians. A minor consumer can have guardians. The minor and each guardian have their own portal email, and a guardian's login lists every linked child.
  • Sharing. A consumer can choose whether the profile is shared with other clients in the organization, and can opt in to share it with trusted service organizations using Fido.

Consumers see provider information on their assignments and never see billing or pay.

Requests without an account

The public request assistant is a chat that anyone with the organization's request link can use, with no login.

  • It asks a few quick questions and collects the date, place, contact details and files.
  • A returning requester gives a client email or organization name, and the request attaches to that client. A new requester gets a client record.
  • Requesters can attach PDF, Word, Excel, text, JPG or PNG files up to 2 MB each.
  • Every public request arrives as pending, and staff review it before anything is committed.
  • It runs on the organization's request page or inside its own website, under the organization's name and domain.

Requests also arrive by calendar invite. Each organization has its own Fido email address. A client or consumer adds it as a guest on a meeting, and Fido creates a request after checking the sender.

Forms

Organizations build external forms with a drag-and-drop builder and publish them by link or embed code. A submission can create a client, consumer, provider, location, assignment, shift or service request. Forms support twelve field types, including file upload, and can be public or limited to signed-in users.

How it works

One sample job, step by step: what you see, and what Fido does behind it.

SampleLincoln ISD · new request · Dana K. submitting for a teacher

  1. Open
    What you see: Dana K. goes to Schedule, then Requests, then Add Request.
    What Fido does: One form in the client portal carries the requester, consumer, schedule, requirements and notes.
  2. Who
    What you see: She turns on I'm submitting on behalf of someone else and adds the teacher's name, email and contact details.
    What Fido does: The requestor's email is used for updates, so the teacher stays informed.
  3. Consumer
    What you see: She picks the consumer, or adds a new profile without leaving the page.
    What Fido does: The form selects a consumer for the request, or opens a new consumer profile in place.
  4. When
    What you see: She chooses Recurring for a weekly meeting.
    What Fido does: Schedule types are One time, Recurring, and Multi-days for events such as conferences.
  5. Details
    What you see: She adds notes and chooses who provides the meeting platform for remote work.
    What Fido does: Requirements show for each service type with preferred and restricted providers. The requester can enter a link.
  6. Publish
    What you see: She switches Draft to Published.
    What Fido does: Publishing sends the request to the scheduler's Requests queue. Hold, Cancel, Reopen and Send message live on the same page.

See both portals

A live walkthrough built around your kind of work.

Book a demoContact sales