Extended License

Extended License - Main Features Overview

The Extended License explains when LocalBoost AI or a marketplace addon can be used in a commercial product where end users pay to access the final service. This is important for SaaS operators, agencies, client portals, and subscription products.

Regular License vs Extended License

Regular License

A Regular License is usually suitable for internal usage, one client project, or a non-resold end product depending on the purchase platform terms.

Extended License

An Extended License is usually required when the product becomes part of a paid SaaS, paid client portal, subscription platform, resale product, or commercial service where end users pay for access to the final result.

Common LocalBoost AI Scenarios

• Agency runs LocalBoost AI internally for client campaigns.
• Business owner uses LocalBoost AI for their own locations.
• SaaS owner sells access to businesses or agencies.
• Developer installs addons from Marketplace and sells access to those addon features.

Important Note

License rules can vary by marketplace and product. Always review the official license file and purchase terms included with your package. This documentation is a practical usage guide, not legal advice.

Extended License - Main Features Overview

Understand Regular and Extended License usage for LocalBoost AI and marketplace addons. This page explains how customers should use the Extended License module in day-to-day LocalBoost AI operations, from setup to review and troubleshooting.

Main Features

• Central workspace for managing Extended License records.
• Business-aware organization so records can be reviewed by local business or workspace.
• Status, ownership, and permission checks to keep customer data controlled.
• Connections with campaigns, CRM, reports, files, and automations where supported.
• Designed for repeat daily use by agencies and local business teams.

Recommended Workflow

1. Open Extended License from the portal sidebar.
2. Choose the correct workspace and business before creating or editing records.
3. Review existing records, statuses, and recent activity.
4. Create or update the required item with complete information.
5. Preview, test, or validate the customer-facing result when applicable.
6. Use reports, logs, or CRM follow-up to confirm the result after launch.

Views, Filters, and Review Options

• Filter by business or workspace when multiple brands are managed.
• Filter by status to separate draft, active, paused, completed, failed, or archived items.
• Use date ranges when reviewing campaign, CRM, report, or log activity.
• Search by name, customer, campaign, email, phone, tag, or template where available.

Available Actions

• Create new records when the plan and permissions allow it.
• Edit existing records without changing unrelated business data.
• Search and filter records to find the correct campaign, customer, page, or automation.
• Open detail or analytics pages for deeper inspection.
• Archive, pause, deactivate, or delete records only after checking downstream usage.

Benefits

• Reduces manual work by keeping related actions in one module.
• Improves consistency across campaigns and customer follow-up.
• Makes reporting easier because activity stays tied to business and campaign context.
• Helps teams move from campaign creation to measurement and follow-up faster.

Before Publishing or Activating

• Confirm the business profile is complete.
• Confirm the user has permission in the active workspace.
• Confirm the current plan includes this feature or addon.
• Test public pages, QR codes, forms, messages, or webhooks before using them with real customers.
• Check mobile layout because most QR and local campaign visitors use phones.

Troubleshooting

• If the module is not visible, check addon status, plan permissions, and user role.
• If records are missing, check the selected business and workspace.
• If a public action fails, test it in a private browser session and inspect validation errors.
• If analytics look wrong, confirm visitors used the tracked LocalBoost URL or QR code.
• If automation or AI does not run, check credits, provider settings, logs, and feature access.

Operational Notes

Use consistent naming for businesses, campaigns, templates, QR codes, automations, and CRM segments. Consistent naming makes reports easier to read and helps support teams diagnose issues quickly. When a feature depends on an addon, confirm the addon is installed, active, available in the current plan, and visible to the current workspace.