Upgrade Version

How to Upgrade LocalBoost AI and Packages

Upgrading keeps LocalBoost AI current with new modules, bug fixes, addon updates, security improvements, and compatibility changes. Always test upgrades on staging before production.

Before Upgrading

• Back up the database.
• Back up uploaded files and storage.
• Back up the current application files.
• Review changelog and marketplace package notes.
• Check whether the update includes migrations.
• Put production into maintenance mode if required.

Upgrade Workflow

1. Upload or install the new package.
2. Run dependency updates if required by the release.
3. Run database migrations.
4. Clear config, route, view, and application cache.
5. Rebuild assets if the update changes frontend files.
6. Test login, businesses, campaigns, QR pages, CRM, reports, Google Business, automations, billing, and settings.

Post-Upgrade Checks

• Businesses and locations still open.
• Public landing pages still resolve.
• QR codes still redirect and record scans.
• Form submissions still create leads, bookings, feedback, or coupon claims.
• CRM customers and tasks are still visible.
• Automations and logs still run correctly.
• Google Business connection remains valid.

Upgrade Version - Main Features Overview

Upgrade LocalBoost AI and marketplace packages safely. This page explains how customers should use the Upgrade Version module in day-to-day LocalBoost AI operations, from setup to review and troubleshooting.

Main Features

• Central workspace for managing Upgrade Version 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 Upgrade Version 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.