Learn OpsIQ without guessing.

Understand who is visiting, where they come from, what pages they view, when they return, and which visits become leads or customers.

Use Client AI Chat for customers and Admin Chat for staff. Keep routine support fast while allowing human handoff when needed.

Manage customer tickets with departments, rich text, attachments, internal notes, priorities, statuses, and notification alerts.

Connect OpsIQ to websites, apps and internal systems so approved actions can be run safely from the admin side.

Use the hosted dashboard for customer accounts, subscriptions, licensing, billing, support, analytics, notifications and website integrations.

Install OpsIQ on your own server when you want direct control over storage, branding, updates, integrations and environment settings.

Connect multiple websites to one OpsIQ dashboard so each site can report visits, chats, leads, feedback and events.

Use one /manage area to control branding, currencies, customers, tickets, notices, webhooks, triggers, and AI behavior.

See traffic, leads, tickets, notifications, AI activity, conversion indicators and operational health in one view.

Watch current visitors, open chats, active journeys, high-intent sessions and support opportunities as they happen.

During promotions, use Live and Analytics together to see which pages or countries are responding.

When a customer asks for help, review the journey and recent actions so the support team understands the customer faster.

Review active conversations, customer messages, guest chats, assigned chats, waiting customers, and chat history.

A staff member can join a chat to help directly. Leaving the chat should return control cleanly without making the customer feel rejected.

Use private staff notes or whispers for internal coordination. Customers should never see internal messages.

Where enabled, staff can offer call, video or screen assistance. Use this only when your team is trained and customers consent.

Install the admin chat app where supported so staff can access conversations from desktop or mobile more conveniently.

Use archive tools to keep the inbox clean while retaining the ability to find past conversations when needed.

Create departments in /manage such as Billing, Technical, Sales, Abuse, Onboarding or General. Route tickets to the right team.

Customers and staff can write formatted replies or switch to plain text when simple messages are better.

Allow screenshots, PDFs and other approved files so customers can provide evidence and support context.

Staff can add private notes for team members without exposing them to the customer.

Use status and priority to control what needs action: Open, Pending, Waiting, Resolved, Closed, Low, Medium, High or Urgent.

Customers and admins receive notifications when tickets are opened, replied to, assigned, updated or resolved.

An action is an approved operation OpsIQ can request, such as creating a customer, reading an order, updating a ticket, checking a subscription or sending a notice.

A trigger tells OpsIQ when something should happen, such as new signup, failed payment, ticket reply, lead created, visitor returns or webhook received.

Webhooks send events between OpsIQ and other platforms. Use signatures and scoped keys so only trusted systems can call your endpoints.

Sensitive actions should require confirmation before running, especially billing, suspension, deletion, customer changes or account-level updates.

During signup, OpsIQ can detect country/city using headers or MaxMind GeoIP and assign the best matching currency.

Customers can change their currency in /account Preferences if your settings allow it.

Admins can manage supported currencies, country mappings, fallback currency and GeoIP database path in /manage.

Invoices should show company details, customer billing profile, tax ID, item rows, subtotal, tax, discount, total, amount due and payment status.

Review customers, profiles, currencies, subscriptions, invoices, tickets and account status.

Create departments, manage customer requests, reply with rich text, add notes, update priority and resolve issues.

Create notices and alerts for customers or admins. Use start/end dates for timed announcements.

Upload logos, dark/light variants, favicon, footer logo and copyright text.

Manage supported currencies, GeoIP path, fallback currency and country rules.

Create API keys, webhooks, triggers and external platform connections.

Use strong passwords and Google Authenticator for the /manage login where enabled.

Give customers clear account security tools such as password updates, sessions and two-factor options where configured.

API keys should be limited to the actions they need. Do not reuse full-access keys for public websites.

Require confirmation for sensitive writes, billing changes, destructive actions and account changes.

Restrict attachment types and size. Do not allow executable files or unknown scripts.

Keep records of important actions, webhook calls, admin changes and automation results.

Check the script is installed, not blocked by CSP/ad blockers, not cached incorrectly, and uses the correct site key.

Check country detection, GeoIP file path, country-to-currency rules, fallback currency and customer preference.

Check AI provider settings, knowledge sources, API key, rate limits, model availability and chat behavior toggles.

Check upload folder permissions, file size limit, extension allowlist and server upload limits.

Check unread status, notification table creation, browser permission, admin/customer recipient scope and bell dropdown script.

Confirm device time is correct, recovery options are available, and the account has the correct secret enabled.