How it works
Glossary
Task, owner, requester, board, follow-up, escalation, run and the other terms these docs use.
Terms used across these docs, in alphabetical order.
Active user
Someone who used Pondros in the last 28 days: asked it something, replied to a follow-up, closed a task, or worked in the app. Business is billed per active user. See Plans and billing.
Admin
A member who can manage people, billing and the workspace’s tools. The person who installs Pondros is the first. See Admins.
AI-built document
A Google Doc, Sheet or Slides deck, or a formatted document, that Pondros writes for you. The only thing Pondros meters.
Automation
A standing job Pondros runs on a schedule, set up by asking, like “every Monday, post what slipped”. See Scheduled jobs and digests.
Board
Where every task lives, in the Pondros web app. A workspace can have several. See Your board.
Check-in
A DM Pondros sends a task's owner as the due date gets close, asking where it stands.
Escalation
What happens when check-ins go unanswered: Pondros warns the owner, then tells the requester.
Guest
Someone in your Slack as a guest. They can use Pondros, see only what's shared with them, and are never billed.
Owner
The person responsible for a task. Check-ins go to them.
#pondros
The channel Pondros creates at install, where the weekly recap and team-wide nudges land.
Project
A group of tasks on a board, often a client or a channel. Tasks caught in a channel are filed under it by default.
Requester
The person who asked for a task. Pondros tells them when the owner replies, and when the work goes quiet.
Suggestion
A possible task Pondros wasn't sure enough to create. It DMs you with Add to board or Not a task.
Task
A piece of work with an owner, a due date, a project and a status. What Pondros catches, tracks and chases.
Turns
A rota for unassigned work: tasks nobody owns go to the next person on the list. Set it with /pondros turns.
Workspace
Your team's Pondros account. One Slack workspace connects to one Pondros workspace.