Build, operate, and extend OpsIQ.

Every page load, click, scroll, and navigation event is captured in real time. See who is on your site right now, what pages they are viewing, how long they spend, and where they came from — all without third-party cookies.

Full history of every visitor with device, browser, operating system, country, city, referrer, UTM parameters, landing page, and identity resolution. Sessions group page views into journeys so you can see the entire path a visitor takes.

Timeline-style playback of captured visitor sessions. See exactly what users did — mouse movements, clicks, scrolls, page transitions, and form interactions. Use it to diagnose UX issues, understand drop-off points, and verify conversion flows.

A real-time stream of visitor activity as it happens. See page views, chat starts, form submissions, and intent signals updating every few seconds. Filter by country, device, or referrer to focus on specific traffic segments.

Pages ranked by visits, engagement time, bounce rate, conversions, and support activity. Identify your highest-performing content and pages that need improvement.

Country, city, and region breakdowns with maps. Device and browser distribution, traffic source analysis, search engine referrer tracking, and market penetration insights.

Track visitor intent signals — pricing page visits, repeated returns, documentation browsing patterns, and support interactions — to identify visitors who are likely to buy, churn, or need help.

Run split tests on your website directly from OpsIQ. Create variants, set traffic allocation, define conversion goals, and measure statistical significance. No external testing tool needed.

Capture client-side JavaScript errors from your website automatically. See error messages, stack traces, affected browsers, frequency counts, and which pages trigger them. Debug frontend issues without separate error monitoring.

Every tracked event — page views, custom events, chat interactions, form submissions, purchases — in a searchable, filterable log with full metadata.

Track orders, revenue, refunds, subscription renewals, and attribute conversions to traffic sources, campaigns, and visitor journeys. Revenue dashboards with period comparison and trend analysis.

High-intent visitors identified by behavior patterns. Score leads based on page visits, time on site, return frequency, support interactions, and custom signals. Feed leads directly into the CRM pipeline.

Automated crawling of your entire website to discover pages, detect broken links, find missing meta tags, check image alt text, validate canonical URLs, and map your site structure. Schedule crawls to run daily, weekly, or on demand.

Comprehensive technical analysis: page speed scores, mobile responsiveness, Core Web Vitals, SSL certificate status, redirect chains, duplicate content detection, crawl depth analysis, and structured data validation.

Evaluate every page for content quality, word count, readability score, keyword density, heading structure, internal/external link ratio, and freshness. Identify thin content, duplicate pages, and content gaps.

Semantic search across your entire site content. Ask natural language questions about your content and get AI-synthesized answers with source page references.

Monitor your search engine rankings for target keywords across Google and other engines. Track position changes over time, compare against competitors, and see which pages rank for which terms.

Discover keyword opportunities based on your content, competitor analysis, and search volume data. Get suggestions for new content topics, long-tail variations, and content optimization targets.

Monitor your inbound link profile. See which sites link to you, track new and lost links, analyze anchor text distribution, and identify link-building opportunities.

For businesses with physical locations: visualize your local search visibility across a geographic grid. See how your rankings vary by location, distance from your business, and search intent.

Connect your Google Business Profile to OpsIQ. Sync reviews, posts, Q&A, photos, and business information. Manage your GBP listing from inside OpsIQ. Respond to reviews, publish posts, and monitor insights.

Automated SEO and analytics reports generated on your schedule (daily, weekly, monthly). Reports include ranking changes, traffic trends, technical issues found, and content performance. White-label output available for agencies.

AI answers customer questions on your website 24/7 using your knowledge base, connected platform data (orders, accounts, subscriptions), and custom training prompts. Supports multiple AI providers: Claude (Anthropic), GPT-4o (OpenAI), Gemini (Google), and Grok (xAI).

An AI copilot inside your admin panel that helps you write ticket replies, draft customer communications, analyze support trends, look up customer data across connected platforms, and execute actions through the connector system.

The AI is grounded in your knowledge base articles, FAQ entries, product documentation, and connected platform data. It does not hallucinate — it answers from your actual business information or escalates when uncertain.

When the AI cannot resolve a question, detects frustration, or the customer asks for a human, it automatically hands off to your team with full conversation context. Configurable decline/timeout auto-revert back to AI.

Write separate instruction prompts for customer-facing AI and admin-facing AI. Control tone, boundaries, escalation rules, prohibited topics, and business-specific behavior. Per-workspace configuration supported.

Every AI conversation is logged with full request/response details, token usage, cost tracking, provider used, and model version. Review conversations to identify training gaps and improve AI accuracy.

Automated analysis of AI conversation patterns. See common questions, resolution rates, handoff frequency, customer satisfaction by topic, and areas where the AI needs better training.

Each connected site/workspace can use its own AI provider, model, temperature, token budget, and training prompts. A SaaS company can use Claude for the main product and GPT-4o for a secondary brand.

Two AI modes: Managed AI (included in your plan, no API key needed) or Bring Your Own Key (use your own OpenAI/Anthropic/Google/xAI API key for full control over model selection and costs). Both are first-class — every feature works with either mode.

Set monthly token budgets, per-conversation limits, and low-balance alerts. Track spending per provider, per workspace, and per conversation. Prevent runaway costs with hard ceilings.

Full helpdesk with departments, priorities (low/medium/high/urgent), statuses, SLA tracking, internal notes, customer replies, file attachments, and threaded conversations. No external helpdesk needed.

AI automatically triages incoming tickets by department and priority. Enable auto-reply for safe departments — the AI drafts and sends a response after a configurable delay (default: 2 minutes) so humans can intervene first.

Connect a mailbox (Gmail, IMAP, or provider-specific) to automatically create tickets from inbound emails. Replies to ticket notification emails update the ticket thread.

Embed a customer-facing ticket portal on your website. Customers can submit tickets, view their history, reply to open tickets, and check status — all branded to your design.

Merge duplicate tickets into a single thread. Merged tickets show [Merged] on the subject line. All conversation history is preserved in the surviving ticket.

After a human agent takes over a ticket, use "Return to AI" to let the AI resume auto-reply on that ticket. Useful when the human-required portion is resolved but the customer has follow-up questions the AI can handle.

AI-assisted ticket management from the inbox view. The copilot suggests replies, summarizes conversation history, recommends priority/department assignments, and can execute actions on connected platforms.

Real-time customer chat managed from a unified inbox. See all active conversations, customer identity, conversation history, and AI suggestions. Multiple agents can collaborate on a conversation.

Trigger chat messages based on visitor behavior: time on page, specific URL visited, scroll depth, return visit count, exit intent, or custom events. Example: show a help message after 60 seconds on the pricing page.

A customizable chat widget embedded on your website. Supports AI chat, live agent chat, ticket submission, knowledge base search, and visitor identity. Responsive, accessible, and brandable.

Collect customer satisfaction ratings after chat and ticket interactions. Design surveys with your own questions, rating scales, and follow-up prompts. Results feed into team performance and AI insights.

Separate AI writing assistant for composing email drafts, ticket replies, announcements, and customer communications. Uses its own prompt (not the chat brain) for professional business writing.

A single screen showing your entire CRM state: pipeline value, deal velocity, upcoming tasks, at-risk deals, agent activity, and AI recommendations. The CRM home page is your daily starting point.

Manage customer contacts with full profiles: name, email, phone, company, tags, lifecycle stage, conversation history, ticket history, purchase history, and custom fields. Link contacts to companies for B2B relationship management.

Visual Kanban-style deal board with customizable stages. Drag deals between stages, set values, assign owners, track close dates, and see pipeline value at each stage. Multiple pipelines supported.

The AI analyzes each deal and provides coaching: risk signals (gone quiet, competitor mentioned, budget concerns), next-best-action recommendations, win probability, and suggested follow-up timing.

Revenue forecasting based on pipeline data, historical close rates, and deal velocity. Reports include pipeline by stage, by owner, by source, conversion rates, average deal size, and sales cycle length.

AI-powered prospecting that identifies potential customers from your visitor data, lead signals, and connected platform activity. Suggests outreach targets, drafts initial messages, and scores lead quality.

Automated multi-step follow-up sequences: email, wait, email, check response, escalate. Define sequences for new leads, stalled deals, post-purchase check-ins, and re-engagement campaigns.

Track customer lifecycle stages (lead, prospect, customer, churned) with automated transitions. The retention agent monitors for churn signals and suggests interventions.

AI agent that continuously cleans and enriches your CRM data: deduplicates contacts, fills missing fields, validates emails, standardizes company names, and flags stale records.

Natural language CRM configuration: tell the AI what your sales process looks like and it builds your pipeline stages, custom fields, deal templates, and automation rules.

Automated audit of your CRM data quality: duplicate contacts, deals without next steps, stale pipelines, missing contact information, and data completeness scoring.

Three-level autonomy control for each CRM AI agent: Autopilot (AI acts independently), Copilot (AI suggests, human approves), and Manual (AI observes only). Set the dial per agent, per action type, and per deal value threshold.

The CRM runs four specialized AI agents: Steward (data quality), SDR (prospecting), Retention (churn prevention), and Analyst (reporting and insights). Each agent has its own Trust Dial setting.

Ready-to-use connectors for Shopify, WooCommerce, BigCommerce, Magento 2, PrestaShop, OpenCart, osCommerce, WordPress, WHMCS, Zendesk, Stripe, Amazon SES, Postmark, Resend, SendGrid, Mailgun, Gmail, IMAP, Slack, and Google Business Profile. Each connector brings platform-specific AI actions, knowledge, and data sync.

Build custom connectors for any platform — no code, AI-assisted, or full code. The builder supports REST and GraphQL APIs, OAuth authorization code flow, webhook auto-registration with Stripe and simple signature schemes, pagination (offset, page, cursor, and link-header), list/error transforms, multi-action context, and marketplace packaging.

The ConnectorBuilderAI helps you build connectors: describe what you want and it suggests actions, writes request handlers, and maps API responses. Handles authentication, pagination, and error handling automatically.

Generic in-app OAuth authorization flow that works with any connector. PKCE support, site-scoped state management, automatic token refresh. Connectors define their OAuth parameters and OpsIQ handles the flow.

Connectors don't just add platform actions — they can power core features through capability "buses". A connector declares a capability (calendar, enrichment, esign in CRM; local_listing, rank_data in Site Intelligence; web_analytics in Analytics; payment_provider in Payments; email_sync in Mailbox; video_meeting in Comms) and implements its small method set; OpsIQ discovers it via CapabilityRegistry and wires it into the UI, the Customer 360 timeline, and the AI actions. Several connectors can offer the same capability with no lock-in. See connectors/PLATFORM_CONNECTORS.md.

Connectors live in one of two tiers. Pre-installed connectors (connectors/) are registry-active out of the box — kept lean to just the keyless reference and the most-used provider per capability (e.g. Google Calendar, Gmail, Google Business Profile). Marketplace connectors (marketplace_connectors/) are discoverable but inert until installed — e.g. Microsoft 365 Calendar, Outlook, DocuSign, Stripe, GA4, SerpApi, Zoom. Every bridge surfaces a marketplace list so the UI and the AI can prompt "install from the marketplace" (notify-to-install) when a capability has no ready provider — never a broken button.

Publish your connectors to the OpsIQ marketplace. Package connectors with profile.json, knowledge.json, workflow_recipes.json, and signed archives. Marketplace supports free and paid connectors with multi-source billing.

All connectors are cryptographically signed for integrity verification. Signing is checked at install time. Use the resign_all_connectors tool to re-sign after updates.

Declarative fuzzy-matching system for connector actions. Define lookup rules and OpsIQ matches user queries to platform entities using fuzzyScore and smartRank algorithms. Example: find_country("germ") matches Germany with 88.9% confidence.

Connectors declare actions with typed parameters, authentication requirements, pagination rules, and response transforms. Over 1,200 HTTP actions across all connectors, all executable through the unified ActionExecutor.

Pre-built workflow recipes that combine multiple connector actions into common business workflows. Example: "When a new order comes in on Shopify, create a ticket, update the CRM, and send a Slack notification."

Connectors declare knowledge topics that sync to the AI knowledge base. Platform-specific help articles, setup guides, and troubleshooting steps are automatically available to the AI without manual knowledge entry.

Full API for visitors, events, tickets, contacts, settings, and connector operations. API key authentication, rate limiting, and JSON request/response format. OpenAPI specification available.

Outbound webhooks for all major events: orders, invoices, subscriptions, tickets, chats, leads, user registrations, and cart abandonment. Async delivery via job queue, exponential backoff retry, SSRF protection, and auto-disable after 15 consecutive failures.

Every outbound webhook is signed with HMAC-SHA256. Verify signatures on your receiving end to ensure webhook authenticity. Stable event_id for idempotent processing.

JavaScript SDK for the tracking widget with identity resolution, custom event tracking, programmatic chat control, and page-specific configuration. Install recipes for React, Vue, Next.js, WordPress, Shopify, and static HTML.

Server-side SDKs and plugins for common frameworks. WordPress plugin, WHMCS module, and generic PHP/Node.js integration libraries.

Push custom events into OpsIQ from your backend: purchases, signups, feature usage, errors, or any business event. Events appear in the visitor timeline and feed into analytics and AI context.

Build automated workflows triggered by events: new ticket, chat started, visitor identified, deal stage changed, or custom event. Triggers execute connector actions, send webhooks, update records, or notify your team.

Visual API and webhook builder inside the admin. Configure endpoints, test requests, inspect responses, and debug integrations without leaving OpsIQ.

Three roles: Owner (full access, billing, danger zone), Full Admin (all operations except billing and danger zone), and Agent (only assigned departments, no settings access). All sensitive pages are hard-gated by role.

Owner and Full Admin-only dashboard showing resolution times, workload distribution, handle depth, channel breakdown, trend analysis, SLA compliance, CSAT by agent, reopen rates, team rollups, and busiest hours. Updated in real time.

Real-time who-is-online widget in the admin navigation. Heartbeat-based presence detection (60-second ping, 300-second extend, auto-prune after 120 days). See which admins are currently active and on which pages.

Each connected site (workspace) can have its own AI configuration, connector settings, ticket departments, branding, and operational rules. Global defaults cascade to workspaces that do not override them.

Manage multiple websites from one OpsIQ admin. Each site has its own tracking snippet, visitor data, and configuration. Switch between sites from the admin navigation.

Registry-driven email templates for all automated communications: ticket notifications, chat transcripts, welcome emails, password resets, and system alerts. Edit HTML templates with live preview, variable chips ({{customer_name}}, {{ticket_id}}), and global layout control.

Import contacts, tickets, and knowledge articles from CSV/JSON. Export visitor data, analytics reports, and CRM records. Data portability for migration between systems.

OIDC (OpenID Connect) single sign-on with full runtime: discovery, authorize, callback, JWKS signature verification, userinfo, domain allow-listing, JIT provisioning, and status guards. SAML configuration support.

Built-in DSAR (Data Subject Access Request) handling: export and delete customer data across all systems. Contact-level data erasure covering sessions, tickets, chats, CRM records, and email logs. Consent management and retention policies.

Block specific IPs or ranges from accessing your site or admin. Automatic lockout after configurable failed login attempts. Failed login log with IP, timestamp, and user agent.

HTTP Strict Transport Security, Permissions-Policy headers, and secure cookie configuration. Self-hosted deployments can add CSP headers through server configuration.

SSRF guard blocks webhooks to private/metadata IP ranges. Async delivery prevents slow endpoints from blocking your application. Auto-disable after 15 consecutive failures prevents resource waste on dead endpoints.

Strict data isolation between workspaces. Visitors, tickets, chats, CRM records, and AI conversations are scoped to their workspace. Cross-workspace data leaks are prevented at the query layer.

Support for monthly, quarterly, semi-annual, yearly, biennial, and lifetime billing cycles. Currency normalization for multi-currency gateways. FX conversion on payment receipt for accurate revenue reporting.

Built-in cron system for scheduled tasks: report generation, data cleanup, subscription renewals, AI training updates, connector syncs, and webhook retries. Health diagnostics with warning indicators.

Configure how long visitor sessions, chat transcripts, AI conversation history, and event logs are retained. Automatic cleanup of aged data to manage storage and comply with retention policies.

System health dashboard showing cron status, database connectivity, AI provider status, connector health, webhook delivery rates, and storage usage. Warnings for configuration issues and performance bottlenecks.

Full website analytics with visitor tracking, session replay, page rankings, geo intelligence, intent funnels, conversion attribution, events, A/B experiments, and JS error tracking — all privacy-friendly, all in one platform.

AI-powered customer chat with knowledge grounding, multi-provider AI support, auto-handoff to humans, proactive chat rules, conversation history, CSAT surveys, and ticket creation from chat.

Native ticket system with departments, priorities, SLA, AI triage, auto-reply with configurable delay, email ingestion, ticket embed, ticket merging, inbox copilot, and Return to AI capability.

AI-first CRM with four specialized AI agents (Steward, SDR, Retention, Analyst), Trust Dial autonomy control, pipeline board, deal coaching, forecasting, sequences, lifecycle management, and natural language CRM configuration.

Site Intelligence with automated crawls, technical SEO audits, content analysis, AI search, SERP rank tracking, keyword research, backlink analysis, local SEO grid, and scheduled white-label reports.

Connector SDK with 25+ pre-built connectors, Connector Builder (no-code/AI-assisted/full-code), OAuth flow, webhook auto-registration, 1,200+ executable actions, SmartLookup, marketplace, and signed packages.

Full GBP connector: review management, post publishing, Q&A management, photo uploads, business info sync, insights tracking, and AI-powered review responses — all from inside OpsIQ.

Registry-driven email templates with visual editor, live preview, variable chips, global layout control, and per-event customization for all automated communications.

Built-in team performance: resolution times, workload, SLA compliance, CSAT by agent, reopen rates, busiest hours, real-time presence tracking, and per-department breakdowns.

Native DSAR handling, data erasure across all systems, consent management, retention policies, and audit trails — built into the platform, not bolted on.

Copy the snippet from Connected Sites and paste it on your website. This gives you tracking immediately.

Go to AI Configuration, pick a provider, enter your key, and save. AI chat is now active on your website.

You now have visitor tracking and AI chat. You can add tickets, CRM, and connectors later.

Go to Knowledge Base and add 5-10 articles about your most common questions. The AI uses these to answer customers accurately.

Go to Tickets and create at least 2 departments (e.g., "Sales" and "Support"). Assign team members to each.

Go to AI Training and write a Customer AI prompt that describes your business, tone, and escalation rules.

Open your website in a private browser and chat with the AI as a customer. Check that answers are accurate and tone is right.

Set up a mailbox (Gmail, IMAP, or a provider connector) so customer emails automatically create tickets.

Enable ticket auto-reply for safe departments. Set a 2-minute delay so humans can intervene first.

Check Dashboard daily. Look at visitor count, bounce rate, top pages, and sales if tracking is connected.

Open AI CRM and let OpsIQ import contacts from your connected platforms. Review the pipeline board.

Check AI History weekly. Look for wrong answers, missed questions, and opportunities to add knowledge.

Create a rule: if a visitor is on the pricing page for 60+ seconds, show a chat message asking if they need help.

If you use a platform that does not have a built-in connector, use the Connector Builder to create one.

Connect OpsIQ to your internal tools using outbound webhooks for ticket, chat, and sales events.

Dashboard, live feed, visitor log, sessions, session replay, top pages, geo intelligence, intent funnel, events log, A/B experiments, JS error tracking, sales and conversions, leads, AI CRM (command center, contacts, companies, deals, pipeline board, deal coaching, forecast, prospecting, sequences, lifecycle, data steward, Build my CRM, CRM config, CRM health, CRM API), tickets, chat inbox, proactive rules, CSAT surveys, email drafts, mailboxes, AI configuration, AI training, AI history, AI insights, knowledge base, connectors, Connector Builder, marketplace, connected sites, team management, team performance, settings, diagnostics, and license.

Website tracking widget (analytics beacon + chat + ticket embed + knowledge base search), client AI chat, ticket submission portal, visitor identity token handling, file uploads, CSAT survey widget, and customer-facing help center.

Command center, contacts, companies, deals, pipeline board with drag-and-drop, AI deal coaching (risk signals, next-best-action, win probability), revenue forecasting, prospecting agent (SDR), automated follow-up sequences, lifecycle and retention management, data steward agent (dedup, enrich, validate), Build my CRM (natural language setup), CRM configuration, CRM health check, Trust Dial (Autopilot/Copilot/Manual per agent), four specialized agents (Steward, SDR, Retention, Analyst), and CRM API with webhooks.

Automated site crawls, technical SEO audit (speed, mobile, Core Web Vitals, SSL, redirects, structured data), content audit (word count, readability, keyword density, heading structure), AI-powered semantic search, SERP rank tracking across engines, keyword research with opportunity scoring, backlink analysis and monitoring, local SEO grid visualization, Google Business Profile sync (reviews, posts, Q&A, photos, insights), scheduled reports (daily/weekly/monthly), and white-label PDF output for agencies.

Customer AI chat (multi-provider: Claude, GPT-4o, Gemini, Grok), admin AI assistant, AI knowledge grounding, auto-handoff with configurable revert, per-workspace AI configuration, managed AI and BYOK modes, token budgets and cost controls, AI history audit trail, AI insights analysis, ticket AI triage, ticket auto-reply with delay, writing AI (separate prompt), and admin inbox copilot.

25+ pre-built connectors (Shopify, WooCommerce, BigCommerce, Magento 2, PrestaShop, OpenCart, osCommerce, WordPress, WHMCS, Zendesk, Stripe, Amazon SES, Postmark, Resend, SendGrid, Mailgun, Gmail, IMAP, Slack, Google Business Profile), Connector Builder (no-code/AI-assisted/full-code), generic OAuth flow with PKCE, connector marketplace with paid distribution, connector signing and verification, SmartLookup fuzzy matching, 1,200+ executable HTTP actions, knowledge sync, and workflow recipes.

REST API (visitors, events, tickets, contacts, settings, connectors), OpenAPI spec, API key management, outbound webhooks (async, signed, retried, SSRF-guarded, auto-disable), Events API for custom event ingestion, widget SDK with identity resolution, triggers cookbook, action contracts, connector SDK, marketplace packaging, server-side SDKs (PHP, Node.js), WordPress plugin, and WHMCS module.

Business identity, AI configuration per workspace, tracking settings, security (HSTS, Permissions-Policy, IP blocking, brute-force protection), RBAC (Owner/Full Admin/Agent), team management and invitations, team performance dashboard, admin presence tracking, email template system (registry-driven, visual editor, variable chips), survey designer, domain knowledge, ticket embed configuration, branding, data retention policies, billing cycle management (monthly through lifetime), currency normalization, import/export, diagnostics, cron automation, and danger zone.

Enterprise SSO (OIDC with JWKS verification, JIT provisioning), SAML configuration, GDPR/DSAR handling (export and delete across all systems), data erasure per contact, consent management, workspace isolation (strict query-layer scoping), audit trails, failed login tracking, IP blocking, outbound webhook SSRF guard, and data retention policies.

Managed AI proxied through OpsIQ provider URL, Site Intelligence provider calls, license validation, health reports, PDF rendering, and data exports — all routed through the configured provider endpoint, not direct vendor API calls from your server.

The number of people on your website right now. This updates every 15 seconds (configurable). A visitor is "active" if they loaded a page within the active threshold (default: 90 seconds).

How many different people visited your website in the selected date range. OpsIQ identifies visitors by a combination of browser fingerprint, cookies, and (if available) authenticated identity.

New visitors are seeing your site for the first time. Returning visitors have been seen before. A high returning ratio means your content brings people back. A very low returning ratio might mean you are not retaining interest.

The percentage of visitors who left after viewing only one page. A bounce rate above 70% on landing pages usually means the page is not meeting visitor expectations — wrong content, slow load, or poor mobile experience.

How long visitors spend on each page on average. Very short times (under 10 seconds) on content pages suggest the content is not engaging. Very long times on checkout pages might indicate confusion.

IP addresses that OpsIQ identified as potentially malicious based on threat scoring, brute force attempts, or manual blocks. Click to see the blocked IPs list.

Revenue from connected sales sources (Shopify, WooCommerce, Stripe, etc.). If sales show zero, check that your platform connector is connected and syncing.

A line graph showing visitor count over the selected date range. Look for patterns: traffic spikes (campaigns, press mentions), dips (weekends, holidays), and sustained trends.

Where your visitors come from: direct, Google, social media, email campaigns, referral sites. Use this to understand which marketing channels are working.

Chrome, Safari, Firefox, Edge, and others. If a browser has unusually high bounce rate, you might have a CSS or JavaScript compatibility issue.

A grid showing visitor activity by hour of day and day of week. Use this to decide when to schedule support shifts, when to send announcements, and when to run promotions.

The last few visitors with country, page, device, and source. Useful for quick spot-checks during campaigns.

The visitor's IP address. Anonymized if IP anonymization is enabled in Settings. Click to see all visits from this IP.

Detected from the IP address using GeoIP data. Requires MaxMind GeoLite2 database or Cloudflare geo headers. Shows "Unknown" if GeoIP is not configured.

The page the visitor loaded. Click to see the full URL. Long URLs are truncated in the table view.

Where the visitor came from before landing on your site. "Direct" means no referrer (bookmarks, typed URLs, some app links).

The visitor's device type (desktop, mobile, tablet) and browser (Chrome, Safari, Firefox, etc.). Parsed from the User-Agent header.

When the page was loaded, in your configured timezone.

If the visitor is identified (via identity token or login), their name or email appears. Otherwise shows as anonymous.

Filter visits to a specific time period. Default: last 7 days.

Search by IP address, page URL, referrer, country, or customer email.

Filter by traffic source: Direct, Organic, Social, Referral, Paid, Email.

Filter by Desktop, Mobile, or Tablet.

Show only first-time visitors who have never been seen before.

Raw page loads. One row per page view. Best for: investigating specific pages, finding traffic from specific sources, diagnosing tracking issues.

Groups page views into journeys. One row per visit session. Best for: understanding user flow, measuring session duration, identifying conversion paths.

Real-time activity. Shows visitors currently on your site. Best for: monitoring campaigns in progress, spotting high-intent visitors, watching support opportunities.

The landing page — where the visitor entered your site. This tells you which content is attracting people.

The exit page — where the visitor left. If the exit page is often the pricing page, visitors might be comparing you with competitors.

How many pages the visitor viewed in this session. More pages usually means more engagement, but it can also mean the visitor is lost.

Total time from first page load to last activity. Sessions with 0 seconds are bounces (single page view, no further interaction).

The traffic source for this session (Direct, Google, social, referral, etc.).

Detected country from the visitor's IP address.

Whether the visitor left after viewing only one page. Bounced sessions have a red indicator.

Whether the visitor completed a tracked conversion event (purchase, signup, form submission) during this session.

Search by IP, email, page URL, or referrer within sessions.

Filter by New visitors (first session ever) or Returning visitors.

Filter by traffic source.

Filter by country to see sessions from a specific region.

Filter to show only bounced sessions or sessions flagged as threats.

How often the live feed updates. Default: 15 seconds. Lower values (5-10s) give faster updates but use more server resources. Higher values (30-60s) are easier on the server but less real-time.

How long a visitor is considered "active" after their last page load. Default: 90 seconds. If a visitor loads a page and then reads it for 2 minutes without clicking, they disappear from the live feed after the threshold.

Click Pause to stop auto-refresh. Useful when you want to read details without the list updating. Click Resume to restart.

The full URL path. Similar pages (e.g., product variants) are grouped if grouping is enabled.

Total number of times this page was loaded in the selected date range.

How many different people viewed this page (a person viewing the same page twice counts as 1 unique).

Percentage of visitors who left your site after viewing only this page. High bounce on landing pages = problem. High bounce on "thank you" pages = normal.

How long visitors spend on this page on average. Very short = not reading. Very long on a form page = confusion.

How many chat conversations were started from this page. High chat starts on a product page means the product description might be unclear.

How many support tickets were created by visitors who were on this page. High ticket count = potential UX or content problem.

The top countries ranked by visitor count. Click a country to drill down to city-level data.

Visual breakdown of traffic by country. Hover for percentages.

Every country with visitors in the selected period, showing visitor count, session count, bounce rate, and conversion rate.

Click a country to see which cities within that country have the most visitors.

Visitors casually looking around. Short sessions, few pages, no specific goal detected.

Visitors reading product/feature pages, docs, or blog content. Longer time on page, multiple content pages.

Visitors viewing pricing, plan comparison, or feature tables. Often returning visitors.

Visitors on checkout, cart, or signup pages. High intent — these are your conversion opportunities.

Visitors on help pages, contact pages, or starting chat. They need assistance.

Visitors who left after one page. Low engagement.

A horizontal bar showing events over time. Click anywhere on the timeline to jump to that moment.

Each page load appears as a segment on the timeline. You can see the exact path the visitor took.

Click events are shown as dots on the timeline and as highlights on the page reconstruction.

Scroll depth is tracked so you can see how far down the visitor read.

Field focus and typing events are recorded. Text input in password and sensitive fields is masked by default.

Fired every time a tracked page loads. Includes URL, title, referrer, and timestamp.

Fired when a visitor opens the chat widget and sends their first message.

Fired for each message in a chat conversation (both visitor and AI/agent).

Fired when a new support ticket is created (from chat, email, widget, or admin).

Fired when a reply is added to a ticket.

Fired when a purchase is completed through a connected platform.

Fired when a tracked form is submitted (if form tracking is enabled).

Fired when a visitor is identified via an identity token.

Fired when a login attempt fails.

Filter by specific event names: pageview, chat.started, ticket.created, etc.

Show events from a specific time period.

Search event data by keyword (URL, email, event property values).

Created but not yet started. You can still edit variants and metrics.

Actively assigning visitors to variants. Do not edit while running.

Reached statistical significance or was manually stopped. Results are final.

Results have been reviewed and the experiment is no longer needed in the active list.

Decide what you are measuring before starting. Choosing a metric after seeing results introduces bias.

Add your team's IP addresses to the exclusion list so staff visits do not skew results.

Do not stop an experiment after 100 visitors. You need hundreds or thousands of visitors per variant for reliable results.

If you change the headline AND the button color, you will not know which change caused the improvement.

After the experiment ends, note which variant won and why you chose to implement it.

The JavaScript error text (e.g., "TypeError: Cannot read properties of undefined").

Which page the error occurred on.

Which browser and device type saw the error. Some errors are browser-specific.

The code location where the error occurred. Click to expand the full stack trace.

When this error first appeared.

When this error most recently occurred.

How many times this error has been recorded.

How many different visitor sessions experienced this error.

Revenue from orders completed today. Refreshes with each new order event from your connected platform.

Revenue aggregated over the period. Refunds are subtracted from these totals.

Line graph showing daily revenue over the selected date range. Look for spikes (promotions, campaigns) and dips (issues, seasonal).

Which traffic sources lead to the most purchases. "Direct" buyers often bookmarked your site. "Google" buyers found you through search.

The latest orders with customer email, amount, currency, and items purchased.

Go to Connectors > Shopify. Create a custom app in your Shopify admin (Settings > Apps and sales channels > Develop apps). Grant scopes: read_orders, read_customers, read_products. Copy the Admin API access token. In OpsIQ, enter your store domain (e.g., your-store.myshopify.com) and the access token. Click Test Connection. If successful, enable webhook sync for real-time order notifications.

Go to Connectors > WooCommerce. In your WordPress admin, go to WooCommerce > Settings > Advanced > REST API. Create a key with Read/Write permission. Copy the consumer key and consumer secret. In OpsIQ, enter your site URL, consumer key, and consumer secret. Click Test Connection.

Go to Connectors > BigCommerce. In your BigCommerce admin, go to Advanced Settings > API Accounts. Create a V2/V3 API Account with read scope for Orders, Customers, and Products. Copy the access token, client ID, and API path. Enter them in OpsIQ and test.

Go to Connectors > Magento. In your Magento admin, go to System > Integrations. Create a new integration with API resource access to Sales, Customers, and Catalog. Activate the integration and copy the access token. Enter it in OpsIQ with your Magento base URL.

Go to Connectors > PrestaShop. In your PrestaShop admin, go to Advanced Parameters > Webservice. Enable the webservice and create a new key. Grant access to orders, customers, and products. Copy the key and enter it in OpsIQ with your store URL.

Go to Connectors > OpenCart. Generate API credentials from your OpenCart admin panel. Enter the API URL, username, and key in OpsIQ. The connector uses OpenCart's REST API for order and customer data.

Go to Connectors > osCommerce. Configure database access or API credentials as documented in the connector settings. osCommerce integration typically requires direct database access or a custom API module.

Go to Connectors > Stripe. Copy your Stripe restricted API key from the Stripe Dashboard (Developers > API keys). The key needs read access to Customers, Charges, Invoices, and Subscriptions. Enter it in OpsIQ. Configure webhook endpoint for real-time events.

Go to Connectors > Paystack. Copy your Paystack secret key from the Paystack Dashboard. Enter it in OpsIQ. Configure webhook URL for transaction notifications.

Use the REST API or webhooks to send sales events from any platform. Send order.completed events with customer email, amount, currency, and items. See the Events API section for the payload format.

Shows which channels bring paying customers. If Google brings 1000 visitors and 50 sales, that is a 5% conversion rate. If email brings 200 visitors and 30 sales, that is 15% — email is more effective per visitor.

Refunded orders are tracked separately. They reduce your net revenue totals. If refund rates are high from a specific source, the traffic might be low quality.

OpsIQ stores the original transaction currency and amount. Multi-currency businesses see revenue in each currency. Normalized reporting uses the configured exchange rate.

Visitors who view your pricing or plans page are actively considering a purchase.

Visitors who come back multiple times are engaged but not yet converted.

Visitors who start a chat are actively seeking help — either pre-purchase or post-purchase.

Visitors who reach the checkout page but do not complete the purchase.

Visitors who submit a contact form, demo request, or signup form.

Visitors who view many pages with long session duration are deeply researching.

Name, email, company if known. Anonymous leads show IP and location.

All sessions from this lead with page flow, duration, and source.

Every page they visited, ordered by recency.

How they found you: organic, paid, social, referral, direct.

A 0-100 score based on behavior intensity, recency, and page intent.

Whether this lead has been added to the CRM as a contact or deal.

AI-generated suggestion on what to do next (e.g., "Visited pricing 3 times — consider proactive outreach").

AI proposals go to the approval queue. You approve, edit, or reject each one. Nothing happens without your say.

When AI suggests a change, it shows the current value and the proposed value. Human-entered data has provenance protection.

Every AI action is recorded in the journal. You can undo any change with one click.

Every AI recommendation shows its reasoning and the data sources it used. No black box.

Pipeline value, deals won/lost, new leads, active deals, and revenue trend — a snapshot of your current state.

AI-discovered insights: stalled deals, at-risk accounts, new opportunities, data quality issues, and market signals.

Actions the AI has taken (in Autopilot) or proposed (in Copilot): stage advances, score updates, contact enrichment, and task creation.

Queue of AI proposals waiting for your decision. Each shows the proposed action, reasoning, and evidence. Approve, edit, or reject.

AI-ranked list of the 10 most important things to do today: follow up on a hot deal, check an at-risk account, research a new lead, etc.

Health of AI agents: Capture, Data Steward, Deal Intelligence, Deal Coach, SDR, Retention. Green = running, amber = needs attention, red = error.

ROI tracking: deals influenced by AI, time saved, accuracy of predictions, and comparison to manual CRM work.

A person in your CRM. They might be a customer, a prospect, a partner, or a lead. Contacts have an email, name, company, tags, lifecycle stage, and hotness score.

Use the search bar to find by name, email, company, or tags. Use filters: lifecycle stage, lead score, source, country, last activity date, assigned owner.

Click a contact to see their full profile: personal info, company, deals, activities, tickets, chats, website visits, lead score, and AI insights.

A 0-100 score calculated from behavior signals: website visits, email engagement, chat interactions, purchase history, and recency. Higher = hotter.

An organization that one or more contacts belong to. Companies have a name, domain, industry, size, and health score.

Contacts are linked to companies by email domain or manual assignment. One company can have many contacts.

A revenue opportunity. Deals have a title, amount, pipeline, stage, win probability, close date, assigned owner, and associated contacts/company.

A percentage chance of winning the deal. Set manually or calculated by AI based on your historical win data. Drives the weighted forecast.

Green (healthy), amber (at risk), or red (stalled). Based on activity recency, stage duration, and engagement signals.

A follow-up action assigned to a person. Tasks have a title, due date, priority, type (call, email, meeting, other), and linked contact/deal.

The AI creates tasks automatically when it detects something needs attention: follow up on a stalled deal, respond to an at-risk account, research a new lead.

Accept the proposal as-is. The action runs through the Trust Layer and is recorded in the journal.

Modify the proposal before approving. For example, change the suggested stage or adjust the amount.

Decline the proposal. The AI learns from rejections to make better suggestions in the future.

Why the deal is healthy, at risk, or stalled. Specific signals: days in stage, last contact date, activity frequency, competitor mentions, objection patterns.

Categorized into: objections raised, competitor mentions, pricing discussions, support risk indicators, renewal/expansion signals. Each signal links to its source (chat transcript, ticket, email, activity).

Who is helping the deal (champion) and who is resisting (blocker). Based on interaction analysis and contact roles.

MEDDICC or BANT checklist (configurable) showing which qualification criteria are met and which are missing. Grade: A, B, C, D, or F.

Before a scheduled meeting, the coach generates a brief: agenda, key points to cover, questions to ask, risks to address, and materials to prepare.

Suggested next message or call script based on the current deal state and recent interactions.

Every claim the coach makes links to a source: a ticket number, chat transcript ID, activity date, or website visit.

Deals with 80% or higher win probability. These are your most likely wins. This should be your minimum expected revenue.

All open deals weighted by their AI-calculated win probability. This is the most realistic prediction of what you will close.

All open deals at full value. This is the maximum possible revenue if everything goes perfectly (it rarely does).

An 80% probability band showing the realistic range. Example: "You will likely close between ₦54,000,000 and ₦86,400,000 this quarter."

Mean Absolute Percentage Error — how far off your forecasts have been historically. Lower is better. A MAPE of 15% means your forecasts are typically within 15% of actual results.

Brier score measuring how well win probabilities match actual outcomes. If deals at 70% probability actually win 70% of the time, calibration is good.

OpsIQ captures a snapshot of your forecast each week (via cron). Over time, you can see how your forecast accuracy improves.

How many deals move from each stage to the next. If 80% pass from Qualified to Proposal but only 20% go from Proposal to Negotiation, your proposals might need work.

Which lead sources produce the most wins. Invest more in high-win-rate sources.

How each sales team member is performing: deals won, pipeline value, average deal size, win rate.

Sandbagging (unrealistically low probabilities), overcommitting (unrealistically high), and committed-at-risk (high-probability deals showing stall signals).

How well the company matches your ideal customer profile (industry, size, location).

Is there evidence they need your product now? Job postings, tech changes, complaints about competitors.

Company size, funding stage, and revenue indicators suggest budget availability.

How relevant your product is to their business based on industry and technology.

Whether you can effectively serve this customer (timezone, language, complexity).

Interested, wants to talk. Sequence pauses, task created for follow-up.

Has concerns but not rejecting. Sequence pauses, task created with objection details.

Wants to stop receiving messages. Contact is suppressed permanently.

Interested but timing is wrong. Sequence pauses, snooze task created.

Not the right contact. Sequence stops, contact flagged for review.

A support question, not a sales response. Sequence pauses, ticket created.

Unsubscribe requests are honored immediately and the contact is suppressed from all future sequences.

Workspace-level daily limit (default: 1,000 emails). Prevents mass sends that trigger spam filters.

Maximum 1 message per contact per day. Prevents overwhelming individual people.

Steps that exceed the daily cap are deferred to the next day. They are never dropped or skipped.

Visual board showing where every account stands: Lead, Prospect, Opportunity, Customer, Expansion, Renewal, At Risk, Churned.

Accounts flagged with high churn risk. Each shows the top driver (support spike, inactivity, payment failure) and a recommended save play.

Accounts that show signals of readiness to buy more: high usage, feature requests, plan inquiries.

Accounts with upcoming renewal dates. Sorted by risk level and revenue value.

Deal health, inactivity, recent losses, declining engagement.

Open ticket count, ticket volume spikes, negative sentiment, escalations.

Login frequency, feature usage, page visits, API calls.

Failed payments, overdue invoices, downgrade requests, cancellation page visits.

For at-risk accounts: reach out proactively, address the concern, offer support, escalate if needed.

For upcoming renewals: confirm satisfaction, review usage, present value, offer incentive if appropriate.

For ready-to-grow accounts: present upgrade options, share success stories, demonstrate ROI.

For underutilizing accounts: offer training, share best practices, enable features they are not using.

Multiple records for the same person (e.g., [email protected] and [email protected]). The steward proposes merging them.

Contacts without email, deals without amounts, companies without domains. Suggests filling from available sources.

Deals without associated contacts, contacts without companies. Proposes linking based on email domain and context.

A deal in "Won" stage with 20% probability, a contact marked "Customer" with no deals, a company with mismatched industry.

Deals that have been in the same stage for too long or contacts whose lifecycle stage does not match their activity.

Create named pipelines with custom stages, default probabilities, and rotting thresholds.

Boost lead scores based on behavior: "Score higher when they view pricing," "Score lower when they visit careers page."

Automatically advance lifecycle stages: "Move to SQL when they request a demo," "Move to Customer when deal is won."

Add fields to contacts, deals, or companies: text, number, date, select, checkbox, URL, email.

Define the MEDDICC or BANT checklist the Deal Coach grades against.

Create, rename, reorder, and delete pipelines and stages. Set default win probability per stage. Set the rotting threshold (days without activity before a deal is marked "stalled").

Add fields to deals, contacts, or companies. Field types: text, number, date, select (dropdown with predefined options), checkbox, URL, email. Custom fields appear on the object profile and in filters.

Define the checklist the Deal Coach uses to evaluate deals. Choose MEDDICC, BANT, or a custom set of criteria. Each item can be marked required or optional.

Define automatic stage transitions: when a contact meets a condition (views pricing, submits a form, makes a purchase), their lifecycle stage advances automatically.

Boost or reduce lead scores based on behavior. Examples: "Viewed pricing page = +15 points," "Downloaded whitepaper = +10 points," "Visited careers page = -5 points." Minimum count can be set (e.g., "must view pricing at least 2 times").

Create named filter+sort combinations for contacts, deals, or companies. Share views with your team. Set a default view per object type.

Database tables exist and have the correct columns. If a migration was missed, CRM Health will flag it.

All CRM agents (Capture, Data Steward, Deal Intelligence, etc.) are registered and healthy. Green = running, amber = needs attention, red = error.

CRM API routes and AJAX endpoints are registered and callable.

The CRM action catalog is registered in the Action Registry. If actions are missing, CRM Health self-heals by re-registering them.

Total contacts, companies, deals, tasks, activities, and events. Useful for verifying imports and ongoing data capture.

API key (Authorization: Bearer opq_...) with scope crm.read or crm.write. POST to /api/v1.php with action and site_key.

crm.contacts.list (search + filter), crm.contacts.detail (by ID), crm.contacts.upsert (create or update), crm.contacts.save.

crm.deals.list, crm.deals.detail, crm.deals.create, crm.deals.update, crm.deals.advance (all through the Trust Layer).

crm.activities.list (timeline for a contact/deal), crm.activities.record (log a new activity).

crm.events.list (durable change feed with since_id cursor), crm.events.catalog (list available event types).

Fired when a new contact is added to the CRM.

Fired when a deal moves to a different stage.

Fired when a deal is closed as won.

Fired when a deal is closed as lost.

Fired when a new task is created (manual or AI-generated).

Fired when a prospect replies to a sequence email.

Fired when an AI agent creates a proposal for the approval queue.

Move the ticket to a different department (e.g., from General to Billing). Useful when the initial routing was wrong.

Assign the ticket to a specific team member. The assigned agent sees the ticket in their "My tickets" view.

Write a note visible only to staff. Use for: investigation findings, refund reasons, engineering context, previous commitments. Internal notes never appear to customers.

Combine duplicate tickets from the same customer. The merged ticket subject gets a [MERGED] tag. All messages from both tickets are preserved in the surviving ticket.

Insert a pre-written reply template. Variables like {{customer_name}} and {{ticket_id}} are automatically replaced.

Let AI improve your draft reply: adjust tone, shorten/lengthen, fix grammar, or translate. You review the result before sending.

Set to Low, Normal, High, or Urgent. Priority affects SLA timers and sort order.

Set to Open, Pending, Waiting on Customer, Resolved, or Closed.

Non-urgent questions, feature requests, general feedback. Target first response: 24 hours.

Standard support questions. Target first response: 8 hours.

Impacting the customer's business. Target first response: 4 hours.

Service down, security incident, data loss, billing error. Target first response: 1 hour.

Master switch. Turn on to enable AI auto-reply for tickets.

Which departments can receive auto-replies. Start with low-risk departments (General, Sales) before enabling billing.

How long to wait before the AI replies (in seconds). Default: 120 seconds (2 minutes). Set to 0 for instant replies.

Optionally set different delays for business hours vs. after hours.

If a human agent replies first, cancel the auto-reply. Default: on.

Enable automatic department routing based on ticket intent.

Which departments tickets can be escalated to.

What status to set when escalating (e.g., Open, Pending).

Whether to add an internal note explaining the escalation reason.

Renders the ticket portal inside a div on your page. The portal takes the full width of its container.

Shows a floating button that opens the ticket portal in a panel. Similar to a chat widget.

Requires a signed identity token. Customers see only their own tickets.

Searchable, status-filtered list. An "Awaiting you" highlight flags tickets the team has answered.

Full conversation view with rich text, attachments, and timestamps.

Customer draft replies are auto-saved so they do not lose work if they navigate away.

The widget polls for new replies every ~12 seconds.

Customers can resolve or reopen their own tickets with one click.

Conversations currently in progress. Green dot = customer is typing or recently active.

Conversations where the AI is responding. You can take over at any time by clicking "Join."

Conversations assigned to you specifically.

Conversations where the customer is waiting for a response.

Completed conversations. Searchable by keyword, date, and customer.

IMAP (most providers), Gmail API (Google Workspace), or Microsoft Graph (Outlook 365).

Host, port, encryption (SSL/TLS), username, password or app password, folder (usually INBOX).

Map the mailbox to a ticket department. Emails to [email protected] create tickets in the "Support" department.

Read the draft and check for accuracy.

Modify the text, tone, or content before sending.

Approve the draft and send it as an email reply.

Delete the draft if it is not appropriate.

If confidence is high enough and auto-send is enabled, drafts are sent automatically after a configurable delay.

Strong reasoning, careful with facts, good at following complex instructions. Models: claude-sonnet-4-20250514, claude-3.5-sonnet. Best for: support conversations, technical questions, detailed analysis.

Fast, creative, good general knowledge. Models: gpt-4o, gpt-4o-mini. Best for: quick responses, creative writing, broad knowledge questions.

Good at factual questions, multi-language support. Models: gemini-2.0-flash, gemini-1.5-pro. Best for: multi-language support, factual lookups.

Fast, concise responses. Models: grok-3-mini-fast. Best for: quick answers, casual tone.

You provide your own API key from the provider. You pay the provider directly. Full control over model selection and usage.

AI is provided as part of your OpsIQ plan. No API key needed. Usage is metered against your plan's AI credit balance.

Set a maximum monthly spend on AI tokens. When the budget is reached, AI features gracefully degrade (shorter responses, no auto-reply) rather than stopping entirely.

Maximum tokens per single conversation. Prevents runaway conversations from consuming excessive credits.

When your AI credit balance drops below the threshold (default: 50,000 tokens), a warning appears in the admin. Set this in AI Configuration.

Go to console.anthropic.com > API Keys > Create Key. Copy the key starting with "sk-ant-".

Go to platform.openai.com > API Keys > Create new secret key. Copy the key starting with "sk-".

Go to aistudio.google.com > Get API Key. Create a key for your project. Copy the key.

Go to console.x.ai > API Keys. Create and copy your key.

Up to a few read-only lookups per turn, cross-referenced before answering. Turn on when you have a connected platform (WHMCS, Shopify, Stripe, Zendesk, etc.). Off = today's single-lookup behaviour, unchanged.

How hard the model reasons on complex turns (low/medium/high). Start on Low; most support questions are handled well there.

Pins a stronger model just for complex agent turns, so everyday chat stays on a light, cheap model and only the hard turns pay for depth. Blank = your normal customer-chat model.

A tiny planning step decides which lookups to pull and whether the knowledge base is needed, then answers in ONE main call instead of several steps. A sub-toggle under Agent mode — it cannot be enabled unless Agent mode is on. Same answer quality, fewer calls on multi-part questions.

Keeps a short running summary of older messages (names, ticket/invoice numbers, amounts, decisions) so the assistant stays consistent across very long chats without resending the whole transcript. Best for support-heavy, long threads; pairs with Agent mode.

Reads small typos ("my open ticketts", "unpaid invocies") as the intended words so the right information is found instead of missed. Works with every connected platform. Off by default; useful for mobile-heavy chat.

Only attaches the customer's account snapshot when the question is actually about their account (balance, invoices, tickets, services), skipping it on general questions. Cuts cost with no quality loss — the assistant can still fetch the account live when a turn needs it.

"Hi", "thanks" and "ok" don't trigger a knowledge-base search — those replies never use it. Any message with real content still searches as normal.

Caps how long a single reply can be. Reply length is the most expensive part of a call, so a sensible cap (around 500 for support) is the single most effective chat cost control. Only lowers your global limit, never raises it.

How much the model thinks before answering (minimal to high). Keep customer chat on minimal/low for speed; reserve higher settings for analysis and the admin copilot.

Every AI surface — live chat, ticket drafts, summaries, analysis, admin copilot, promotions, Site Intelligence and more — can run on its own model. Light where speed matters, strong where quality matters. Blank on a surface = provider default for that job.

The admin copilot can keep a bounded working memory and load only the tools a question needs (lean tools) instead of every tool every turn.

Your instructions are sent on every turn, so their length is a recurring cost. The Compress button rewrites a slot to say the same thing in fewer words. It refuses the rewrite if it would drop any {variable} or rule, and reports what it protected — so it never silently changes meaning.

Shows what OpsIQ already knows about your business per slot, so you can delete anything you were repeating in your own instructions.

What the agent web search uses. The default is DuckDuckGo: keyless, free, works on every install. Brave Search, Tavily and Serper.dev (Google results) usually return better results but each needs an API key from that provider. If a keyed provider fails for any reason (bad key, quota used up, network trouble), that search falls back to DuckDuckGo automatically, so search never goes dark.

The key for your chosen provider, only needed for Brave, Tavily or Serper. Once saved it is masked and never shown on the page again; paste a new one to replace it. A keyed provider becomes active only when both the provider and its key are saved.

Controls how the AI talks to your customers in the chat widget. This is the most important prompt to get right.

Controls how the AI assists your admin team in the operator dashboard. This handles internal queries and action execution.

When the conversation happened.

Name and email if known, otherwise IP and country.

Chat widget, ticket auto-reply, email draft, or admin AI.

Full transcript of the conversation: customer messages and AI responses.

How many tokens the conversation consumed. High token usage may indicate the AI is giving overly verbose answers or the conversation went in circles.

Any actions the AI executed during the conversation (looked up order, created ticket, etc.).

If CSAT is enabled, the customer's satisfaction rating for this conversation.

Search for specific topics to see how the AI handles them. Example: search for "refund" to check if the AI is following your refund policy.

Show only low-rated conversations to focus on dissatisfied customers.

Show only ticket auto-replies to audit automated responses separately from chat.

High-token conversations may indicate problems: the AI rambling, going in circles, or failing to answer the question.

The most frequently asked questions. If "How do I reset my password?" is #1, your knowledge base needs a prominent password reset guide.

CSAT scores over time. Is AI satisfaction improving or declining? Sudden drops may indicate a knowledge base change that broke something.

What percentage of conversations does the AI resolve without human intervention? A rate above 70% is good. Below 50% means the AI needs more training.

Why conversations get handed off to humans. Common reasons: customer requested human, AI could not answer, sensitive topic, billing issue.

Topics where the AI frequently says "I don't know" or gives low-confidence answers.

How many messages per conversation. Very long conversations (10+ messages) might indicate the AI is not understanding the question.

Ask: "Show me all tickets from [email protected]" or "What is the status of order #ORD-5523?"

Ask: "Summarize the last 10 tickets" or "What are the top support issues this week?"

Ask: "How do I set up auto-reply?" or "What does the bounce rate card mean?"

Ask: "Create a ticket for [email protected] about billing" or "Close ticket T-12345"

Ask: "How many visitors did we get yesterday?" or "What is our revenue this month?"

Write a separate article for each topic: return policy, shipping rates, account setup, password reset. Do not combine unrelated topics.

Start with the question customers ask, then provide the answer. This helps the AI match questions to articles.

"Returns must be initiated within 30 days of delivery" is better than "We have a return policy."

What about international returns? What about digital products? What about items bought on sale? Cover the exceptions.

Review articles quarterly. Delete outdated information. Update pricing, policies, and procedures when they change.

Open the article, mark it published, and turn on the option to show it in the Help Center.

Use the <strong>Publish All</strong> button to push your whole published set to the Help Center in one click, instead of doing them one at a time.

Already have FAQs? Use <strong>Publish all to Help</strong> to turn them into help articles so they sit alongside everything else.

Scans your pages for technical SEO issues and lists every page with its problems. Re-run any time, or schedule it.

Add the keywords you care about; OpsIQ checks where your site ranks and tracks movement over time.

Discover new keyword ideas to target, with the AI keyword coach to help prioritise.

See who links to you, refresh the list, and disavow links you do not want associated with your site.

Add competitor domains and compare your visibility against theirs, with an AI competitor analysis.

Scan local-listing visibility across a geographic grid to see where you show up on the map, plus Google Business Profile tools.

Run page-speed checks so you can fix slow pages that hurt rankings and conversions.

Generate content briefs and drafts aimed at the keywords you are targeting.

Build printable, customer-ready reports of everything above.

sitemap.xml, robots.txt, and redirect, canonical and header rules in .htaccess (Apache / LiteSpeed) or the nginx config.

Collapses a multi-hop redirect chain down to a single hop straight to the final URL, inside the same managed .htaccess block, so speed and link value stop leaking through the extra hops.

Missing or weak page titles, meta descriptions, canonical tags and structured-data (schema) blocks.

Yoast, Rank Math and SEOPress titles & meta, and image alt text, applied through WP-CLI on the SSH path or the REST API on the hosted path.

Adds JSON-LD (schema) to pages that are missing it. On the SSH path a small managed helper (a must-use plugin) prints the markup so it works with or without an SEO plugin; on the hosted path your SEO plugin carries it.

Adds one relevant internal link inside existing WordPress content to rescue orphan pages and connect related posts. One link per page, never inside a heading, an existing link or a shortcode, and always approved by you first.

Drafts full replacement content for thin pages (turned on by a crawl option, see below). Every draft is reviewed and approved by you before anything publishes, and the old content is kept so it can be restored.

Turns on W3 Total Cache page caching when the crawl finds speed problems and that plugin is installed, so pages serve faster.

Product and collection SEO titles & descriptions, page and blog-article SEO, plus 301 redirects, through the Shopify Admin API.

Per-page SEO title and meta description through the Webflow Data API v2.

Every crawl also writes the concrete fix content (titles, meta descriptions, alt text, schema, redirects) for what it found, so the fixes are ready to review and apply the moment the crawl finishes instead of being generated later on demand. Uses AI credit on each crawl.

The agent may draft full replacement content for thin pages. Nothing is ever published on its own: each draft appears as a change you review side by side and approve or reject, the previous content is kept so it is reversible, and it is limited to a few pages per pass. Uses AI credit per draft.

Shopify and WordPress connectors ship with OpsIQ — just enable them under Connectors and add the store / site credentials.

Webflow, Wix and Squarespace install from Connectors → Marketplace, then connect the same way.

The agent can only do what Site Intelligence recommended for that domain — it cannot make arbitrary changes to your site or server.

Every write is previewed as a diff and applied only after you approve that specific step.

A snapshot is saved before each write, so any change can be reverted.

Each changed page is re-checked the instant it is written and gets a “fixed live” verdict, so a fix is confirmed against the live page right away, not only in the closing re-crawl.

Internal links and thin-page content rewrites are higher-impact, so they are always shown to you for approval and are never applied automatically, whatever mode you run.

Auto-Implement runs on Managed AI; it is blocked when a workspace is using its own (BYOK) keys.

AI tokens bill normally as you use them, plus one flat per-use fee per Auto-Implement session — both drawn from the same Managed-AI credit.

Show only in (or hide from) chosen countries, cities or timezones via GeoIP. Great for region-specific offers or a geo-redirect.

Limit to certain pages using equals / starts-with / contains / regex, and exclude pages too.

Desktop, tablet or mobile — e.g. a slim bar on mobile, a modal on desktop.

New, returning, known (in your CRM) or anonymous; CRM segments, lifecycle stage, lead score or browser language.

By UTM (utm_source, utm_campaign) or referring site — e.g. only visitors from a specific ad.

Start / end dates, time-of-day windows, and how often a person can see it (per session, per day, after they close / click / convert).

Show to a percentage of visitors and run variants head-to-head; the same person always sees the same variant.

With a connector enabled, target by live account state — e.g. customers with unpaid invoices, or active subscribers.

Split traffic across design variants; let the studio promote the statistical winner automatically, or hand traffic to the bandit optimiser which shifts visitors toward what converts as evidence comes in.

Reserve a slice of visitors who see nothing, so you can prove the campaign itself causes the lift.

Different content per audience on the SAME campaign — mobile visitors, big carts, returning customers — each segment gets its own version.

Variants can also test WHEN to appear: immediate vs delayed vs exit-intent, measured head-to-head.

Target by what someone did with another campaign — "saw campaign A but didn't convert" — to build multi-step promotion sequences.

A small pill visitors can reopen after closing the campaign, so a closed pop-up is never gone for good.

Chat with the design copilot to edit the canvas ("make the headline urgent, add a countdown"), get campaign ideas from your own traffic data, translate a campaign per country, or auto-fix a low design score.

One command reads your website and proposes your real brand colours and fonts; save and every picker leads with them.

Steps blocks get true per-screen editing — tabs for each screen, add or reorder screens, and the preview follows along.

Name important versions ("Launch candidate"), restore any of them, and see a warning when a teammate is editing the same campaign.

See desktop, tablet and mobile side by side in one view; toggle pixel rulers for precise placement.

Every campaign can also be a standalone hosted page for bios and QR codes, an email drip sequence for captured leads, or a one-click web-push draft.

Publish freeze windows (change-freeze periods), an emergency pause-all switch, approvals, audit trail and version rollback.

Pick from a large library of banner designs and a full colour system — transparent, solid or gradient — to match your brand.

Fine-tune wording, button labels, policy links, banner position, and how long a choice is remembered.

Define your own cookie categories and the wording visitors see. You decide what is essential — essential is always on; everything else is theirs to allow or refuse.

Scan your site and let OpsIQ AI auto-detect every cookie and tracker, categorise it, and write a plain-language purpose. This powers the preferences table and auto-blocking.

Choose how consent behaves by law (below), and turn on group-domain sharing, Google Consent Mode v2, and re-consent intervals.

See live consent stats from real visitor choices — accept rates, by category — scoped to your workspace.

When the path is predictable and you want it identical every time — booking steps, a returns wizard, a "which plan?" chooser, collecting an email before handoff. Flows never improvise.

When questions are open-ended — "does this work with my setup?". The Customer Chat AI answers from your trained knowledge. A flow can hand off to the AI (or a human) at any step.

Runs as the opening message when a visitor first opens the chat.

Runs when the visitor types a word you listed (e.g. refund, pricing, cancel).

Starts once contact details are shared, or a set time into the conversation.

Runs as the chat wraps up (e.g. a rating), or is started by a Proactive Message rule.

Each step targets an element and shows a bubble with your text. Add as many stops as the walkthrough needs and order them.

Start from a preset or design your own bubble — colours, gradients, spotlight — with a live preview on the right.

Optionally link a Proactive Rule so the tour auto-starts when that rule fires (e.g. a returning visitor's first dashboard visit).

A tour is eligible to run only while Active is ticked. Untick to take it down without deleting it.

Write a personalised 1:1 email with {tokens} from the contact and CRM.

Send to a CRM segment, scheduled or now, with caps and send-time control.

Reusable message templates for repeated outreach.

Reply detection records responses and auto-stops follow-ups to anyone who replied.

A searchable record of every consent grant and revoke — by contact, channel (email, push, SMS, in-widget), action, source and date. Your proof a contact agreed (or withdrew).

Who on your team viewed, edited, exported, erased or messaged a contact's data — with the admin, contact, action, stated reason and IP. Exactly what a regulator asks for.

Declare where this workspace's data lives, set how many days activity rows are kept (0 = forever), and record your data controller and DPO.

A printable Data Processing Addendum that fills in your controller, address, DPO, residency and retention. Print or save as PDF.

The AI can look up customer data, orders, subscriptions, and more through the connector. When a customer chats, the AI has real platform data to reference.

Your connector's ContextProvider feeds the ticket-AI a read-only account summary of the ticket owner. Resolve the customer by <code>customer_id</code> when known; otherwise — on ticket auto-replies, where the ctx flag <code>customer_trust_email</code> is true — look the account up by <code>customer_email</code> (the verified ticket sender). Remote platforms expose a <code>/context/customer-by-email</code> endpoint and the connector calls it. This is what makes the AI quote a real balance/invoice instead of saying “please log in.” Honour the operator's data-class toggles (<code>customer_sections</code>, <code>customer_allow_credit</code>) and stay strictly read-only — never emit secrets.

Your connector's IdentityProvider feeds three universal ticket lookups: <code>lookupCustomerById()</code> (customer card), <code>lookupCustomerServices()</code> (product/service table), and <code>listCustomers($query,$limit)</code> — the "Search customer or type email" picker on the native Compose-New-Ticket form. Return rows of <code>{id, external_id, name, email, company, phone, platform, platform_label}</code>. <strong>Remote rule:</strong> if your customers live in another database or service, fetch them over your platform's API inside these methods — never read the other system's tables directly (in the OpsIQ DB they're empty placeholders, which is why a local read returns an empty picker). Gate the remote path on your configured API URL; keep a local read only as a same-DB fallback.

When inbound email becomes a native ticket, OpsIQ detects the sender by calling <code>lookupCustomerById(0, ['email'=>$sender])</code> across every connector; the first match "owns" the customer and its <code>platform</code> slug is stamped on the <code>ticket.created</code> event as <code>_pipe_owner_platform</code> (empty = guest). So a WHMCS-customer email opens a ticket in WHMCS (WHMCS numbering, mirrored as one), while an unknown sender stays a native guest. <strong>If your connector mirrors native tickets onto its own platform</strong>, your <code>ticket.created</code> handler must gate on this: <code>if (array_key_exists('_pipe_owner_platform',$payload) && $payload['_pipe_owner_platform'] !== '<your-slug>') return;</code> — the key is absent on non-piped (chat/manual/AI) tickets, so those mirror as before. Per-department control lives under Team & Departments → Open tickets via email (Anyone / Customers only / Off).

The AI can perform actions through the connector: create tickets, update orders, cancel subscriptions — all with your approval through the Trust Layer.

Connectors contribute platform-specific knowledge articles to the AI. Shopify connector adds e-commerce troubleshooting; WHMCS connector adds hosting knowledge.

Some connectors register webhooks with the external platform for real-time event notifications (new orders, ticket updates, etc.).

E-commerce connectors feed revenue data into the Sales dashboard for attribution and analytics.

Look up data without changing anything. Examples: list_orders, get_customer. Safe, no confirmation needed.

Create or modify data. Examples: create_ticket, update_order. May require confirmation.

Remove data. Examples: cancel_subscription. Always require confirmation.

Declared in actions.json — generic API calls defined declaratively.

Optional per-action "capability" field in actions.json — a connector-neutral class tag (e.g. "tickets" for a ticket read/lookup, "ticket_create" for opening a ticket). OpsIQ gates the whole class uniformly across every connector: ticket reads drop out of the AI when the operator turns off AI Ticket Awareness, and ticket creation is reserved for OpsIQ's own composer (so a connector's create tool can't duplicate it). Declare it and your connector conforms — OpsIQ never needs to know your action names. The Connector Builder exposes it as a Capability dropdown per action.

Implemented in PHP in the connector class. Full control over logic.

A static key sent in a header or query parameter. Simplest method.

Token sent in the Authorization header. Common for modern APIs.

Username and password encoded in the Authorization header.

Full authorization code flow with PKCE. OpsIQ handles redirect, exchange, and refresh via OAuthHelper.

Uses offset and limit parameters. Example: ?offset=100&limit=50.

Uses page number. Example: ?page=3&per_page=50.

Uses a cursor token from the previous response.

Uses the Link response header with rel="next".

Base64 of the RAW file bytes — use for files behind auth (most inbound cases). OpsIQ decodes and re-hosts it under /opsiq/uploads/ via the universal AttachmentIngest. The most portable shape.

A public https URL (e.g. a Zendesk content_url). Must be https; passes an SSRF / allowlist check before it is stored.

A path under /opsiq/uploads/ you already wrote (what the native composer uploader produces).

Preferred — the service id exactly as it appears in your IdentityProvider::lookupCustomerServices() list (each service's id). Unambiguous match.

A platform service-code, e.g. WHMCS S396 (service 396) / D11 (domain 11). OpsIQ decomposes the optional type-letter + id and matches your service list, with a type guard so a domain code never matches a product of the same id. Expose a matching ref on each service for an exact match.

A domain name; matched as a substring against each service's detail / domain.