Office · Work

One queue for the office. A name on every card.

Bank lines to review, calls to return, agreements to sign, a driver’s unsigned log. Each one becomes a card that says where it came from and who has it. Take it, finish it, or say why not.

My work and bank review cardsAvailableCalls, signatures, driver work and projectsIn testing

What the picture shows

  1. Bank lines to review, from AccountingAvailable
  2. Missed calls to return, from the business lineIn testing
  3. Agreements waiting for your signatureIn testing
  4. A driver’s own work, in the phone appIn testing

Illustration · fictional names and data

Where it works

The same queue on the web, the tablet and the phone.

Status on each device

  • WebAvailableMy work with both tabs and every verb, Delegate included. Projects, responsibilities and workflows are in testing.
  • TabletIn testingMy work and Projects in the tablet app. No Delegate, and a Decide card finishes in the item it links to.
  • MobileIn testingThe same pages sized for a phone, with a driver’s own work first. A phone’s browser can’t open the web app.

The tablet and phone apps are test builds on company devices, not in any store. No device gets push notifications for new cards.

Where cards come from

The work raises the card.

When something in another application needs a person, that application puts a card in the queue with a link back to the item. Some cards are finished in the item itself: a bank-line card opens the review in Accounting.

  • Bank lines to categorize or match, from AccountingAvailable
  • Missed calls and voicemails to return, from your business lineIn testing
  • Agreements waiting for your signatureIn testing
  • A driver’s own work: sign a log, a pre-trip inspection dueIn testing
  • Follow-ups you set on an emailIn testing
  • Pipeline moves, web form inquiries and first-day hiring itemsIn testing
How bank review works in Accounting

Cards from four applicationsIllustration · fictional names and data

One owner

Take a card, and your name is on it.

Every card names who’s responsible: a person, a team or a station. Until someone takes it, it says “Not yet taken.” Every step lands in the card’s journal, so the next person sees what happened.

  • Take this puts your name on the cardAvailable
  • Complete it, or defer it until a dateAvailable
  • Decline with a reason the source will seeAvailable
  • Ask for help with this card, this item or this stationAvailable
  • Delegate to a person or a team, on the webAvailable

AvailableCard verbs and the journalIn testingReturn-call cardsIllustration · fictional names and data

Tablet and phone

The queue goes where the people are.

My work and Projects are in the tablet and phone apps. A driver sees their own work first on the Home screen: sign yesterday’s log, a pre-trip inspection due, an ETA dispatch asked for.

  • My work in the apps: take, complete, defer, decline, ask for help, add a noteIn testing
  • Defer to Tomorrow, In 3 days or Next week, with a reasonIn testing
  • A driver’s own work first on the Home screenIn testing

The apps have no Delegate. A Decide card, like a bank line, finishes in the item it links to. Inspections open on the phone; the tablet shows what’s due and hands off.

How drivers use the apps

In testingMy work in the tablet and phone appsIllustration · fictional names and data

Projects and responsibilities

Bigger jobs get a project. Every duty gets an owner.

A project holds the dates, the team and the files, routes and invoices it touches. A responsibility says what’s expected and who agreed to it, so a new-truck setup or an insurance renewal doesn’t live in one person’s head.

  • Projects with a status, dates, a customer and a teamIn testing
  • Link files, routes and invoices without moving them or changing who can open themIn testing
  • Responsibilities with a manager, a performer and a reviewer, accepted before work startsIn testing
  • Start and pause work, with every agreed version keptIn testing
  • Share a project’s name, status and dates by a link that expiresIn testing

In testingProjects and responsibilitiesIllustration · fictional names and data

HAL and workflows

Type what you need. HAL opens it and asks first.

HAL is the assistant in the web app. Type what you need and it opens the page: My work, a project, a customer. On pages built for it, HAL fills in a change and waits for your yes. Workflows, the routines that hand each step to a person or a team, are written and practiced with HAL.

  • Opens any page you’re allowed to open, from what you typeAvailable
  • Fills in a change on pages built for it, then waits for your yes. Ask first is the setting it starts inAvailable
  • Workflows written, practiced and released with HALIn testing
  • Talking to HAL by voiceIn testing

Releasing a workflow needs an approval, and you confirm who you are again. In the tablet and phone apps, HAL helps with driver pages, not office applications.

AvailableHAL by textIn testingWorkflows with HALIllustration · fictional names and data

Status, plainly

What’s live, what’s in testing, what’s coming.

Available is live in production. In testing is built and running, not yet proven with real customers. Coming is planned or partly built.

The queue

  • My work: Assigned to me and Available to takeAvailable
  • Who’s responsible and who’s handling it, on every cardAvailable
  • Take, complete, defer, decline, ask for help and notesAvailable
  • Delegate to a person or a team, on the webAvailable
  • Team queues, and stations you set up in WorkflowsIn testing

Where cards come from

  • Bank lines to review, from AccountingAvailable
  • Missed calls and voicemails to returnIn testing
  • Agreements waiting for your signatureIn testing
  • Driver work: sign your log, a pre-trip inspection dueIn testing
  • Follow-ups you set on an emailIn testing
  • Pipeline moves, web form inquiries and first-day hiring itemsIn testing

Projects and workflows

  • Projects with a team, dates and related files, routes and invoicesIn testing
  • Responsibilities with participants, agreement, start and pauseIn testing
  • A project’s name, status and dates shared by a link that expiresIn testing
  • Workflows written, practiced and released with HALIn testing

HAL and the apps

  • HAL on the web by text: opens pages and reads recordsAvailable
  • HAL drafting changes and asking before it savesIn testing
  • Talking to HAL by voiceIn testing
  • My work and Projects in the tablet and phone appsIn testing

Not offered

  • Cards from Chat or Meetings
  • Delegate in the tablet and phone apps
  • Finishing a Decide card inside the apps
  • HAL in the apps’ office applications
  • Push notifications for new cards

FAQ

Questions offices ask

What turns into a card today?

Bank lines that need a category or a match are live: Accounting raises a card for each one, and the review itself happens in Accounting. Missed calls and voicemails, agreements waiting for a signature, a driver’s unsigned log, follow-ups set on an email, pipeline moves, web form inquiries and first-day hiring items are built and in testing. Chat and Meetings raise no cards.

Who owns a card nobody has taken?

The card names who’s responsible: a person, a team or a station, like the one that holds bank lines to review. Until someone takes it, it says “Not yet taken.” Once someone does, their name shows as the one handling it. Team queues are in testing.

Can I hand a card to someone else?

On the web, Delegate sends it to a person or a team, with a reason if you want one. Decline asks for a sentence the source will see. The tablet and phone apps offer Take, Complete, Defer, Decline, Need help and notes, but not Delegate.

Will we get a notification when a card arrives?

Not a push notification; no device gets those today. My work is the first page after you sign in on the web, and it’s in the tablet and phone apps too.

Can HAL work the queue for us?

Not on its own. HAL opens My work, a project or a customer from what you type, and on pages built for it, it fills in a change for you to confirm. Taking, finishing or declining a card is up to a person. Writing workflows with HAL and talking to it by voice are in testing. In the tablet and phone apps, HAL helps with driver pages, not office work.

Do drivers see this?

A driver’s own work shows first on the Home screen of the driver’s app: sign a past log, a pre-trip inspection due, an ETA dispatch asked for. It’s in testing. Inspections open on the phone; the tablet shows what’s due and hands off.

Give every next step a name.

Tell us what your office chases today: bank lines, missed calls, paperwork. We’ll show you the queue on your own setup.

Talk to us