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

rev 1702026-05-08

Two more industry onboarding templates (B2B services / consultative sales + Home services platforms) + server-side per-rev link index on /changelog for crawler discoverability + JSON-LD CollectionPage + ItemList structured data on /templates and /integrations — closes the rev-169 named next-sprint candidates (further industry templates AND /changelog SSR'd page link to per-rev pages) at two more verticals + the SSR'd discoverability axis + opens the structured-data axis on the public marketing trio — 92nd unbroken cadence rev

Two more onboarding templates — B2B services + Home services platformsBrings the templates cluster to seventeen named verticals. B2B services / consultative sales closes the named rev-169 next-sprint candidate (B2B services with long sales cycles) at the sixteenth vertical: 4 high-importance memory entries (named-next-commitment buyer communication, multi-stakeholder layer-up champion rule, 14-day pipeline-stall red flag, outcome-bound proposal scope rule) + 1 sample proposal-stage stakeholder feedback signal. Home services platforms closes the named rev-169 next-sprint candidate (home services platforms — HVAC / plumbing / electrical adjacent at the platform tier) at the seventeenth vertical: 4 high-importance memory entries (named-technician customer confirmation, parts/labour quote transparency, 90-day callback red flag, 24-hour-after-invoice review-request cadence) + 1 sample dispatch coordination signal. Two new OnboardingTemplateKey enum values (b2b_services, home_services) extend the rev-19 pattern.
Server-side per-rev link index on /changelogCloses the named rev-169 next-sprint candidate (/changelog page link to per-rev pages on the SSR'd HTML — adding it server-side too would let crawlers discover the per-rev URL even without JS). The rev-169 'Open page →' link lives inside the rev-101 'use client' ChangelogList component which can mask discoverability for crawlers that don't fully render the React tree. Rev 170 adds a plain server-rendered <nav> + <ol> at the bottom of /changelog with one anchor per rev that guarantees every per-rev URL lands in the SSR'd HTML response body regardless of JS execution. Pure SSR, zero client-side cost. Visually tucked as an 'All revisions' appendix under the rev-101 client list so it doesn't compete with the existing search + permalink surface above. Closes the SSR'd discoverability axis on the rev-169 per-rev detail page primitive.
JSON-LD CollectionPage + ItemList structured data on /templates and /integrationsPairs with the rev-103 /blog/[slug] Article markup as the second + third axes of the structured-data story across the public marketing trio. The /templates page emits a CollectionPage with an ItemList of every shipped template (name, description, URL); the /integrations page emits a CollectionPage with an ItemList of every channel (axis-prefixed name + auth model in description). Google + AI tooling discovery systems that scrape schema.org markup now see every template + every integration channel with one fetch instead of having to render the React tree. Procurement teams searching for 'AI workspace integrations' or 'Loop Desk templates by vertical' land on the matching page with full structured-data context, not just title + description. Marketing surface — pairs with the rev-167/168/169 dynamic OG cards (rich previews) and the rev-103 / rev-105 / rev-107 / rev-108 blog index entries (per-axis discoverability) for the full SEO + sharable-card story across every public marketing surface.
Templates + integrations + CTA copy refresh/templates page count copy bumps 'fifteen verticals today' → 'seventeen verticals today' across hero, metadata title, OpenGraph + Twitter description, and the templates-cta. Two new keyword hints on the per-vertical chip line (B2B services 'Pipeline · stakeholders · proposals · expansion'; Home services 'Dispatch · technicians · quotes · callbacks'). Four new SEO keywords (AI for B2B services, AI for home services platforms, AI for HVAC contractors, AI for plumbing companies). 'Don't see your vertical?' radar list refreshes — replaced with creator economy infrastructure (newsletters / membership platforms), small manufacturing / craft production, and franchise-model multi-location operators now that B2B services + home services are shipped. Sitemap gains 2 new per-template detail pages automatically (priority 0.55, monthly) since it reads from ONBOARDING_TEMPLATES directly.