Main Content and Operations

Main Content and Operations

This section covers operational modules that keep the platform useful and up to date: support tickets, notifications, blogs, FAQs, files, static pages, documentation, marketplace content, and communication workflows.

Recommended Routine

• Review open support tickets daily.
• Update FAQs when repeated questions appear.
• Publish blogs or announcements for releases.
• Review files and storage usage.
• Keep documentation aligned with current modules.
• Send notifications carefully and only to the intended audience.

Main Content and Operations - Main Features Overview

Manage support, notifications, blogs, FAQs, files, marketplace content, and operational communication. This page explains how customers should use the Main Content and Operations module in day-to-day LocalBoost AI operations, from setup to review and troubleshooting.

Main Features

• Central workspace for managing Main Content and Operations 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 Main Content and Operations 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.