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

rev 1762026-05-08Accelerating

Two more industry onboarding templates (Independent veterinary practices + Small distillery / craft brewery) + per-template launch metadata + sitemap freshness boost (templates launched within 90d carry priority 0.7 + lastModified at launch date vs 0.55 default) + 'New' pill on the /templates index for verticals shipped within the last 60 days + 'Added in rev N' trailing fact on every /templates/[key] detail page header + sixth FAQPage JSON-LD Q&A naming the launch rev + date so Google search snippets show recency context — closes both rev-175 named next-sprint candidates (further industry templates AND per-template detail page sitemap.xml priority bump for newly-launched verticals) at two more underserved verticals where regulated discipline (DEA controlled-substance reconciliation on the vet side, TTB + tied-house compliance on the distillery side) is the load-bearing differentiator + opens a recency-signalling axis on the public marketing surface across three coordinated surfaces (sitemap, structured data, on-page chrome) — 98th unbroken cadence rev (rev 176)

Two more onboarding templates — Independent veterinary practices + Small distillery / craft breweryCloses the named rev-175 next-sprint candidate at two more underserved SMB segments. Independent veterinary practices (companion-animal vets, exotics, small-animal hospitals — 4 high-importance memory entries: estimate-with-named-DVM-and-price-range discipline before any procedure begins, 14-day post-due wellness recall cadence with named-DVM attribution, welfare-led end-of-life conversation framing rule (never lead with cost), DEA + state-board controlled-substance weekly reconciliation compliance + 1 sample estimate-vs-final-invoice gap signal). Small distillery / craft brewery (owner-operated craft distilleries, microbreweries, small-batch producers — 4 high-importance memory entries: weekly channel-mix discipline with separate margin tracking on taproom vs distribution, TTB + state production reporting cadence with hard 5-business-day reminders, tied-house red flag rule on any inducement-shaped value transfer to retailers/distributors, 15% production-yield deviation red flag + 1 sample distributor free-keg promotional inducement signal). Two new OnboardingTemplateKey enum values (veterinary, craft_distillery) extend the rev-19 enum without migration. The templates cluster is now twenty-seven named verticals deep — closes the day-1 starvation-point story across two more underserved owner-led segments where regulated discipline (DEA controlled-substance handling + welfare-led conversation framing on the vet side, TTB excise reporting + tied-house enforcement on the distillery side) is the load-bearing differentiator against generic AI tools that don't know the regulatory vocabulary.
Sitemap freshness boost for newly-launched templatesCloses the named rev-175 next-sprint candidate ('per-template detail page sitemap.xml priority bump for newly-launched verticals'). Templates whose launch date (per the new TEMPLATE_LAUNCH metadata map) is within the last 90 days now carry priority 0.7 + changeFrequency weekly + lastModified at the launch date — vs the rev-169 default of priority 0.55 + changeFrequency monthly + lastModified at request time. Crawlers + AI tooling discovery systems that prioritise recently-changed pages now see newly-launched verticals as fresher than the long-tail of older verticals. Pairs with the rev-176 'New' pill on /templates and the rev-176 FAQPage JSON-LD launch-date Q&A so search-engine recency signals align across all three surfaces (sitemap freshness, structured data, on-page chrome). The TEMPLATE_LAUNCH map sits as a sibling Record next to ONBOARDING_TEMPLATES — zero schema cost, no migration, no touch on the 25 existing template entries. Future templates set their entry explicitly when they ship; templates without an entry fall back to the standard 0.55 priority with `new Date()` as lastModified.
'New' pill on /templates + 'Added in rev N' header chip on every /templates/[key] detail pageVisual companion to the rev-176 sitemap freshness boost so the recency signal carries through to the visitor's eye, not just the crawler's. /templates index renders a brand-color 'New' pill in the heading row of every template card whose launch date is within the last 60 days (a tighter window than the 90-day sitemap window so visitors see only the truly recent additions). The pill carries a `title` attribute naming the launch rev for hover discoverability. /templates/[key] detail pages render an 'Added in rev N' trailing chip in the header stat row alongside the existing memory count + signal count + share chip, so a procurement reviewer landing from a search-result snippet sees recency at-a-glance. Both surfaces are pure server-rendered — zero client-side JS cost, zero schema cost, identical SSR + first-paint render. Pairs with the rev-176 FAQPage JSON-LD launch-date Q&A as the third coordinated recency surface.
FAQPage JSON-LD extended with sixth launch-date Q&A on every /templates/[key] pagePure additive on top of the rev-171 FAQPage JSON-LD primitive (which shipped 5 procurement-conscious questions per vertical: 'will it know my industry on day 1', 'what gets pre-loaded', 'is the pre-loaded knowledge editable', 'can I skip a template', 'how does flat-fee compare to per-cycle credits'). Rev 176 appends a sixth Q&A — 'When did the [Vertical] template ship?' — answered with the launch rev + ISO date pulled from the rev-176 TEMPLATE_LAUNCH metadata map. Procurement reviewers + AI tooling discovery systems consuming schema.org markup get explicit recency context in the same fetch they already make for the rev-171 FAQ block. Search-engine snippets that surface FAQPage 'Q' rows in rich results now have a freshness Q to surface alongside the procurement-conscious ones. Strategic significance: the rev-103 / rev-170 / rev-171 / rev-174 / rev-175 structured-data primitives all answered 'what is this page' for crawlers; rev 176 answers 'how recently has it changed' as a structured signal. Pairs with the rev-176 sitemap freshness boost (priority + lastModified) and the rev-176 'New' pill (visible on-page chrome) as the third coordinated recency surface.