Clear answers for OpsIQ users.

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

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.

Most teams reach a first measurable result within about two weeks: a share of conversations handled by AI, faster first-reply times and a few tools switched off. There is no implementation-services contract; sign up, connect your platforms and start operating.

Yes. You can start free and explore the core operating layer (chat, tickets, tracking and connectors) before committing to a paid plan.

Yes. The marketing site auto-detects your country and shows pricing in the region's enabled currency, and you can override the currency manually. Operators control which currencies are enabled.

Nine payment gateways ship today: Stripe, PayPal, Paystack, Flutterwave, Razorpay, Mollie, Pesapal (M-Pesa), and crypto via NOWPayments and Plisio. Each runs in test or live mode, and which methods appear at checkout depends on your operator's configuration.

AI is pay-as-you-go and is never bundled into the plan price: no plan includes a free token allotment. With Managed AI you pay only for the tokens the AI processes, from a prepaid wallet or one-time token packs, at a per-plan rate that gets cheaper on higher tiers. Or use BYOK and pay your own provider directly. Token packs are available on every plan, including free Starter.

Yes. Connect your own OpenAI, Anthropic, Google Gemini or xAI Grok key and OpsIQ sends requests straight to that provider, billed by them with no markup from us. Or use Managed mode, where OpsIQ meters usage from your wallet. You can switch modes and choose models per feature.

You keep access until the end of the paid period. Your data can be exported at any time from the export tools, and retention settings control how long logs are kept after that.

Yes. Releases ship to Cloud and Self-hosted alike: the same release for everyone, not an enterprise-only fork.

Yes. Remote Sites let multiple websites send tracking, chat and event data into one dashboard, and agencies can manage many client workspaces from a single hub with per-client permissions.

Each workspace is isolated by tenant. If you have a specific data-residency requirement, talk to us about options, and self-hosting lets you keep the entire data path on your own infrastructure.

Yes. Because the platform and data model are the same on both, you can export your data and migrate. Talk to support to plan a migration.

No. OpsIQ never trains AI models on your data and does not sell it. Only the context needed to answer a request is sent to the model provider you configure; with BYOK that request goes straight to your own provider, whose data-use terms then apply.

Yes. AI History logs every AI turn: the rendered prompt, the response, the model, tokens and result, owner-only and exportable as CSV. The full conversation is also kept in the chat thread, so there is no black box to explain to a compliance team.

Only through action contracts. The AI cannot invent operations; every write goes through an approved, scoped contract with validation and, for sensitive changes, a confirmation card.

The built-in cookie-consent platform enforces choices per category: when analytics consent is off, capture genuinely stops rather than just hiding a banner.

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.

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.

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.

Admins create and manage departments in the admin Tickets area. 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.

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.

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.

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 the admin Appearance settings.

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.