Using Observer

Quick Actions

One click or one key. Each action already knows what to read.

Quick Actions are the buttons in the Meeting Window. Each one is a saved prompt plus the context it should use, so you do not stop talking to type.

They live on a Playbook. Change the Playbook and the buttons change with it.

What an action can read

  • Transcript — what was just said
  • Screen — what is visible right now
  • Search — a current fact from the web

The icons on a button show which of these it uses. The Playbook prompt, PDF summary, and current chat can also be included.

Built-in actions

General includes Reply, Screen Help, Recap, and Lookup.

  • Reply — draft what to say next
  • Screen Help — help with what is on screen, plus recent talk if listening is on
  • Recap — summarize the last few turns
  • Lookup — check a fact online

Catalog templates

Playbooks can add ready-made actions such as Objection, Next Step, Verify Claim, Debug Screen, or Action Items. These are starting points. You can keep them, reorder them, or replace them.

Custom actions

Write your own when the catalog does not match the job.

  • Name — the label on the button
  • Prompt — what Observer should do when you press it
  • Sources — transcript, screen, search, or a mix
  • Deep — whether Option + Shift should think longer

A Playbook can have up to 10 actions. Drag to set the order. Option + 1 through Option + 0 follow that order.

When to use which

  • A reply from the conversation → Reply or a custom transcript action
  • Something on screen → Screen Help, Debug Screen, or a custom screen action
  • A fact that is not in the room → Lookup or search
  • A question you type yourself → chat, with Screen Context or Full Context if you need a screenshot

Empty chat + Command + Enter (Ctrl + Enter on Windows) runs screen analysis — screen only, no typed prompt.

See how Sales, Interview, and Recruiting ship different buttons on the Use cases page.