Before OperasAI, checking how the business was doing meant opening separate spreadsheets, a payments dashboard, and maybe a notebook for tasks. The Dashboard collapses all of that into one screen you can read in a few seconds.

It answers the question every owner asks first thing in the morning: how are we doing, and is anything broken?

Stat cards across the top show the numbers that matter most: total sales, order count, revenue, and similar metrics, each with a small delta showing how it moved compared to the previous period, so you instantly know if things are trending up or down.

An activity feed lists what just happened in the business, newest first: new orders, paid invoices, new tickets, and so on.

The figures are computed live from your actual data (sales, orders, invoices) every time you load the page, so nothing here is a stale cached report.

The "Ask OperasAI" bar at the top is a real text input, not just a shortcut. Type a question or instruction and press enter, and it takes you straight into AI Chat with your text already filled in, ready to send.

Most business software makes you click through several screens to find one number. AI Chat lets you just ask, in plain language, and get an answer, or have the assistant do the multi-step work for you.

It's the one place in OperasAI where the AI can act, not just answer: it reads your data, uses connected integrations as tools, and remembers facts for later.

Every message you send can trigger the assistant to call internal tools, for example looking up a customer's order history, searching the Knowledge Base, or pulling recent Gmail messages, before it replies, so its answers are grounded in your real data rather than guesses.

You can attach up to two files to a message, and the assistant reads their contents as part of answering.

When the assistant learns something useful about a customer during a conversation, such as a preference or a detail worth remembering, it automatically saves it as a memory note. These appear on that customer's detail page and inside the Knowledge Base, and can be deleted individually if they're no longer accurate.

Quick lookups (what did customer X order last month), drafting content (emails, campaign copy, support replies), and cross-tool questions that would otherwise take several clicks (summarize today's Shopify orders and flag anything over $200).

Start a fresh conversation any time with the New Chat button. Older conversations stay saved and accessible.

Not every sale needs a full Order with line items, stock and fulfillment. Sometimes you just need to log that $50 came in from a walk-in customer. Sales is built for exactly that: a quick, no-friction way to record revenue.

A sale has an amount, an optional link to a customer record (so it counts toward that customer's history), and an optional source label, such as walk-in, referral or website, so you can later see where revenue is coming from.

Sales feed directly into the revenue numbers shown on the Dashboard and in Finance.

Any sale can be deleted if it was entered by mistake, and the deletion is logged in the Audit Log.

Once a storefront integration like Shopify, WooCommerce, TikTok Shop, or a Facebook or Instagram Shop is connected, its completed orders show up here too, each carrying a badge for the channel it came from, so a sale from Shopify never gets mixed up with one from TikTok Shop.

A sale only appears once the matching order is actually completed, not while it's still pending or processing, and its revenue is counted exactly once, through the matching Order, so connecting several channels at once never inflates your numbers.

Once a business has more than a handful of customers, you need somewhere to answer who this person is and what your history with them looks like, without digging through old emails or invoices.

Opening a customer takes you to their detail page: every order, invoice and support ticket they've ever had, plus their lifetime value, in one scrollable view.

The AI's memory notes about that customer, things it picked up during chat conversations, also appear here and can be removed if they're outdated or wrong.

If you sell physical goods, you need a single source of truth for what you sell, what it costs, and how much you have left. Without it, Orders has nothing to pull from and you can't tell when you're about to run out.

Each product has a name, SKU, price, current stock quantity, and a reorder threshold. When stock falls at or below that threshold, the product is flagged as low stock, which is also what the Workflows low-stock trigger watches for.

Placing an order reserves stock from the product. Cancelling, refunding or deleting that order releases the stock back.

A forecast panel estimates how much of each product you're likely to need going forward, based on past order activity, so you can restock ahead of time instead of reacting after you've already run out.

Connecting Shopify, WooCommerce or TikTok Shop keeps your catalog here in sync automatically: name, SKU, price and stock quantity refresh every five minutes, with each synced product carrying a badge showing which store it came from.

This is also what lets a synced order show a real line-by-line breakdown instead of a generic placeholder, since each item in that order can now be matched back to an actual product here.

A Sale is a single number. An Order is a full transaction: multiple products, quantities, a customer, and a status that changes as the order moves through fulfillment. Orders is for anything beyond a single flat amount.

Build an order by adding one or more products with quantities and a customer. Placing it reserves that quantity of stock from each product.

Status moves through Pending, Processing and Completed in the normal flow, or can be set to Cancelled or Refunded at any point. Both of the latter automatically restore the stock that was reserved.

Deleting an order also restores its reserved stock, unless it was already Cancelled or Refunded, since that stock was already given back.

Orders placed on a connected Shopify, WooCommerce, TikTok Shop, or Facebook or Instagram Shop show up here on their own, polled in every five minutes, so you never have to re-enter what already happened on the storefront itself.

Each synced order carries a badge naming its channel and keeps its status live: if it moves from pending to paid on the storefront, the next sync updates it here too. Manually created orders are unaffected and keep working exactly as before.

An order records what was sold. An invoice is the actual bill you send to get paid for it, and not everything you invoice for started as an order: services, custom work and retainers often don't.

Create an invoice from an existing order (it inherits the amount and customer), or start one from scratch for any amount and description.

Generate a payment link you can send directly to the customer, and track its status as it moves: Draft, Sent, Paid, Overdue if it passes its due date unpaid, or Void if it's cancelled.

The payment link is created through whichever payment provider your business has connected under Settings → Integrations — Stripe if it's connected, otherwise Paddle. If neither is connected, connect one first.

Invoices can be deleted without affecting the order they were created from.

Revenue alone doesn't tell you if the business is healthy. You need to see what's going out too, which is why Finance pairs expense tracking with the revenue already captured by Sales, Orders and Invoices.

Log an expense with a category such as rent, supplies or payroll, an amount, and an optional note.

The summary panel at the top combines this with revenue data to show total revenue, total expenses, and profit for the period at a glance.

Any expense entry can be deleted at any time.

Assignments only mean something if there's a real list of people to assign to. Employees gives Projects and Support a shared directory instead of each one keeping its own, so a name means the same person everywhere in the app.

A simple list of people on your team with their basic details. Once an employee exists here, you can assign them to Project tasks and Support tickets so ownership is clear.

There's no separate login or permissions tied to an employee record by itself; that's handled under Settings, Users for people who need access to OperasAI.

Uploads happen in several different places in the app, such as a chat attachment or a shared document. Without a central library, each one would only be reachable from wherever it was first uploaded.

Anything uploaded elsewhere in the app, such as a file attached to an AI Chat message, lands here automatically, so there's always one place to find a document again instead of hunting back through old conversations.

Files here can also be referenced by the AI assistant when relevant, since it has access to the same library.

Running a business isn't only sales and support; there's internal work too, like launching a new product line, redesigning a page, or onboarding a hire. Projects gives that work a home with visible progress.

Create a project, then break it into tasks. Each task sits in one of three columns, To Do, In Progress or Done, and moves across the board as work progresses.

Tasks can carry a priority of Low, Medium or High, and be assigned to an employee so ownership is clear.

Deleting a project unassigns its tasks rather than deleting them, so the work itself isn't lost. Individual tasks can be deleted directly.

Tasks and tickets are great for tracking status, but they don't answer what's happening today or this week. Calendar gives the business a time-based view instead of a status-based one.

Shows upcoming and past events in a single calendar view, so time-bound work doesn't get lost in a list. Switch between the time periods you need to see what's scheduled at a glance.

When scheduling a meeting, set it to repeat daily, weekly or monthly up to a chosen end date, and OperasAI creates every occurrence up front rather than making you add each one by hand.

Each occurrence can be cancelled individually, or you can cancel the whole series (every upcoming occurrence) in one action from any occurrence in it.

Add a reminder to a meeting (10 minutes, 30 minutes, 1 hour or 1 day before it starts) and OperasAI notifies every attendee, plus whoever created it, at the right time automatically.

Customer questions and complaints need to be tracked somewhere that isn't a shared inbox, so nothing falls through the cracks and you can see what's still open at a glance.

A ticket carries a status (Open, In Progress, Resolved, Closed) and a priority (Low, Medium, High, Urgent). Filter pills at the top show a live count of tickets in each status.

Opening a ticket shows the full conversation and lets you reply to the customer directly from the detail panel.

Tickets can be deleted once they're no longer needed, with a confirmation step first.

Reaching customers at scale, a sale announcement, a restock notice, a seasonal promotion, needs somewhere to be drafted, tracked and sent from, rather than being handled one-off through personal email or a phone.

Draft a campaign by picking a channel, Email or SMS, writing a subject line for email, and a message, then sending it.

Campaign status tracks the send: Draft while you're working on it, Sending while it goes out, Sent once it's delivered, or Failed if something went wrong.

A campaign can be deleted before or after sending if you no longer need the record.

A single day's numbers rarely tell the full story. Growth, seasonality and the effect of a change you made last month only show up when you can look back over time, which is what Reports is built for.

Where the Dashboard gives you today's snapshot, Reports is built for looking at trends over time across sales, orders and customers, useful for spotting patterns the daily view won't show, like a slow decline that's invisible day to day but obvious over a month.

Two interactive charts show your revenue and order count for each of the last 30 days, combining both Sales and Orders into one daily total. Hover anywhere on either chart to see the exact figure for that day.

The total for the period is shown above each chart, so you get the 30-day sum at a glance as well as the day-by-day shape of it.

Some things should happen every single time without you remembering to do them, like notifying someone when stock runs low, or firing off an action the moment a new order comes in. Workflows handles that so nothing depends on a human noticing in time.

A workflow pairs one trigger, such as low stock, a new order, or a new support ticket, with one or more actions that run automatically when that trigger fires.

Each workflow can be toggled active or inactive without deleting it, which is useful for pausing something temporarily.

Every run is logged with a status of Success, Partial or Failed, so you can see exactly what happened and debug anything that didn't fire correctly.

For AI Chat to give accurate answers about your business, it needs a trustworthy source of truth. The Knowledge Base is that source, and it's deliberately separate from whatever the AI happens to pick up in conversation.

Every article has a status: Draft, Published or Archived, set from the editor. The AI's knowledge-base search tool only ever reads Published articles, so a Draft stays private and won't influence the assistant's answers until you publish it.

Below the articles, a "Saved from chat" section lists memory notes: facts the AI picked up automatically during conversations. These are kept for reference and can be deleted individually if they're wrong or no longer relevant.

Your business data doesn't all live inside OperasAI. Some of it sits in Gmail, Shopify, Stripe, or a dozen other tools. Integrations lets the AI see and use that data too, instead of being blind to everything outside this app.

Found under Settings, Integrations. Each card shows whether it's connected and lets you connect or disconnect.

Most providers use a simple paste-your-credentials flow (an API key or access token you copy from that provider's own dashboard). Gmail, Outlook, Google Drive and Google Analytics instead use a secure OAuth sign-in, the same kind of "Continue with Google" flow you see on other apps, so you never have to hand OperasAI a password.

Once connected, the AI can use that integration as a tool in chat, so a question like "any unread emails from suppliers" or "how did yesterday's Shopify orders look" gets answered from your real, live account rather than requiring you to go check it yourself.

You connect it the same way you'd sign into any app with Google: a secure OAuth popup where you grant OperasAI read access to your mail, no password ever typed into OperasAI itself.

Once connected, the AI can read and summarize your inbox on request, for example pulling unread messages from a specific sender, summarizing what came in overnight, or checking whether a particular supplier has replied yet.

Connected through a Microsoft OAuth sign-in, the same secure pattern as Gmail. Once linked, the AI can read and summarize recent emails on request, exactly like the Gmail integration.

Connected through the same Google OAuth sign-in as Gmail. Once linked, the AI can list and look up files in your Drive, useful for a request like "find the contract I saved last week" without having to open Drive and search yourself.

Connected through Google OAuth, scoped specifically to one GA4 property you choose during setup, so the AI only ever sees the site you intended to connect. Once linked, you can ask things like "how did website traffic look this week" directly in chat and get a real answer from your actual Analytics data.

Connected by pasting a store access token you generate from your own Shopify admin panel, rather than an OAuth sign-in. Once connected, the AI can pull recent orders, so a question like "how did today's sales look" is answered straight from Shopify without opening its dashboard.

A background sync also runs every five minutes, pulling your Shopify products and orders into Products, Orders and, once an order is marked paid, Sales, each tagged with a Shopify badge so you can tell them apart from orders entered by hand or from another connected channel.

Connected by pasting a REST API consumer key and secret, generated from your own WordPress site's WooCommerce settings page. Once verified, it behaves just like Shopify: the AI can pull recent orders whenever you ask, and the same five-minute background sync keeps Products, Orders and Sales up to date automatically, tagged with a WooCommerce badge.

Connected by pasting a Stripe API key from your Stripe dashboard. Once connected, the AI has visibility into payments and charges, useful for quick questions about revenue or about a specific transaction without logging into Stripe.

Connected by pasting a Paddle API key from your Paddle dashboard. If both Stripe and Paddle are connected, invoice payment links are created through Stripe first; Paddle is used when Stripe isn't connected.

Connected by pasting your PayPal app's client ID and secret, which PayPal issues once you register an app in their developer dashboard. Once connected, the AI can pull recent PayPal transactions when asked.

Connected by pasting your Facebook Page ID and a page access token, both generated from Facebook's own developer tools for your Page. Once connected, the AI can pull recent posts from your business Page, useful for reviewing what's already gone out without opening Facebook.

If your Page also has an approved Facebook Shop with checkout handled on Facebook itself, the same five-minute sync used for Shopify pulls its catalog and orders into Products, Orders and Sales too. A Page without a Shop set up this way simply has nothing to sync, which is normal.

Connected by pasting your Instagram Business account ID and an access token, the same pattern as Facebook. Once connected, the AI can pull recent media from your account on request.

Instagram Shopping shares its catalog with the linked Facebook Page's Commerce setup, so the same sync condition applies: an approved Shop is what makes products and orders sync into Products, Orders and Sales, tagged with an Instagram badge.

Connects your WhatsApp Business presence to OperasAI, so conversations and messages flow into the same place as your other channels instead of living only in the WhatsApp app itself, making them part of the same history the AI and your team can reference.

This one works differently from the other paste-your-credentials providers. TikTok's Partner API requires one platform-level app registered with TikTok Shop's Partner Center; a single business cannot generate its own API key the way it can on Shopify or WooCommerce. Once that platform app is in place, you connect through a sign-in flow, the same shape as Gmail, and the AI can then pull recent TikTok Shop orders.

Once connected, the same five-minute background sync used for Shopify and WooCommerce pulls TikTok Shop's products and orders into Products, Orders and Sales, tagged with a TikTok Shop badge.

An assistant with access to real business data needs boundaries that are explicit, not assumed. AI Settings is where you set those boundaries rather than leaving them hard-coded.

Found under Settings, AI. This is where you tune the assistant's behavior and what data and tools it's allowed to use when answering questions in AI Chat, so its access matches what you're actually comfortable with.

Company holds your business profile. Users controls who has access to your OperasAI account and what role each person has.

From Settings, Users you can invite someone by email. They get an invite link that either creates their account or, if they already have one, lets them sign in and join with one click.

Roles control what a member can actually do. Every business starts with an Owner role that can do everything, and you can create more roles, such as Sales or Support, each with its own set of permissions covering areas like sales and orders, finance, products, projects, support, marketing, the knowledge base, workflows, billing, developer tools and team management.

A member's role can be changed, or the member removed, at any time from the same page. Someone without the right permission for an action simply won't be able to do it, both in the interface and if they try the underlying API directly.

A new account starts on a 14-day free trial with its own working, if modest, limits (a couple of team seats, 50 AI Chat messages a month, and so on), so there's no credit card wall before you can actually see whether OperasAI fits how you work.

Three days before the trial ends, a banner on the Dashboard gives you the heads-up. If it does end without a plan chosen, the account isn't deleted or touched: it's simply paused until you pick one, and everything, from your data to how far you'd gotten through this month's usage, picks up exactly where it left off the moment you do.

Every plan includes every feature and every tab; what changes between Starter, Growth and Business is how much of each you get; things like AI Chat messages a month, team seats, orders a month, and storage, shown side by side on the pricing page and again here under Settings, Billing.

Hitting a limit doesn't lock you out of what you've already built: existing data stays fully visible, and only the specific action that would exceed the limit, like sending one more AI Chat message this month, is blocked with a message telling you exactly what to upgrade for.

Developer tools and the full Audit Log search are the two things reserved for the Business plan specifically, since they're aimed at larger, more technical teams rather than every business. Both tabs stay visible on every plan; opening one on Starter or Growth shows what it does and a button to upgrade, rather than hiding it entirely.

API Keys let you call the OperasAI public API from your own scripts or external tools. Generate a named key, then use it to authenticate requests instead of logging in as a user.

Webhooks do the reverse: give OperasAI a URL, and it will send a signed POST request to it whenever something happens, such as a new sale, a new order, or a paid invoice, so you can verify it's genuinely from OperasAI.

This tab, along with the full Audit Log search below, is only usable on the Business plan, described above.

A complete history of who changed what across the account. Every create and delete action anywhere in OperasAI is recorded here, including the user, the entity, and when it happened.

A short version of this, recent activity only, also appears right on the Dashboard for every plan; searching and filtering the full history here by action, entity or date range is the part reserved for Business.

Mistakes happen: a duplicate order, a test entry, a campaign that should never have been drafted. Every entity that can be created needs a matching, equally easy way to undo that, instead of leaving incorrect data stuck in the system forever.

Sales, orders, invoices, expenses, projects, tasks, campaigns, tickets, products and knowledge base articles all have a delete action next to them.

Every delete asks for confirmation first through a styled dialog, so nothing is ever removed from a single accidental click.

Deleting an order that wasn't already cancelled or refunded correctly restores any stock it had reserved, and every deletion is written to the Audit Log so there's always a record of who removed what and when.