Loop Desk is an always-on business workspace that takes incoming signal (email, forms, feeds, notes) and turns it into briefs, watch items, and next actions.

Does Loop Desk send emails on my behalf?

Loop Desk can draft responses, but nothing sends until you approve and explicitly trigger it. The approval boundary is fundamental.

What signal sources does Loop Desk support?

Email, RSS/Atom feeds, form submissions, manual notes, and webhooks. The desk treats all sources equally in its processing loop.

rev 165 — Loop Desk changelog

rev 1652026-05-07

Strategic diversification — Healthcare/Wellness onboarding template + public /integrations marketing page + activation checklist v2 (6 steps with refreshed copy and a guardrail nudge) + evergreen operator blog post on the always-on desk shape — pivot away from the 14-rev cost-spike alarm thread (rev 151-164) onto the public-marketing + onboarding axes — 87th unbroken cadence rev

Healthcare/Wellness onboarding template — sixth industry presetNew ONBOARDING_TEMPLATES entry for Healthcare/Wellness practice owners (independent therapists, dentists, vets, dental clinics, wellness studios) — a real underserved SMB segment that until rev 165 had to fall back on Other/Custom. Seeds 4 high-importance memory entries (patient-communication preference, no-show policy, review-cadence lesson, retention-red-flag lesson) plus 1 sample patient-feedback signal so the workspace's first cycle has substance. Mirrors the rev-19 pattern (Ecommerce/SaaS/Consulting/Agency/Creator) at the sixth named vertical. Strategic significance: closes a gap in the day-1 starvation-point story for an industry segment that maps cleanly onto Loop Desk's approval-first vocabulary (no-show notification, review-request copy, retention nudges all want the same human-in-the-loop boundary).
Public /integrations marketing page — closes the public marketing trioLoop Desk has shipped /changelog (history) since rev 14 and /roadmap (future) since rev 38, but until rev 165 had no single page answering 'what does this product connect to?' for procurement teams + B2B buyers evaluating governance-first AI. The /integrations page lists every Loop Desk channel grouped by axis: inbound (RSS / review sites / LinkedIn / email forwarding / inbound webhooks / manual logging — 6 entries with auth model + sinceRev), outbound (Slack push / outbound webhooks per-event router / daily digest / public share links / public desk-health badge SVG — 5 entries), and programmatic (REST API v1 / OpenAPI 3.1 / MCP server coming Q3 — 3 entries). Each entry names the auth model and the rev where it shipped, doubling as a vendor inventory for SOC 2 / ISO 42001 procurement reviews. New page mounted at /integrations + sitemap entry + nav links across landing/changelog/roadmap/docs/blog so the public marketing trio (changelog + roadmap + integrations) is reachable from every other public surface. Strategic significance: cumulative diversification away from the 14-rev cost-spike-axis cluster (rev 151-164) onto the public marketing surface. SEO win on 'AI workspace integrations', 'governance-first AI vendor inventory', 'MCP business workspace integrations' — buyer-side terms.
Activation checklist v2 — 6th step + sharper copy on existing 5The rev-11 activation checklist shipped 5 steps (connect a source / log signal / run a cycle / approve first output / wire integration) when the dashboard had ~12 panels. After 154 revs the desk has accumulated memory teaching, multi-operator invites, per-recipient digests, cost guardrails, and the MCP-foundation v1 API — but the checklist copy still read like rev 11. Rev 165 refreshes it on three axes: (a) sharper copy on the existing 5 steps that names current affordances ('connect a feed' vs 'Hook up an RSS feed'), (b) adds a 6th step 'Set a guardrail' that nudges new operators toward configuring at least one of: daily cost cap (rev 20), Slack quiet hours (rev 15), or workspace timezone (rev 20) — until rev 165 first-day operators didn't see the desk's operator-respect controls until they hit them organically, (c) visual: numeric badges on each step + tactile hover lift on incomplete steps so the recommended sequence is implicit. New `hasGuardrail` boolean computed in `app/page.tsx` from existing workspace columns. Strategic significance: the activation surface is the single most operator-loaded onboarding affordance on the dashboard; refreshing it to match the modern feature set is a load-bearing trust signal for new workspaces.
Evergreen blog post — 'The Morning News Habit, Replaced By An Always-On Desk'New blog post pivots away from the AI-meta / governance-DevOps / CI-CD security topics that have dominated the rev-by-rev blog cadence for many cycles. Operator-focused angle: what changes structurally when an owner-led team's morning news routine is replaced by an always-on AI workspace. Frames the four trust contract pieces (approval boundary / audit trail / cost predictability / operator-respect controls) as the structural constraints that make 'always-on' a sustainable daily habit rather than a weekend experiment. Names Notion Custom Agents' per-cycle credits + HubSpot Breeze's outcome-based pricing as competitive contrast. SEO play on 'always-on AI workspace', 'morning routine AI', 'governance-first AI for owner-led teams', 'flat-fee AI workspace' — operator-side buyer terms distinct from the technical/governance cluster the recent posts have all been targeting. Closes with concrete CTA cluster pointing at signup + docs + integrations + roadmap.