Clear answers for OpsIQ users.

OpsIQ is an AI-powered operations platform for websites and online businesses. It combines visitor tracking, customer chat, admin chat, tickets, AI writing, analytics, webhooks, billing tools, notifications and account management.

Business owners, admins, support agents, sales teams, developers and customers use different parts of OpsIQ. Admins manage the platform in /manage, while customers manage their profile, preferences, tickets and billing in /account.

Yes. OpsIQ can support a managed cloud-style setup and self-hosted deployments. In both cases, the goal is the same: connect websites, track activity, support customers and automate safe actions.

Start with branding, currency, admin security, departments, tracking, customer account pages, notifications, then AI chat and webhooks. This makes testing easier and avoids enabling too much at once.

Tracking shows how visitors move through your website before they chat, open tickets, sign up or buy. It helps you understand traffic sources, page performance, location, lead intent and support demand.

OpsIQ can track visits, sessions, pages, referrers, devices, browser details, countries, cities when available, remote sites, events, leads, chat activity and conversion indicators.

Location depends on available signals such as headers, Cloudflare country data or MaxMind GeoIP. VPNs, mobile networks and proxies can reduce accuracy.

Common causes include duplicate tracking scripts, staff traffic, bots, test pages, remote-site duplication, cache behavior or missing excluded IP/path rules.

Check that the tracking script is installed, the site key is correct, the browser is not blocking the script, excluded paths are not too broad and the remote site is marked active.

It helps customers answer common questions, troubleshoot issues, provide details, request a human, upload attachments and open or continue tickets when needed.

No. The AI should first try to understand and help with the issue. A ticket should be created when the customer provides enough detail, needs staff help or the issue is not resolved.

For logged-in customers, the chat can use safe account context only when enabled by the admin. Access should be limited to what is useful and appropriate.

Yes, if attachments are enabled. Admins should set safe file types and maximum upload size.

Yes. You can configure colors, dark/light mode, glass effects, launcher shape, avatars, bubble styles, welcome messages and position.

Admin Chat is the staff workspace for customer conversations, internal coordination, assignments, handoff, private notes and live support.

They are private staff messages used for coordination. Customers should never see them.

OpsIQ Writing helps draft replies, summarize issues, prepare announcements, write follow-ups and create clearer customer communication.

Yes, but automatic replies should only be enabled where the knowledge is reliable and the topic is safe. Billing, legal, abuse and security cases should usually be reviewed by staff.

Tickets support departments, priorities, statuses, rich text, plain text, emoji, attachments, internal notes, staff replies, customer replies and notifications.

Admins create and manage departments in /manage Tickets. Departments help route support requests to the right team.

Customers can open tickets from /account Support, from the chat escalation flow, or any connected support entry point enabled by the admin.

The bell shows unread notifications. Customers and admins can click it to preview updates and open the full notification details.

Yes. Admins can create customer notices with title, message, style, optional link, start date and end date. Notices can appear in the customer account header during the selected period.

Actions are approved operations that OpsIQ can request from a connected platform, such as reading a customer, creating a task, updating a ticket or checking a subscription.

Triggers are events or conditions that start a workflow, such as a new signup, ticket reply, visitor returning, failed payment or webhook event.

Webhooks connect OpsIQ with other websites and apps. They send signed events or receive signed requests so systems can communicate securely.

No. The safest approach is to expose approved API actions with scoped permissions, signatures, validation and confirmation for sensitive changes.

Yes. Remote sites allow multiple websites to send tracking, chat and event data into one OpsIQ dashboard.

OpsIQ can detect a visitor or signup country using available location signals and assign the best matching currency. Admins can set fallback currency and country mappings.

Yes, customers can change currency in /account Preferences if the admin allows it.

Customers should keep company/legal name, phone, billing address, city, state, postcode, country, tax ID and timezone updated. This improves invoices and support accuracy.

Invoices should include seller details, customer billing details, tax ID where applicable, item rows, subtotal, tax, discount, total, amount due, payment status and notes.

Yes, admin login can use Google Authenticator where enabled. Make sure device time is correct when validating codes.

Use scoped keys, rotate them when needed, do not expose them publicly, and only allow the actions a connected site actually needs.

Yes. Admins can upload global, footer, account and admin logos, including dark and light variants, plus a favicon.

Yes. Admins can edit the copyright text from /manage Appearance.

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

Check folder permissions, upload size settings, PHP upload limits, allowed file extensions and available storage.

Check that notifications are being created for the correct customer or admin, unread status is set, JavaScript loads correctly and the dropdown route is reachable.

Check GeoIP path, country headers, country-to-currency rules, fallback currency and whether the signup form selected a different currency manually.