Skip to main content
Home (/) is the composer. The first message starts a thread (/t/…). ⌘N starts another. ⌘K opens the command palette. Rename, delete, and the Today / Past 7 days / Older groups are in Threads. Under the composer, on desktop:
  • Playbooks (or Start here while you are activating) — work Rivvi can stand up. Click a card to begin in chat.
  • Recent — threads you can jump back into.
  • Programs — what you already run, plus inbound and the website widget.
Playbooks are grouped Run the day, Dig in, Grow, Then stand up, and What it knows. Which cards you see depends on your access and what is connected. A card starts a thread. It does not dial by itself. A card’s menu is Pin {name} to top or Unpin {name}. Pinned cards sit under Pinned. Under the composer, three starters: Summarize today, What needs me?, and What’s in-flight?. Recent is threads. A thread with no title is Untitled thread. A card can say Resume: {title}. The scope mark is Workspace, Chat, Setup, or Paused. View all opens Threads. Programs on home is the work you already have. A new org leads with First program or First programs, then Stand up. Sections can read Programs to stand up, Channels live, and Start later. View all programs opens Monitor. A row says one of: If something is waiting, When you’re ready appears above those tabs. Sidebar Inbox is the follow-up queue when the count is above zero. See Inbox.

What you can do from chat

Chat is the whole product, not only outreach. These are separate jobs. Asking for one of them never starts the others. You do not need Rivvi’s words. If you want a count, a chart, or a draft, say that. Rivvi will not dial because you asked a question.

Add something to the message

+ on the composer is Add to chat:
  • Attach file — a file for this thread. PDF, Word, PowerPoint, Excel, CSV, text, or an image. Up to 50 MB. Details.
  • Capture screen — a screenshot of what you are looking at.
  • Data lake — a file already saved under Settings → Data lake. Empty state: Nothing in the data lake yet. Open data lake goes to Settings.
  • Connectors — turn a connected tool on for this thread, or Browse connectors / Manage connectors.
A one-off sheet for a run is an attachment. Put a file in the data lake when the team should analyze it again later. Clinic roster, who works where, and location hours live in Knowledge, not in the composer.

Cards in the thread

  • A report — headline, chart, table. A follow-up revises the same card.
  • A decision — Looks good on a list, Launch / Schedule, or a form you fill in.
  • A live view — a run, Inbox, or a detail you can open.
Some buttons open Monitor, a program, or Settings. Finished reports, memos, and decks also land in sidebar Artifacts. Come back to the thread to change them.
A run you build in chat goes out only when someone clicks Launch or Schedule. Asking, writing, and analyzing do not place a call or send a text. Echo is the exception — see LeadingReach.

Next

Attach files

Data lake

Artifacts

Runs