Use when the user wants a listenable brief for work produced by AI agents, coding tools, or document workflows: agent sessions, code changes, pull requests, plans, specs, research reports, documentation pages, blog posts, URLs, local files, or pasted markdown. Also use for casual requests like give me the brief, audio…
Use when the user wants Pipa to turn fuzzy demand into defined work by selecting one focused operation for framing, chartering, stakeholders, requirements, scope, roadmap, decisions, or a specific workday plan.
Use when the user wants Pipa to coordinate active service delivery: status, blockers, risks, owners, handoffs, dependencies, triage, weekly client updates, QA, and next actions.
Create and cancel simple one-shot email follow-up reminders through Pipa. Use this when the user wants Pipa to email them a specific reminder at a future time, such as “email me tomorrow at 9 to follow up,” “remind me by email next Friday,” or “send me a reminder in two hours.” Also use it to cancel a previously…
Use when the user wants Pipa to help a service business get paid: invoices, payments, billable time, budgets, margin, change-control money impact, and payment follow-through.
Use when the user wants Pipa to help a small service business get work: content, inbound, leads, pipeline, opportunities, referrals, outreach, market signals, and next opportunity actions.
Use when the user wants to talk through work with Pipa or their current agent in a live voice huddle: Pipa Huddle, Pipa voice session, talk this through, walking work session, plan this by voice, voice call with my agent, or discuss this out loud. Starts a voice huddle with agent context and optional handoff. Do not…
Use when the user wants to improve operations through a workday shutdown, acceptance decision, handover, retrospective, or closeout review and needs Pipa to select the right focused operation.
Use when the user wants Pipa to maintain client trust: follow-ups, check-ins, client health, retention, renewals, referrals, testimonials, stakeholder care, and relationship-sensitive next actions.
Use when the user wants to manage Pipa configuration across profile setup, connectors, company brain or memory, permissions, automations, triggers, loops, or access audits. Route profile setup to pipa-setup and connector setup/status to pipa-connectors. Do not use for business work or an already-connected app action.