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 172 — Loop Desk changelog

rev 1722026-05-08

Two more industry onboarding templates (Franchise / multi-location operators + Financial advisor / regulated professional services) + Gravatar auto-resolution on per-author OG cards + new public GET /api/v1/onboarding-templates endpoint completes the four-axis public-marketing v1 cluster (planned + most-requested + shipped + brand voice + industry-fit) — closes both named rev-171 next-sprint candidates (further industry templates AND per-author avatar URL field auto-resolution) at two more underserved verticals + the cheapest possible per-author identity primitive + the missing fourth axis on the v1 marketing surface — 94th unbroken cadence rev

Two more onboarding templates — Franchise / multi-location operators + Financial advisor / regulated professional servicesCloses the named rev-171 next-sprint candidate (further industry templates — franchise-model multi-location operators AND professional services with regulated client obligations) at two more underserved SMB segments. Franchise / multi-location operators (regional QSR / boutique fitness chains / multi-unit retail / multi-clinic platforms — 4 high-importance memory entries: brand-standard variance discipline across locations, weekly-roll-up + monthly-drill-down per-location P&L cadence, 8-location regional manager span-of-control ceiling, 90-day-decline + no-franchisor-contact franchisee retention red flag + 1 sample regional manager same-store-sales decline signal) AND Financial advisor / regulated professional services (independent RIAs, insurance brokers, financial planners, regulated wealth managers — 4 high-importance memory entries: suitability-rationale-leading recommendation framing, KYC + suitability gate before any recommendation, 13-month annual-review cadence regulatory cliff, client-readback suitability-violation red flag + 1 sample concentration-risk client question signal). Two new OnboardingTemplateKey enum values (franchise, financial_advisor) extend the rev-19 pattern. The templates cluster is now twenty-one named verticals deep, closing the day-1 starvation-point story across two more underserved SMB segments where the procurement-conscious buyer's 'will it know my industry on day 1?' question is loudest — multi-location operators where brand-standard discipline + per-location P&L cadence + franchisee retention are 2026 market-table-stakes, and regulated professional services where KYC + suitability + fiduciary documentation are the load-bearing differentiators against generic AI tools that don't know fiduciary regulatory obligations.
Per-author Gravatar auto-resolution on per-author OG cardsCloses the named rev-171 next-sprint candidate (per-author avatar URL field auto-resolution from the author's email so contributors with a Gravatar profile get a real photo on the OG card without registering it manually). Until rev 172 the rev-168 per-author OG card primitive shipped initials-fallback avatars (rev 171); contributors who wanted a real photo had to register an avatarUrl URL by hand. Rev 172 closes that gap at the cheapest possible primitive: a registered `email` field in data/blog-authors.json (or `authorEmail` in markdown frontmatter) auto-derives a Gravatar URL with `d=identicon` so a missing Gravatar profile falls through to a deterministic geometric pattern (always renders, never 404s) instead of a broken-image placeholder. MD5 of the lowercased + trimmed email is the load-bearing piece — same hash format every Gravatar SDK across every language ecosystem expects so a contributor who already has a Gravatar profile gets a real photo on every per-author OG card with zero configuration. The shared `getAuthorProfile` helper resolves the avatar with the same registry → frontmatter → null cascade rev 107 introduced; the new email field rides on top with the same precedence. Authors who explicitly want the rev-171 initials-circle treatment just don't register an email. Strategic significance: closes the OG-image-polish loop on the byline axis at the cheapest possible cost — no avatar-fetching infrastructure required for missing profiles, no broken-image placeholder, and zero configuration for contributors with an existing Gravatar profile.
GET /api/v1/onboarding-templates — public templates list on the v1 surfaceOpens the missing fourth axis on the public-marketing v1 cluster. Until rev 172 the rev-19/165/166/167/168/169/170/171/172 onboarding templates list lived only in the dashboard signup flow + the rev-166 public /templates marketing page + the rev-169 per-template detail pages. MCP hosts driving the desk programmatically — particularly the upcoming MCP server (Q3 #1) that wraps /api/v1 — needed a machine-readable templates surface so an integration agent could render 'which onboarding template fits my workspace?' in its own UI and apply it programmatically without scraping HTML. Rev 172 closes that gap. Each row carries key + name + description + memoryCount + signalCount + url + the full memories[] + signals[] arrays. No auth — public marketing surface (same model as /api/v1/badge.svg, /api/v1/roadmap-*, /api/v1/changelog, /api/v1/blog). Cache-control public, max-age=300, s-maxage=1800. Pairs with /roadmap-items (planned) + /roadmap-votes (most-requested) + /changelog (shipped) + /blog (brand voice) + /onboarding-templates (industry-fit) as the now-five-axis public marketing surface on the protocol-bound side. Closes the named rev-171 MCP-server protocol-translation work at the templates axis — the upcoming MCP server has nothing left to design across the public marketing v1 cluster.
Templates page count + radar copy refresh + visual polishTemplates page count copy bumps 'nineteen verticals today' → 'twenty-one verticals today' across hero, metadata title, OpenGraph + Twitter description, JSON-LD CollectionPage block, and the templates-cta. Two new keyword hints on the per-vertical chip line (Franchise `Per-location P&L · brand-standard · regional cadence · franchisee retention`; Financial advisor `KYC · suitability · annual review · fiduciary documentation`). Eight new SEO keywords (`AI for franchise operators`, `AI for multi-location retail`, `AI for boutique fitness chains`, `AI for QSR franchises`, `AI for financial advisors`, `AI for RIAs`, `AI for insurance brokers`, `AI for regulated professional services`). 'Don't see your vertical?' next-radar list refreshes — replaced with direct-trade food/beverage (small-batch coffee, cheese, single-origin chocolate), small construction / general contracting, and outdoor recreation (gear shops, guide services, charter operators). New API hint chip on the templates CTA names the new /api/v1/onboarding-templates endpoint inline so integration-minded readers discover it. New focus-visible accessibility ring on every templates-page interactive element (chip links, expand summary, CTA buttons) so keyboard-only operators land cleanly — mirrors the rev-38 dashboard accessibility pattern.