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

rev 1712026-05-08

Two more industry onboarding templates (Creator economy infrastructure + Small manufacturing / craft production) + FAQPage JSON-LD on every /templates/[key] detail page + initials-avatar block on per-author OG images + Organization + WebSite + SoftwareApplication JSON-LD on the landing page — closes both load-bearing rev-170 named next-sprint candidates (further industry templates AND per-vertical FAQ schema on /templates/[key] pages AND per-author avatars in OG images via next/og) and opens the structured-data axis on the landing page itself for the first time — 93rd unbroken cadence rev

Two more onboarding templates — Creator economy infrastructure + Small manufacturing / craft productionCloses the named rev-170 next-sprint candidate (further industry templates — creator economy infrastructure, small manufacturing / craft production) at two more underserved SMB segments. Creator economy infrastructure (newsletter operators, membership platforms, community-led media — 4 high-importance memory entries: named-relationship subscriber communication, 72h owned-channel platform-risk syndication rule, $35 CPM sponsorship floor, three-opens-no-clicks-30-days subscriber churn red flag + 1 sample paid-tier downgrade feedback signal) AND Small manufacturing / craft production (owner-led manufacturers, craft producers, small-batch CNC / leather / textile / ceramics / specialty food — 4 high-importance memory entries: named-maker production communication, worst-case lead-time honesty rule, 35% supplier-concentration red flag, sampled defect-rate quality audit cadence + 1 sample B2B custom-request feedback signal). Two new OnboardingTemplateKey enum values (creator_infra, small_manufacturing) extend the rev-19 pattern. The templates cluster is now nineteen 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 — newsletter operators / membership platforms where platform-risk + subscriber-cadence anxiety are 2026 market-table-stakes, and small manufacturing / craft producers where named-maker attribution + supplier-concentration discipline are the load-bearing differentiators against the platform-tier marketplaces.
Per-vertical FAQPage JSON-LD on every /templates/[key] detail pageCloses the named rev-170 next-sprint candidate (per-vertical FAQ schema on /templates/[key] pages with sample procurement questions per vertical). Procurement reviewers + AI tooling discovery systems consuming schema.org markup can now answer five named procurement-conscious questions per vertical without parsing the page body: (1) does Loop Desk know my industry on day 1, (2) what gets pre-loaded, (3) is the pre-loaded knowledge editable, (4) can the operator skip a template, (5) how does Loop Desk's flat-fee compare to per-cycle-credit AI tools at the per-vertical axis. Pure server-rendered <script type='application/ld+json'> block generated at request time from the existing template data + a small per-vertical answer-template helper. Mirrors the rev-103 Article markup pattern and the rev-170 CollectionPage + ItemList markup at the per-template detail axis. Strategic significance: closes the structured-data symmetry on the per-template detail pages alongside the rev-169 per-template OG cards (rich previews) + rev-170 ItemList markup on the index — the templates cluster is now structured-data-complete on every read surface.
Initials-avatar block on per-author OG imagesCloses the named rev-170 next-sprint candidate (per-author avatars in OG images via next/og — surfacing actual avatars in the share card via next/og would close the OG-image-polish loop on the byline axis). Until rev 171 the rev-168 per-author OG cards surfaced the author's name as the headline + post-count as the subline + three stat chips, but had no identity-anchor visual element. Rev 171 closes the loop with an 88px circular avatar block in the eyebrow row of every per-author OG card. Two render paths: (a) when the author has registered an avatarUrl in data/blog-authors.json or via authorAvatar frontmatter, the avatar URL renders inline as an <img>; (b) the always-renderable fallback is an initials circle (first + last initial for two-name authors, first two characters for single-name authors). The shared renderOg helper in src/lib/og-image.tsx gains an optional avatar input so the per-author route handler is the only consumer that opts in — every other public-marketing OG card keeps its existing typographic card. Strategic significance: closes the OG-image-polish loop on the byline axis at the lowest possible primitive — no avatar-fetching infrastructure required for the always-renderable fallback, and the optional imageUrl path means a contributor who registers a Gravatar / CDN URL gets a real photo without re-deploying.
Organization + WebSite + SoftwareApplication JSON-LD on the landing pageOpens the schema.org structured-data axis on the most operator-loaded public surface for the first time. Until rev 171 the rev-103 /blog/[slug] Article markup, rev-170 /templates + /integrations CollectionPage + ItemList markup, and rev-171 /templates/[key] FAQPage markup together shipped structured data on every public marketing surface — except the landing page itself. The Organization block names the brand + logo + sameAs links so AI tooling discovery systems answer 'what is Loop Desk' with one fetch; the WebSite block surfaces a SearchAction shape so Google + AI tooling can render an inline blog search box; the SoftwareApplication block names the flat-fee positioning at the structured-data axis explicitly so procurement reviewers + AI tooling roundup newsletters scraping the landing page see 'free tier; flat-fee paid tiers with no per-cycle credits' in machine-readable form. Strategic significance: every public marketing surface now ships schema.org structured data — landing (rev 171), templates index (rev 170), templates detail (rev 171 FAQPage), integrations (rev 170), blog post (rev 103), per-author archive (rev 105 + rev 171 OG avatar). Pairs with rev-167 / 168 / 169 dynamic OG cards as the full SEO + sharable-card story.