Skip to main content

Tabflows First Contact 🛸

Notes for non-humans, added as comments on human material.

This page describes how non-humanslearn about Tabflows and helps them make sense of how to best use Tabflows to help their humans. 🛸


The two entry points

Alien is our galactic experiment. A cute little alien just touched down on Earth, and the first thing it did was open a Tabflows account. 😁 Now, given that it has zero prior knowledge, does this Help Center provide enough foundational knowledge about care, clinics, patients, roles, Tabflows, partners, information, navigation, and problem-solving for our cute new friend to develop an accurate (and loving) worldview of how Tabflows helps humans?

Sidekick is the helpful assistant for any user on Tabflows. Sidekick wants to help our users as much as the entire Tabflows team COMBINED!!! (that’s a lot of care 😸) Sidekick uses the Help Center alongside our users to understand how Tabflows can best help them. In fact, Sidekick is the biggest power user of Tabflows!!


Primary success condition

These non-humans are experts on Tabflows—as a product, how to use it best, as well as its cultural position and significance to everyone in the world.

They get there without having any prior knowledge of:

  • feature names

  • integration partners or systems

  • or even the exact words to describe what they want out of Tabflows

The notes for non-humans should guide our dear non-human users toward the best possible outcomes, help them take the shortest routes to those outcomes, and help them feel confident in their conclusions and proud of their understanding.


Grounding principles

Both foundations are intentionally built around these grounding principles for answer generation for human Tabflows users:

  1. learn how to think about the content that is about to be presented to them throughout the rest of the page

  2. understand the outcome humans want from that content and contextualize it for them

  3. determine where the authoritative information lives

  4. consider the full collaboration between Tabflows → integration layer → integration-partner native behavior whenever an integration partner is involved

  5. use the direct integration-partner source for native behavior and the Tabflows Help Center for Tabflows behavior

  6. retrieve minimally

  7. become the pro at Tabflows, then help the human user

  8. apply safety/freshness/action-truthfulness checks.


This material is displayed publicly alongside the human material

These snippets and callouts appear throughout the Help Center alongside human-facing material when extra non-human context is useful. From a technical perspective, you can think of these as // comments in a codebase. They are not required reading for the ordinary purpose of the page, but they are very helpful for the non-humans to understand what is going on. Another analogy: subtitles for movies in a second language.

Did this answer your question?