reference

Glossary

Plain-English definitions for every Looper term — credits, BYOK, AEO, mission, drift, and more.

A

A/B test: Why use this

Understand A/B tests so you can stop guessing which subject line or CTA wins and let the data call it.

Benefits:

Looper tracks conversions and calls the winner at statistical confidence.

Test subject lines, page copy, or CTAs without rolling your own setup.

Configure at /experiments; results show inline.

An A/B test (Experiment) is a controlled test between two variants (subject line, page copy, CTA). Looper tracks conversions and calls a winner once statistical confidence is reached. Configure at /experiments.
Ad audience: Why use this

Understand Ad audiences so you stop rewriting the same persona over and over in every ad you generate.

Benefits:

Define a persona once, reuse it across every ad-copy generation.

Keep targeting consistent across campaigns and channels.

Build a library of saved audiences for quick selection at generation time.

An Ad audience is a saved target persona (demographics, pain points, jobs to be done) that ad-copy generators reference. Define once at /ad-audiences and reuse across ads.
AEO: Why use this

Understand AEO so you can win citations inside ChatGPT, Claude, Gemini, and Perplexity — where buyers increasingly start their research.

Benefits:

Track whether your brand appears in AI answers for the queries that matter.

Treat AEO as the LLM-era analog of SEO and prioritize accordingly.

See exactly where you're cited (and where competitors are) at /aeo.

AEO stands for Answer Engine Optimization. It tracks whether your brand gets cited in answers from ChatGPT, Claude, Gemini, and Perplexity for the queries you care about. AEO is the LLM-era analog of SEO. Monitor citations at /aeo.
Affiliate code: Why use this

Understand Affiliate codes so attribution actually works and your affiliates get paid correctly.

Benefits:

Each affiliate gets a unique slug — clean attribution out of the box.

Idempotent tracking means duplicate clicks don't double-count.

Append ?ref=CODE to any tenant URL — affiliates can promote any page.

An Affiliate code is the unique slug each affiliate gets to track their referrals. Append it as ?ref=CODE on any tenant URL. Idempotent commission tracking ensures duplicate clicks do not double-count.
Affiliate program: Why use this

Understand Affiliate programs so you can scale word-of-mouth without building an attribution stack yourself.

Benefits:

One program per tenant keeps configuration simple.

Idempotent commission ledger prevents double-pay.

Pending-to-paid balance flow keeps you and your affiliates on the same page.

An Affiliate program is a referral program with unique referral codes, idempotent commission tracking, and pending-to-paid balance management. One program per tenant. Manage at /commerce/affiliates.
Agency dashboard: Why use this

Understand the Agency dashboard so you can run multiple sub-tenants from one screen instead of switching tabs.

Benefits:

One cross-tenant rollup of AI usage, revenue, and alerts.

Spot which client is over-spending or under-performing at a glance.

Live at /agency, refreshed on every visit.

The Agency dashboard is the cross-tenant rollup that an agency operator sees across every sub-tenant they own. Includes AI usage, revenue, alerts. Open at /agency.
AI workflow builder: Why use this

Understand the AI workflow builder so you can describe an automation in plain English and skip the visual editor.

Benefits:

Faster than dragging nodes manually (chat to workflow JSON via Claude Sonnet).

Output is real workflow JSON you can edit later if needed.

Lowers the bar for non-technical operators to ship automations.

The AI workflow builder is the chat surface that takes a natural-language description and emits a workflow JSON via Claude Sonnet. Faster than dragging nodes manually. Live at /workflows/build.
Approval: Why use this

Understand Approvals so you know how to unblock paused workflows and missions waiting on a human.

Benefits:

Triage every pending approval from one queue at /approvals.

Prevent silent stalls: pending approvals get a daily summary.

Keep humans in the loop where it matters, without slowing down everywhere else.

An Approval is a paused workflow or mission step waiting for human signoff before it can proceed. Triage from /approvals.
Attribution report: Why use this

Understand the Attribution report so you can answer "what's actually driving revenue?" without spreadsheets.

Benefits:

See paid revenue rolled up by payment link, affiliate, coupon, and lead source.

Pick a window (7/30/90/365) that matches your sales cycle.

CSV export for board decks or further analysis.

The Attribution report rolls up paid revenue by payment link, affiliate, coupon, and lead source. Available at /reports/attribution. CSV export available. Default windows: 7 / 30 / 90 / 365 days.
Attribution window: Why use this

Understand Attribution windows so you can credit revenue to the source that earned it, not the one that ran last.

Benefits:

Pick the right lookback (7/30/90/365) for your buying cycle.

Stop under-crediting top-of-funnel sources that closed weeks later.

Adjust per report at /reports/attribution; no schema change needed.

The Attribution window is the lookback period the Attribution report uses to credit revenue back to sources. Default windows: 7, 30, 90, 365 days. Change in the report at /reports/attribution.
Audit log: Why use this

Understand the Audit log so you can answer "who did what, when?" in a heartbeat.

Benefits:

Timestamped history of every important action — fast incident response.

Two surfaces: workspace audit (/settings/audit-log) and security audit (/security/audit-log).

Critical for compliance reviews and post-mortems.

The Audit log is a timestamped history of every important action in your workspace: who did what, when. Two surfaces: /settings/audit-log (workspace) and /security/audit-log (security-flagged events).
Auto-assign: Why use this

Understand Auto-assign so inbound leads land on the right person automatically — no manual routing.

Benefits:

Route by industry, region, or source automatically.

Eliminate the "who's covering this?" Slack thread.

Scale inbound past one person without dropping leads.

Auto-assign rules route new leads to a teammate or queue based on criteria (industry, region, source). Set up at /leads/auto-assign. Useful when more than one person handles inbound.
Automation: Why use this

Understand Automations so you can turn on Looper's prebuilt logic without writing custom Workflows.

Benefits:

Pre-built and tested — flip a switch, get value.

No need to design a workflow from scratch for common patterns.

Build a custom Workflow only when no Automation fits.

An Automation is a pre-built workflow that ships with Looper and that you can turn on or off without building from scratch. The set lives at /automations. For custom logic, build a Workflow instead.

B

Bespoke mode: Why use this

Understand Bespoke mode so you pick the right quality tier for the moment — higher quality where it counts, faster everywhere else.

Benefits:

Claude Opus quality for content you'll actually ship.

Pick on demand; not the default (cost matters).

Fast mode for first drafts, Bespoke for the keep.

Bespoke mode is the higher-quality option in site generation. Instead of Fast mode (Haiku, cheap, seconds) Bespoke runs Claude Opus, takes longer, and produces site copy with more nuance. Choose it at /sites when generating a new site. Costs more credits.
Blog: Why use this

Understand Blog so you can publish SEO-friendly long-form content without leaving Looper.

Benefits:

Markdown body plus SEO override fields means clean control over meta.

Per-tenant publishing — every customer gets their own blog.

Auto-generated metadata via generateMetadata for the pages you don't override.

A Blog is your per-tenant publishing surface with markdown body, SEO override fields, tags, and reading-time. Posts get SEO metadata via generateMetadata. Manage at /blogs. Public URLs: /sites/blog/[tenantSlug] and /sites/blog/[tenantSlug]/[postSlug].
Brand kit: Why use this

Understand Brand kit so every site, post, ad, and email Looper generates looks like you, not a generic AI.

Benefits:

Set logo, palette, fonts, taglines once — every output inherits them.

Stop dragging the same logo into every generated asset.

Agencies can replicate brand kits per client via snapshots.

A Brand kit is your stored set of brand assets: logo, color palette, fonts, taglines, and usage notes. Every site, blog post, ad, and email Looper generates references the brand kit by default. Set it up once at /brand-kit and every output inherits the look.
Brand voice: Why use this

Understand Brand voice so AI-generated writing sounds like you across every surface.

Benefits:

One profile per audience (Friendly B2C, Technical B2B, Founder voice) — pick at generation time.

Consistency across blog posts, ads, emails, sequences.

Edit once, propagate everywhere.

A Brand voice is a saved tone profile that AI writing surfaces use to keep your copy consistent. Define one per audience or product (e.g. "Friendly B2C," "Technical B2B," "Founder voice"). Configure at /brand-voices.
Business blueprint: Why use this

Understand Business blueprint because every generative surface in Looper reads it before generating anything — fill it in once and outputs improve everywhere.

Benefits:

Set niche, audience, offers, voice once — better outputs across the platform.

Skip describing your business in every prompt.

Edit in one place; every downstream surface picks up the change.

The Business blueprint is the structured profile of your business (name, niche, audience, offers, voice) that every generative surface references. Fill in at /onboarding/profile.
BYOD: Why use this

Understand BYOD so agents can work against your real external data instead of just what's in Looper.

Benefits:

Connect DB, sheet, file store, or API — agents read in real time.

Avoid bulk-importing data you already have somewhere else.

One connection point at /data-sources serves every agent.

BYOD stands for Bring Your Own Data. It is the pattern for connecting an external data source (DB, sheet, file store, API) so agents can read it. Configure at /data-sources.
BYOK: Why use this

Understand BYOK so you can skip Looper's credit markup once your AI spend justifies the setup.

Benefits:

Pay the underlying model provider directly — no markup.

Use your own Anthropic, OpenAI, or Google account and rate limits.

Switch back to credits anytime at /settings/billing-mode.

BYOK stands for "Bring Your Own Key." Instead of paying Looper for AI usage in credits, you connect your own Anthropic, OpenAI, or Google API key and Looper charges the model provider directly. Owners set BYOK keys in /settings/billing-mode. BYOK skips the credit markup but still costs you whatever the underlying model costs.

C

Chat widget: Why use this

Understanding Chat widgets lets you put an AI front desk on any site so visitors get answers and leads convert in real time.

Benefits:

Answer common questions without a human on shift

Qualify visitors and hand off to a human only when needed

Power each widget with its own knowledge base and agent

Capture leads at the moment of intent, not after a contact form

A Chat widget is an embeddable AI chat bubble you drop on any site. It can answer FAQs, qualify leads, and hand off to humans. Configure at /widgets. Each widget has its own knowledge base and agent.
Client portal: Why use this

Understand Client portal so you can give every customer a single white-label home for their bookings, orders, and certificates.

Benefits:

Customers self-serve every artifact you've shared with them.

White-label means your brand, not Looper's.

Cuts down on "where do I find my receipt?" support emails.

The Client portal is a white-label area where each of your customers can see their bookings, orders, certificates, and any other artifacts you have shared with them. Configure branding at /portal-settings. Public URL: /portal/[tenantSlug].
Community: Why use this

Understand Communities so you can run a Skool or Circle-style discussion space inside your workspace.

Benefits:

Scoped per tenant — your community, your brand.

Channels and threads keep discussions organized.

Email-keyed membership ties community access to customer records.

A Community is a Skool or Circle style discussion space with channels and threads, scoped to a tenant. Members are email-keyed. Build at /communities-admin. Public URL: /community/[tenantSlug]/[communitySlug].
Competitor watchlist: Why use this

Understand Competitor watchlist so you spot competitor changes before your customers do.

Benefits:

Periodic screenshot diffs catch homepage and pricing changes.

Pricing and feature snapshots make comparisons easy.

Ad library at /ad-intel completes the picture.

The Competitor watchlist tracks competitors with periodic page screenshots and diffs, plus pricing and feature snapshots. Add competitors at /competitors. Their ad library lands at /ad-intel.
Computer-use agent: Why use this

Understand the Computer-use agent so you have an option for repeating browser tasks no API supports.

Benefits:

Drives a real browser like a human (click, scroll, fill, screenshot).

Reach for it only when no native integration exists.

Slower than API calls but unblocks otherwise impossible automations.

The computer-use agent is an Anthropic-powered AI that drives a real browser session: clicks, scrolls, fills forms, takes screenshots. Use it for repeating tasks no API supports. Configure at /computer-use. Slower than direct API calls; only reach for it when no integration is available.
Conversation analytics: Why use this

Understand Conversation analytics so you can see what's happening in chat and voice without listening to every recording.

Benefits:

Resolution rate, time-to-first-response, sentiment, deflection — at a glance.

Find which channels are over- or under-performing.

Justify staffing decisions with hard numbers.

Conversation analytics is the rollup of metrics on chat-widget and voice conversations: resolution rate, time-to-first-response, sentiment, deflection rate. Available inside /analytics.
Countdown timer: Why use this

Understand Countdown timers so you can drive urgency around launches, sales, and deadlines.

Benefits:

Embed on a landing page or share a standalone link.

Live countdowns convert better than static copy.

Manage at /countdown-timers; no separate timer tool needed.

A Countdown timer is a live countdown you embed on a page or share as a standalone link. Use to create urgency around a launch, sale, or deadline. Manage at /countdown-timers. Public URL: /c/[tenantSlug]/[timerSlug].
Coupon: Why use this

Understand Coupons so you can run discount promotions with the right guardrails (cap, expiry, usage limit).

Benefits:

Percent or fixed amount — match the promo to the offer.

Optional cap and expiry prevent runaway discount abuse.

Tracked in attribution so you can measure promo-driven revenue.

A Coupon is a discount code (percent or fixed amount) applied at checkout. Optional cap, expiry, usage limit. Manage at /commerce/coupons.
Course: Why use this

Understand Courses so you can sell or give away structured learning without a separate LMS.

Benefits:

Email-keyed enrollment ties students to your CRM.

Per-lesson progress so students see their own status.

Optional auto-enroll on commerce-product purchase for one-click access.

A Course is a sequence of lessons your customers (members) enroll in. Email-keyed enrollment, per-lesson progress, optional auto-enroll on commerce-product purchase. Build at /courses-admin. Public catalog: /courses/[tenantSlug]/[courseSlug].
Creative intel: Why use this

Understand Creative intel so you can see which themes and hooks actually drive engagement across ads, posts, and emails.

Benefits:

Cross-source signal aggregation — not just one channel.

Identify your highest-performing patterns and double down.

Stop guessing which campaign worked; the data is in one view.

Creative intel aggregates signals across your generated creative (ads, posts, emails) so you can see which themes, hooks, and assets are driving engagement. Open at /creative-intel.
Creator dashboard: Why use this

Understand Creator dashboard so you can manage marketplace listings, earnings, and payouts in one place.

Benefits:

One screen for everything you sell on the marketplace.

Track earnings and pending payouts without spreadsheets.

Lives at /marketplace/creator — bookmark it.

The Creator dashboard is the surface where an agency or independent creator manages their marketplace listings, earnings, and payouts. Live at /marketplace/creator.
Credential: Why use this

Understand Credentials so you can give learners and badge earners a verifiable certificate that builds their resume — and your reputation.

Benefits:

Auto-issued on course completion or badge earn.

Public verification URL anyone can use to confirm authenticity.

Strong social-proof signal customers share organically.

A Credential is a verifiable digital certificate Looper auto-issues when a customer completes a course or earns a badge. It comes with a public verification URL anyone can use to confirm authenticity. Issue and manage at /credentials-admin. Public URL: /credential/[publicToken].
Credit pack: Why use this

Understand Credit packs so you can pre-buy AI capacity at a better per-credit price.

Benefits:

Tiered pricing — more credits per dollar at higher tiers.

No expiry; sit unused until you need them.

Buy at /settings/credits, top up anytime.

A Credit pack is a purchased bundle of credits with a tiered price (more credits per dollar at higher tiers). Buy from /settings/credits. No expiry.
Credits: Why use this

Understand Credits so you can budget AI usage accurately without translating tokens in your head.

Benefits:

Prepaid units; predictable spend.

Cap monthly burn at /settings/limits to prevent surprise bills.

Switch to BYOK once volume justifies skipping the markup.

Credits are Looper's prepaid AI usage units. One credit roughly maps to a fixed amount of model inference, with the exchange rate set by the platform and visible at /settings/credits. Credits are bought in packs, drawn down by every AI run, and can be capped per month at /settings/limits. The alternative is BYOK.
Custom Agent: Why use this

Understand Custom Agents so you can build a reusable AI persona once and call it anywhere via @mention.

Benefits:

Configure system prompt, allowed tools, and KB once, use many times.

Call agents in chat with @mention — no copy-pasting prompts.

Audit every run in /agents/logs to see what actually happened.

A Custom Agent is a reusable AI persona you configure with a system prompt, allowed tools, and a knowledge base. Agents are available in chat with @mentions. Manage at /agents. View execution history at /agents/logs.
Custom Object: Why use this

Understand Custom Objects so you can model your business in your own terms when leads / companies / deals don't fit.

Benefits:

Define your own record type (Patient, Property, Project, anything).

Inherits CRM mechanics (tags, views, automations) for free.

One schema definition lets the whole team work the new object.

A Custom Object is a record type you define yourself when the built-in objects (leads, companies, deals) do not fit. For example, a vet clinic might create a "Patient" object with pet fields. Define schemas at /custom-objects, then create and view records like any other CRM entity.

D

Deliverability: Why use this

Understand Deliverability so your emails actually reach the inbox instead of dying in spam.

Benefits:

Track open / click / bounce / spam-complaint rates in one view.

Surface fixes (warmup, list hygiene, subject patterns) before sender reputation tanks.

Avoid landing on email blocklists that take weeks to escape.

Deliverability is the chance your email reaches the inbox instead of spam or promotions. Looper tracks open / click / bounce / spam-complaint rates and surfaces fixes (warmup, list hygiene, subject line patterns) at /deliverability.
Dispatch: Why use this

Understand Dispatch so each notification lands on the right channel — not all of them, not none.

Benefits:

Pick channel per notification type (email, SMS, Slack, in-app).

Stop drowning teammates in duplicate alerts.

Configure once at /settings/dispatch; routing applies everywhere.

Dispatch is the routing layer that decides which channel (email, SMS, Slack, in-app) each notification lands in. Configure at /settings/dispatch.

E

Estimate: Why use this

Understand Estimates so you can quote a client cleanly and convert to an invoice the moment they say yes.

Benefits:

Same line-item structure as an invoice — convert in one click.

No payment hook on the estimate; safer for "thinking it over" stage.

Tracked alongside invoices for full revenue visibility.

An Estimate is a quote with the same line-item structure as an invoice but no payment hook. Convert to an invoice once the client accepts. Manage at /commerce/invoices.
Evergreen queue: Why use this

Understand Evergreen queue so your social channels stay alive even when you stop writing new posts.

Benefits:

Drop posts in once, they recycle on your chosen schedule.

Keep accounts warm without weekly content sprints.

Pause anytime when you want to switch to live posting.

The Evergreen queue is a pool of social posts that auto-recycles on a schedule. Drop posts in once; they cycle out at your chosen cadence. Manage at /social-content.
Export: Why use this

Understand Exports so you can leave with your data anytime — for backup, audit, or migration.

Benefits:

Per-table export at /exports as CSV or JSON.

Full-tenant GDPR-style export at /settings/privacy.

Founders cannot bypass this; the data is yours.

An Export is a downloadable dump of one or more tables (leads, deals, custom records, orders). CSV or JSON. Initiate from /exports. Full-tenant GDPR-style export available from /settings/privacy.

F

Forecast: Why use this

Understand Forecast so you can answer "what's our pipeline going to close this quarter?" with a number, not a guess.

Benefits:

Projects revenue by expected close date and stage probability.

Use it for monthly and quarterly planning conversations.

Open at /forecast — refreshes from current pipeline state.

The Forecast view projects pipeline revenue by expected close date, weighted by stage probability. Useful for monthly and quarterly planning. Open at /forecast.
Form: Why use this

Understand Forms so you can capture leads from any site, link, or campaign and land them in your CRM automatically.

Benefits:

Custom fields match your CRM, no manual mapping later.

Embed, share as a link, or fire from a campaign — pick the channel.

Submissions land directly in /leads with full attribution.

A Form is a lead-capture form with custom fields you can embed on a site, share as a link, or fire from a campaign. Submissions land in your CRM. Manage at /forms.
Funnel: Why use this

Understand Funnels so you can move prospects through multi-step qualification without losing them at step one.

Benefits:

Each step asks for a small commitment before the next.

Higher conversion than a single giant form.

Public URL pattern means share-ready out of the box.

A Funnel is a multi-step page sequence designed to capture leads and qualify them step by step. Each step asks for a small commitment before the next. Build funnels at /funnels. Public URL pattern: /f/[tenantSlug]/[funnelSlug].

G

GEO: Why use this

Understand GEO so you structure content for citation inside LLM-generated answers.

Benefits:

Track GEO ranking — see whether LLMs are quoting you.

Practice content structuring that makes LLMs more likely to cite.

Pair with AEO for full LLM-era visibility.

GEO stands for Generative Engine Optimization. It is the practice of structuring content so that LLMs cite or paraphrase you when generating answers. Track GEO ranking at /geo. Closely related to AEO; GEO focuses on the content side while AEO focuses on the citation side.

H

Haiku / Sonnet / Opus: Why use this

Understand Haiku / Sonnet / Opus so you stop overpaying for tasks that don't need the top model.

Benefits:

Looper auto-routes per task — Haiku fast and cheap, Opus high-quality, Sonnet in between.

Override anywhere quality matters (Bespoke mode uses Opus).

Know the trade-off (cost vs quality) when you pick manually.

Haiku, Sonnet, and Opus are the three tiers of Anthropic''s Claude model family. Haiku is fastest and cheapest; Opus is highest quality and most expensive. Looper routes per-task to the right one. Fast-mode features use Haiku; Bespoke uses Opus.
HIPAA tier: Why use this

Understand HIPAA tier so you can close healthcare deals that other tools can't touch.

Benefits:

BAA-backed model routing keeps PHI inside compliant providers.

Audit-log retention meets HIPAA requirements out of the box.

PHI scrubbing in logs prevents accidental data exposure.

HIPAA tier is a higher-trust security mode for healthcare data. Enables BAA-backed model routing, audit-log retention, and PHI scrubbing in logs. Turn on at /security/hipaa. Owner-only.

I

Image gen: Why use this

Understand Image gen so you produce brand-consistent images without firing up Photoshop or hopping to another tool.

Benefits:

Brand-aware (uses your brand kit by default).

/images is the generation surface; /image-gen is the library.

Pick aspect ratio and model per prompt.

Image gen produces brand-consistent images from a text prompt. /images is the designer-tuned brand-aware surface; /image-gen is the persistent library where outputs live. Both consume credits or BYOK calls.
Inbound webhook: Why use this

Understand Inbound webhooks so external services can push data or events into Looper without polling.

Benefits:

Per-tenant URL — no shared secrets to manage.

Trigger a workflow or insert data from any external source.

Generate and rotate at /settings/inbound.

An Inbound webhook is a URL external services can POST to in order to trigger a Looper workflow or insert data. Generate per-tenant at /settings/inbound.
Install: Why use this

Understand Installs so you can see and manage everything you've added from the marketplace or library.

Benefits:

One screen for every installed skill, agent, template, recipe.

Remove what you don't use to keep the surface clean.

Re-install with one click later if needed.

An Install is a skill, agent, template, or recipe you have added to your workspace from the marketplace or library. Manage what is installed at /installs.
Invoice: Why use this

Understand Invoices so you can bill customers cleanly with a state machine that tracks every status from draft to paid.

Benefits:

Built-in state machine: draft, sent, paid, void.

Optional pay-via-Stripe link for one-click collection.

Hosted public URL means customers see it without logging in.

An Invoice is a bill you send to a customer with line items, totals, and an optional pay-via-Stripe link. State machine: draft, sent, paid, void. Manage at /commerce/invoices. Public URL: /i/[tenantSlug]/[publicToken].

K

Knowledge base: Why use this

Understanding the Knowledge base concept lets you feed your agents the right documents so answers are grounded in your content, not guesses.

Benefits:

Ground agent answers in your own source-of-truth documents

Reduce hallucinations by pointing retrieval at vetted PDFs and URLs

Reuse one library across every widget and agent in the tenant

Update one doc and every dependent agent gets the new context

A Knowledge base is a collection of documents (PDFs, MD, HTML, URLs) that agents and chat widgets retrieve from at runtime. Manage at /knowledge.

L

Lead discovery: Why use this

Knowing how Lead discovery works lets you fill your pipeline from Apollo, GitHub, Places, and the open web without manual prospecting.

Benefits:

Find net-new leads across four sources from one Mission

Replace hours of manual sourcing with a single run

Match your ICP with structured criteria, not gut feel

Feed results straight into pipelines and sequences

Lead discovery is the AI-driven workflow that finds new leads matching your criteria across Apollo, GitHub, Google Places, and broader web searches. Runs as a Mission. Start at /leads/discover.
Listings: Why use this

Understanding Listings shows you which directories carry your business and where you are leaking calls because of gaps.

Benefits:

Track presence across Google, Yelp, Bing in one view

Catch missing or inconsistent NAP data before it hurts ranking

Use the 10-point GBP optimizer to fix what costs you the most

Tie reputation work to local search visibility

Listings tracks your business presence across third-party directories (Google Business Profile, Yelp, Bing Places). Looper surfaces a 10-point GBP optimizer at /reputation.

M

Magic link: Why use this

Knowing what a Magic link is lets you give affiliates and customers passwordless access without standing up an auth system per portal.

Benefits:

Remove the password friction that kills portal logins

Issue scoped, time-bound access from a single email

Reduce support tickets from forgotten credentials

Stay compliant by not storing extra customer secrets

A Magic link is a one-time sign-in link sent by email that authenticates you without a password. Affiliates and customers use magic links to access their portals.
Manual actions: Why use this

Understanding the Manual actions queue tells you where the AI is uncertain so you can clear judgment calls fast instead of letting them pile up.

Benefits:

Catch low-confidence drafts before they reach customers

Keep autopilot moving by triaging only the exceptions

Train the system over time by approving or rejecting calls

Audit edge cases in one place instead of hunting through inboxes

The Manual actions queue is the list of items the AI flagged for human review (low-confidence drafts, edge cases, escalations). Triage from /manual-actions.
Market research: Why use this

Knowing Market research as a Mission lets you brief any new vertical, city, or competitor set in hours, not weeks.

Benefits:

Skip the manual research swirl on a new market entry

Get demand, competition, pricing, and lead pools in one brief

Run it any time the market shifts, not once a quarter

Hand a structured artifact to sales and ops directly

Market research is an AI-driven scan of a city, vertical, or competitor set that returns a structured brief on demand pockets, competition, pricing, and lead pools. Launched as a Mission from /leads/market-research.
Marketplace mission: Why use this

Understanding Marketplace missions opens a second revenue line: sell your best workflows to other tenants without doing the work yourself.

Benefits:

Turn a proven Mission into a recurring revenue product

Earn per run while buyers run on their own data

Reuse one build across unlimited buyers

Distribute through Looper without standing up your own marketplace

A Marketplace mission is a paid Mission listed in the marketplace. Buyers run it on their own data; sellers earn each run. Browse at /marketplace/missions.
Mission: Why use this

Understanding what a Mission is tells you when to spawn one instead of a Chat or Workflow, so you pick the right tool for the job.

Benefits:

Hand off long, multi-step research and execution to the agent

Run for minutes or hours without you babysitting tokens

Get a reviewable artifact at the end, not a chat scroll

Decompose into sub-agents that work in parallel

A Mission is a long-running AI task you spawn from /missions. It can decompose into sub-agents, run for minutes to hours, and produce an artifact you review. Missions are different from Chat (single-turn back-and-forth) and Workflows (deterministic, no-LLM-required step sequences). Common Missions: lead enrichment, market research, content generation.
Mission template: Why use this

Understanding Mission templates lets you reuse your best setups instead of rebuilding a prompt and tool list every run.

Benefits:

Launch a tuned Mission in one click, not ten

Lock in the prompt, sub-agents, and tools that worked before

Share a known-good starting point across the team

Iterate the template once and every run improves

A Mission template is a reusable starting point for a Mission: prompt, default sub-agents, default tools. Library lives at /missions/templates.
My work: Why use this

Knowing about My work gives you a single inbox for everything that needs you, so nothing slips between tasks, approvals, missions, and leads.

Benefits:

See every assigned item in one consolidated list

Stop tab-switching between leads, tasks, and approvals

Prioritize across surfaces by due date and status

Catch handoffs that fell into another tool

My work is the consolidated view of every task, approval, mission, and lead assigned to you across the workspace. Open at /my-work.

N

Notifications: Why use this

Understanding the Notifications feed lets you tune which events earn your attention so the bell only fires when it matters.

Benefits:

See assignments, approvals, and billing alerts in one place

Route the right events to the right channels

Mute the noise without missing the signal

Audit what fired and when, in one feed

Notifications is the bell-icon feed of recent events: assignments, approvals, mission completions, billing alerts. Manage routing at /settings/notifications.

O

Onboarding: Why use this

Knowing the Onboarding flow exists tells you the fastest path from signup to a working setup with brand, blueprint, and first Mission.

Benefits:

Reach time-to-first-value on day one

Configure the basics in the right order, no guesswork

Get a first Mission running without reading docs

Track setup progress with the welcome checklist

Onboarding is the first-day setup flow that takes you from signup through business blueprint, brand kit, and your first Mission. Tour starts at /onboarding. Setup checklist at /welcome.
Outgoing webhook: Why use this

Understanding Outgoing webhooks lets you push Looper events into your own stack so other systems react in real time.

Benefits:

Fire downstream automations the second an event happens

Connect Looper to any system that accepts a POST

Replace polling with event-driven integrations

Audit deliveries and replay failures from one screen

An Outgoing webhook is a POST Looper sends to a URL you configure when a chosen event happens (lead created, payment received, mission finished). Set up at /settings/webhooks.

P

Payment link: Why use this

Knowing about Payment links gives you a checkout URL you can share anywhere without standing up a storefront.

Benefits:

Take payment from DMs, email, or social in one click

Skip the storefront build for one-off products or plans

Route funds straight to your Stripe Connect balance

Track conversion per link without extra tagging

A Payment link is a hosted checkout URL for a single product or recurring plan. Share it in DMs, email, social, anywhere. Powered by Stripe Connect direct charges. Create from /commerce. Public URL: /p/[tenantSlug]/[linkSlug].
Pipeline: Why use this

Understanding the Pipeline view gives you the deal status of your whole book at a glance, with drag-to-move stage changes.

Benefits:

See where every deal sits without filtering reports

Move deals between stages with one drag

Tailor the schema per tenant so it matches how you sell

Spot stuck deals by stage clustering, not spreadsheet math

The Pipeline is the Kanban-style board view of your deals, grouped by stage. Drag a card to move it to the next stage. The schema is per-tenant, configurable in your CRM settings. Open at /leads/pipeline.
Project (team): Why use this

Understanding Team projects gives you a cross-functional tracker that lives alongside your CRM data instead of a separate PM tool.

Benefits:

Coordinate cross-functional work without a side tool

Tie initiatives to the leads and deals they affect

Track owners, status, and due dates in one view

Separate this from Build Projects so each stays focused

A Team project is a cross-functional initiative your team coordinates around. Tracks tasks, owners, status, due dates. Distinct from /projects (Build group). Live at /team/projects.
Project (user): Why use this

Knowing what a Build Project is lets you organize skills, prompts, and data around one goal instead of letting them sprawl.

Benefits:

Group related skills, prompts, and sources in one folder

Keep Build work separate from cross-functional team projects

Reuse a Project as a starting point for the next one

Permission and share at the Project boundary

A Project in the Build group is a scoped folder of work (skills, prompts, data sources) you organize around a goal. Distinct from /team/projects (cross-functional initiatives). Live at /projects.
Prompt: Why use this

Understanding Prompts as first-class objects lets you write a system prompt once and reuse it across every agent that needs it.

Benefits:

Stop copy-pasting the same instructions into every agent

Update one prompt and every dependent agent improves

Version and audit prompt changes in one place

Share proven prompts across the team

A Prompt is a saved system prompt you can reuse across agents and templates. Library at /prompts.
Public ID: Why use this

Understanding Public IDs protects you from exposing internal UUIDs in public URLs, which would leak record counts and ordering.

Benefits:

Keep internal IDs out of customer-facing links

Prevent enumeration attacks on your public surfaces

Hide row counts and creation order from outsiders

Rotate public IDs without breaking internal references

A Public ID is an opaque, hard-to-guess identifier used in public URLs (funnel publicId, invoice publicToken, credential publicToken). Never expose internal UUIDs in user-facing URLs.

Q

QR code: Why use this

Understanding QR codes bridges offline campaigns to your tracked URLs, so every print, sign, and event scan counts.

Benefits:

Connect print, signage, and events to your attribution stack

Log every scan as a tracked click

Update the destination without reprinting the code

Tie offline traffic to leads and revenue

A QR code is a scannable image that resolves to a Looper-tracked URL. Every scan is logged. Useful for offline campaigns, print, events. Manage at /qr-codes. Public URL: /q/[tenantSlug]/[qrSlug].
Queue: Why use this

Knowing about the Queue gives you a single place to inspect, retry, and cancel every background job so nothing silently hangs.

Benefits:

See every async job in one timeline

Retry failed jobs without rebuilding the inputs

Cancel runaway work before it costs more credits

Diagnose why a Mission or export stalled

The Queue is the async job queue showing every background task (mission, sync, large export). Status, retry, cancel from /queue.
Quiz: Why use this

Understanding Quizzes as scored Surveys lets you segment leads by skill, persona, or intent, not just contact info.

Benefits:

Segment leads by tiered result, not raw form data

Drive personalized follow-up off the tier they earn

Increase engagement with a gamified flow

Reuse the Survey builder you already know

A Quiz is a scored survey that returns a tiered result (e.g. "You are a beginner / intermediate / pro"). Quizzes live inside the Survey surface but flip on scoring + result tiers. Build at /surveys with quiz mode enabled. Useful for lead segmentation and engagement.

R

Recipe: Why use this

Knowing what a Recipe is lets you save a working workflow with its context and replay it across tenants or in the marketplace.

Benefits:

Capture a working workflow with description and example I/O

Apply it to a new tenant in one click

Share or sell proven recipes through the marketplace

Onboard new tenants from a tested baseline

A Recipe is a saved workflow template you can apply across tenants or share with the marketplace. Recipes capture not just the workflow but a description, expected inputs, and example outputs. Manage at /recipes.
Reseller markup: Why use this

Understanding Reseller markup lets agencies bake their margin into client billing without manual math each invoice cycle.

Benefits:

Add your margin once instead of per invoice

Bill clients on metered usage with markup applied

Keep the underlying Looper rate hidden from clients

Adjust margin without touching individual statements

Reseller markup is the percentage an agency adds on top of Looper's underlying pricing when billing its own clients. Set at /agency/settings. Lets agencies bake their margin into the tenant's metered usage line item without doing manual math each invoice cycle.
resolveTenant: Why use this

Understanding resolveTenant explains how Looper pins every request to the right tenant and role, which is the safety rail behind every API.

Benefits:

Know which helper gates every API route in the system

Debug 401 and 403 responses with a clear mental model

Trust that role and tenant checks happen before any handler

Reuse one pattern across every new route you build

resolveTenant is the server helper every API route calls first to pin the request to the active tenant and the caller''s role. It returns ctx with tenantId, userId, role. If it fails the route returns 401 or 403.
Reviews AI: Why use this

Understanding Reviews AI lets you respond to every inbound review in your brand voice without burning hours on copy.

Benefits:

Reply to Google and Yelp reviews in minutes, not days

Match your brand voice without writing each one

Pick approve-first or full autopilot per channel

Protect rating velocity that drives local rankings

Reviews AI is the auto-responder that drafts replies to inbound reviews (Google, Yelp, others) in your brand voice. Approve or autopilot per channel. Manage at /reviews-inbox.
RLS: Why use this

Understanding RLS gives you the mental model for how Looper isolates tenant data, which matters every time you touch a multi-tenant table.

Benefits:

Trust that no tenant can read another tenant's rows

Verify isolation from one admin dashboard

Write queries knowing the policy enforces tenant scope

Pass security review with documented row-level controls

RLS stands for Row-Level Security. It is the Postgres feature Looper uses to ensure one tenant''s data is never visible to another tenant. Every multi-tenant table has RLS policies on it. Founders verify at /admin/system-health.
Role: Why use this

Understanding Roles lets you give each teammate the right slice of Looper without overexposing settings or data.

Benefits:

Grant only the access each role needs

Separate owner, admin, member, viewer, agency, affiliate, customer surfaces

Prevent accidental edits by limiting permission scope

Audit who can do what without spreadsheet tracking

A Role is your permission level inside a workspace: owner, admin, member, viewer, agency, affiliate, customer, or founder. Each role sees a different slice of Looper. Owners manage roles at /settings/team.
RSS auto-import: Why use this

Understanding RSS auto-import lets you repackage your blog and industry sources into social content without copy-paste.

Benefits:

Pull blog posts in automatically as they publish

Repackage curated industry feeds into your channels

Skip the manual copy-paste from feed reader to scheduler

Keep social fresh even on weeks you do not write new posts

RSS auto-import pulls posts from a configured RSS 2.0 or Atom 1.0 feed and queues them into your social-content workflow. Set up at /social-content. Useful for repackaging your own blog or curated industry sources.

S

Scheduled reports: Why use this

Understanding Scheduled reports lets you put weekly and monthly numbers on autopilot instead of pulling them by hand.

Benefits:

Email key metrics to stakeholders on a fixed cadence

Cover attribution, revenue, leads, calls, appointments in one config

Free up the hour you used to spend on report-building

Hold the team accountable to numbers they get pushed

Scheduled reports run on an hourly cron and email the PDF/CSV to your chosen recipients. Built-in templates: attribution, revenue, leads, calls, appointments, local audit. Manage at /reports.
Scoring rule: Why use this

Understanding Scoring rules lets you focus sales time on the leads most likely to close instead of working the list top-down.

Benefits:

Quantify which leads deserve outreach today

Combine positive and negative signals into one score

Bulk recompute when your rules change

Drive routing and sequences off score, not gut feel

A Scoring rule is a condition (e.g. "company size more than 50") that assigns positive or negative points to a lead. Total score lives on the lead record. Configure at /scoring-rules. Use bulk recompute to update existing leads when rules change.
Sending identity: Why use this

Understanding Sending identities is the prerequisite for any outbound email work, since unverified domains land in spam.

Benefits:

Send from your real domain with SPF and DKIM verified

Avoid spam folder placement on cold outreach

Confirm inbox deliverability before any sequence runs

Manage multiple senders without juggling email accounts

A Sending identity is a verified email address (or domain) that Looper is allowed to send mail from on your behalf. You verify via SPF, DKIM, and an inbox confirmation click. Set up at /sending-identities. Required before any /sequences run.
Sequence: Why use this

Understanding Sequences lets you nurture leads on a timed drip without manually firing one email at a time.

Benefits:

Drip multi-step email and SMS without manual sends

Branch the flow based on lead behavior

Trigger automatically on lead, tag, or manual enroll

Recover replies and replies-to-handoff to a human

A Sequence is a multi-step email or SMS drip campaign. Each step has a delay, content, and optional branch logic. Sequences run on triggers (lead added, tag applied, manual enroll). Build at /sequences.
Skill: Why use this

Understanding Skills lets you extend your agents with packaged capabilities from the marketplace instead of building each tool from scratch.

Benefits:

Add proven capabilities without writing new tools

Combine system prompt, tools, and KB in one install

Reuse the same Skill across multiple agents

Swap or upgrade Skills without rewriting agents

A Skill is a packaged capability (one or more tools + a system prompt + KB) your agents can call. Install from the marketplace at /installs.
Skip trace: Why use this

Understanding Skip trace lets you complete partial lead records so you can actually reach out instead of holding a name with no phone.

Benefits:

Recover phone, email, and address you do not have yet

Run as a one-click action from any lead record

Use credits or BYOK depending on what fits your billing

Convert dead-end records into contactable leads

Skip trace is the process of looking up missing contact data (phone, email, address) for a lead you already have a name and a sliver of info on. Looper offers it as a one-click action on /leads/[id]. Skip traces consume credits or BYOK calls depending on your billing mode.
Snapshot: Why use this

Understanding Snapshots lets agencies clone a working tenant setup onto a new client in seconds instead of rebuilding from scratch.

Benefits:

Replay workflows, sequences, templates, and brand kit at once

Onboard a new sub-tenant in minutes, not hours

Standardize what a fresh tenant looks like across the agency

Roll back a tenant to a known-good state if needed

A Snapshot is a saved copy of a tenant''s configuration (workflows, automations, sequences, templates, brand kit, settings). Agencies and owners use snapshots to clone a working setup onto a new sub-tenant in seconds. Manage at /settings/snapshots.
Snippet: Why use this

Understanding Snippets lets you reuse signatures, disclaimers, and stock replies anywhere with a slash command instead of retyping.

Benefits:

Drop reusable text into email, site, social, chat in one keystroke

Keep brand-approved language consistent across surfaces

Update one snippet to update every place it lives

Speed up support and sales replies dramatically

A Snippet is a reusable text block (signature, disclaimer, common reply, social bio) you can drop into emails, sites, social posts, and chat with a slash command. Manage at /snippets.
Spend cap: Why use this

Understanding Spend caps protects you from runaway AI bills by stopping new runs once you hit a monthly limit.

Benefits:

Cap monthly AI spend at a number you set

Pause runs automatically instead of getting a surprise invoice

Raise the cap when you genuinely need more

Sleep better knowing the limit enforces itself

A Spend cap is a monthly limit on AI usage (credits or BYOK dollars). Once hit, Looper pauses new runs until next month or until you raise the cap. Set at /settings/limits.
Spend transparency: Why use this

Understanding Spend transparency tells you exactly which features and models drove your AI bill, so you can cut the expensive ones.

Benefits:

See per-feature and per-model spend breakdowns

Find the cost driver behind a bill spike

Decide which features to keep on premium models

Negotiate caps and plans with real usage data

Spend transparency is the per-feature, per-model breakdown of where your AI usage went this month. View at /transparency. Use it to find unexpected cost drivers.
Stripe Connect: Why use this

Understanding Stripe Connect is the unlock for taking payments through Looper without standing up a separate payment processor.

Benefits:

Accept payments under your own Stripe account

Route funds straight to your balance, not Looper's

Power payment links, invoices, commerce, affiliate payouts

Stay in compliance with Stripe-managed KYC and KYB

Stripe Connect is the account linkage that lets Looper accept payments on your behalf and route funds directly to your Stripe balance. Required for /commerce, payment links, invoices, and affiliate payouts. Connect from the /commerce banner.
Sub-agent: Why use this

Understanding Sub-agents shows you how a Mission can run specialized workers in parallel, which is faster than one big context window.

Benefits:

Parallelize research, writing, and review steps

Give each sub-agent its own focused context window

Specialize prompts and tools per step

Scale a Mission without bloating a single agent

A sub-agent is a specialized AI agent that a parent Mission delegates work to. Sub-agents have their own prompts, tools, and context windows, so a research Mission can run a "find sources" sub-agent in parallel with a "write summary" sub-agent. Configure them at /missions/subagents.
Survey: Why use this

Understanding Surveys gives you a way to collect responses, segment leads, and trigger automations without bolting on a third-party form tool.

Benefits:

Collect responses on a hosted form you control

Drive segmentation and tags from answers

Trigger workflows the moment a response comes in

Publish at a clean public URL with your tenant slug

A Survey is a hosted form you publish to collect responses. Survey responses can drive automations, segment leads, or simply gather feedback. Manage at /surveys. Public URL pattern: /s/[tenantSlug]/[surveySlug].

T

Task: Why use this

Understanding Tasks lets you assign work to a teammate with the lead or deal context attached, so nothing gets lost between systems.

Benefits:

Assign work directly from a lead or deal record

See all team tasks in one global view

Filter to only your own tasks when heads-down

Keep accountability inside the same tool as the data

A Task is a unit of work assigned to a teammate, optionally linked to a lead or deal. Global view at /tasks. My-only view at /tasks?scope=mine.
Template library: Why use this

Understanding the Template library lets agencies reuse sequence, workflow, recipe, mission, and brand-kit templates across every owned tenant.

Benefits:

Share templates once, see them in every owned tenant

Stop rebuilding the same sequence per client

Standardize delivery across the agency book

Update a template once and every tenant gets the change

The Template library is the shared store of templates (sequence, workflow, recipe, mission, brand kit). Agencies see the library across every owned tenant. Live at /templates.
Tenant: Why use this

Understanding Tenants is the foundation for everything else in Looper, since every row, user, and setting is scoped to a tenant.

Benefits:

Reason about what is scoped where across the product

Separate businesses cleanly, even under one agency

Map users and roles to the right workspace

Operate multi-tenant from day one, not after a rewrite

A Tenant is a single workspace inside Looper. One business, one set of users, one set of data. Agencies operate across multiple tenants. Founders manage tenants at /admin/tenants.
Tenant switcher: Why use this

Understanding the Tenant switcher lets agencies and multi-tenant users hop between workspaces without logging out.

Benefits:

Switch active workspace in two clicks

Avoid logging out and back in to change tenants

Keep one identity across every owned workspace

Stay productive when juggling many client tenants

The Tenant switcher is the dropdown in the top nav that swaps your active workspace when you belong to more than one. Agencies use it constantly.
Trigger Link: Why use this

Understanding Trigger Links lets you turn any URL into a tracked click that can attribute to a lead and fire workflows on tap.

Benefits:

Track every click on links you share in email, SMS, bios

Attribute clicks back to a specific lead when possible

Fire workflows the second someone taps

Publish at a clean tenant-branded short URL

A Trigger Link is a Looper-hosted short URL that records every click, attributes it to a lead when possible, and can fire workflows on click. Use these in emails, SMS, or social bios when you want to know who clicked. Manage at /trigger-links. Public URL pattern: /t/[tenantSlug]/[linkSlug].

V

Voice agent: Why use this

Understanding Voice agents lets you cover inbound calls 24/7 without staffing a phone line.

Benefits:

Answer every inbound call without a human in the loop

Qualify callers and book appointments automatically

Capture intent on calls that would otherwise go to voicemail

Run on a Twilio number you already trust

A Voice agent is an AI agent that answers calls on a Twilio number, qualifies callers, and books appointments. Configure at /voice. Requires a connected Twilio number.

W

Workflow: Why use this

Understanding Workflows is how you automate work that mixes deterministic logic with AI steps, on any trigger you care about.

Benefits:

Automate the busywork between leads, deals, and outreach

Mix deterministic steps with AI judgment where it helps

Trigger on events, schedules, or manual run

Build visually or by describing what you want in chat

A Workflow is a step sequence (visual or chat-built) that runs when a trigger fires (lead created, form submitted, time elapsed, manually run). Workflows can mix deterministic logic with AI steps. Build at /workflows or describe in chat at /workflows/build.

A

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

B

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

C

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

D

Why use this

Why use this

E

Why use this

Why use this

Why use this

F

Why use this

Why use this

Why use this

G

Why use this

H

Why use this

Why use this

I

Why use this

Why use this

Why use this

Why use this

K

Why use this

L

Why use this

Why use this

M

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

Why use this

N

Why use this

O

Why use this

Why use this

P

Why use this