Brand

Configure public FormLead branding and powered-by behavior.

In LeadFlow AI, this area is part of the buyer's operational workflow: build a lead capture asset, publish it safely, collect qualified lead records, route those records to the correct owner, and review performance before changing traffic or sales processes. Treat every setting here as production-facing when the item is connected to a live form, funnel, survey, QR link, embedded page, automation, custom domain, file, or paid SaaS plan.

Main Features Overview

Create multi-step, single-page, embedded, popup, and campaign-specific forms.
Use AI-assisted copy, questions, labels, and qualification prompts.
Capture hidden fields such as UTM source, campaign, page URL, referrer, and workspace context.
Publish forms with spam protection, consent fields, thank-you behavior, and notification routing.

When to Use This Feature

Use Brand when the team needs a controlled way to manage this part of lead generation instead of handling it through spreadsheets, disconnected forms, or manual email threads. It is especially useful when agencies manage multiple customer workspaces, when SaaS customers need repeatable form and funnel setup, or when administrators must control which features are available by plan.

Do not use this area as a catch-all record store. Keep records tied to the correct workspace, client, form, funnel, campaign, or lead source so analytics, permissions, exports, and automation rules stay accurate.

Practical Examples

A real estate agency creates a seller valuation form with budget, location, timeline, and contact fields.
A SaaS buyer creates a demo request form that scores leads based on company size and urgency.
A marketing team embeds a newsletter form on WordPress and routes submissions into LeadFlow AI.
An agency creates one reusable intake template, then duplicates it for each client workspace.

Recommended Workflow

Start from the correct workspace and confirm the client, campaign, or product offer context.
Create or update the record with complete names, source details, status, owner, and visibility settings.
Connect related records such as form, funnel, survey, response, lead, automation, integration, file, QR code, or report.
Run a realistic test before publishing: submit the form, inspect the lead, check notifications, and review analytics.
Monitor the first production traffic or submissions and adjust only after identifying a clear issue.

Important Fields and Records

Field label, field key, validation rule, placeholder, help text, required flag, and default value.
Consent text, privacy link, captcha setting, redirect URL, thank-you message, and notification recipients.
Hidden tracking fields for UTM source, medium, campaign, content, term, referrer, and landing URL.
Workspace or tenant owner, because records must remain separated between buyers, teams, and clients.
Status and visibility, because draft, published, archived, internal, and active records behave differently.
Created and updated timestamps, because troubleshooting often depends on knowing when a campaign changed.
Owner or assignee, because lead response speed and accountability matter in a lead generation product.

Permissions and Plan Access

Access should be controlled by workspace role, team permissions, owner permissions, and SaaS plan features. A form builder role may create drafts but not publish. A lead operator may view responses and update lifecycle stage but should not change custom domains, billing, or tracking scripts. Admins should test visibility with a non-admin account after changing plans, marketplace addons, or sidebar permissions.

Confirm the user's workspace owns the form, funnel, lead, client, or report being opened.
Confirm the active plan allows publishing, AI generation, automation, reports, files, custom domains, QR tools, templates, surveys, or integrations where relevant.
Hide buttons and routes for addon features when the addon package is not installed.
Review team roles before allowing delete, export, billing, integration, or domain changes.

Best Practices

Name records with form, funnel, source, offer, and date context. Validate forms before driving paid traffic. Use hidden fields and UTM capture consistently. Keep lifecycle stages simple enough for operators to update. Review analytics weekly and make one controlled change at a time so conversion changes can be understood. For agency work, keep each customer's workspace, team members, files, domains, and reports separated.

For production SaaS use, configure plan limits before launch, test payment and email delivery, and keep a backup before importing, deleting, or bulk updating lead data. For agency use, create a standard onboarding checklist for each client: workspace, brand settings, lead fields, consent copy, funnel pages, integrations, notification recipients, test submissions, and reporting cadence.

Troubleshooting

The page or button is not visible
Check the user role, workspace ownership, active SaaS plan, addon installation status, and sidebar/menu permissions. Clear cache after changing permissions or package status.

Saved changes do not affect the public form or funnel
Confirm the draft was published, the correct domain or embed code is being used, and browser cache or CDN cache is not serving an older version.

Lead data looks incomplete
Review required fields, custom field keys, hidden tracking fields, consent settings, spam protection, and integration mappings. Submit a test lead from a private browser session.

Notifications or webhooks are not delivered
Check mail settings, queue workers, cron configuration, webhook endpoint availability, provider credentials, and recent failed job logs.

A user sees the wrong information
Review workspace ownership, team membership, route permission middleware, plan features, and whether the account is operating inside the correct active team.

FAQ

Can this feature be sold inside SaaS plans?
Yes, when your license and business model allow it. Use plan permissions and limits to decide which plans can access forms, responses, funnels, surveys, AI tools, QR tools, reports, files, custom domains, integrations, support, and automation.

Should agencies create one workspace per customer?
That is the cleanest operating model for most agencies because it separates branding, leads, forms, funnels, reports, files, domains, team members, and integrations.

Can admins edit customer records?
Admins can usually inspect and support customer records, but production teams should keep an audit trail and avoid changing customer data unless support or operations requires it.

What should be tested before launch?
Test installation, login, plan access, form publishing, funnel redirects, survey links, QR links, lead capture, email automation, webhooks, reports, files, custom domains, payments, and cache clearing.