Solutions
Government programs
How a government program coordinating interpreting for many agencies and locations uses Fido for client records, requests, rates, billing documents and an audit trail.
A government program that arranges interpreting for the public and for its own staff works with many departments, locations and providers. Fido keeps each department's records, rates and requirements in one account and shows each request through to its billing document.
What the work looks like
Departments and offices request service. Each has its own locations, contacts and billing terms. Providers come from the program's own roster, contracted agencies or both. Staff need a clear record of who asked for what, who was assigned and what was billed.
What Fido gives a program
| Need | What Fido provides |
|---|---|
| Client and location records | Each department is a client with its own locations, contacts, rates and requirements. Settings flow from the organization to the client and then to the location. |
| Requests from many offices | Client users request from the Client portal. Anyone with the program's request link can start a request in the public request assistant, and staff review each one before anything is committed. |
| Consumers on record | Each consumer record holds communication modes, requirements and preferences, linked to the clients that serve them. |
| Rates | A billing rate resolves from the client location, the client, the organization location and the organization default, in that order. |
| Billing documents | Each client receives invoices. A pro forma statement is a quote the client accepts or rejects with a reason. An internal approval step with a deadline and an amount threshold can come before an invoice goes out. |
| Different access for different staff | Admins set what each role can do in every module, then fine-tune for an individual person. |
| A record of every change | History & Logs is an append-only trail with old and new values. |
| Your own systems | Calendars sync with Google and Microsoft. Developers read and write Fido data through the External API with organization API keys, each with scopes, an expiry, a rate limit and an IP allow-list. |
| Data location | Customer data is hosted in the United States. Organizations that need hosting in their own country can request regional hosting. |
A typical week
- Requests arrive from departments through the Client portal, the request link or calendar invites, into one review queue.
- A scheduler approves each request into an assignment and staffs it, directly or by broadcast.
- Departments follow their own requests and assignments, ask for changes and message the scheduler.
- Work is completed, and Fido builds an invoice for the client.
- Finance reviews invoices, sends them, records payments and syncs with QuickBooks Online or Xero.
How it works
One sample job, step by step: what you see, and what Fido does behind it.
SampleINV-3012 · internal approval on
- SetupWhat you see: An admin opens Rates & Billing and turns on approval for invoices.What Fido does: The admin sets the number of days approvers have, a dollar amount below which invoices go out freely, and a fallback.
- ThursdayWhat you see: INV-3012 is created and shows Pending.What Fido does: With internal approval on, a new invoice stays internal, marked Pending, until an authorized user approves it.
- FridayWhat you see: Jordan M. approves it from the document.What Fido does: Approvers approve or reject from the document, and a rejection can carry a reason.
- DeadlineWhat you see: On another invoice nobody acted in time, and it was approved and sent.What Fido does: At the deadline Fido does what you chose: approve and send, keep it pending, or notify a scheduler or admin. It checks once a day.
- Pro formaWhat you see: A pro forma passes internal approval, then the client approves it.What Fido does: A pro forma can need internal approval and client approval, each with its own deadline and fallback.
Related
See Fido with your program's work
A live walkthrough built around your kind of work.