Support

Need help?

Most answers are already written down. For everything else, Oneop does not publish a response time — there is no SLA instrument behind one — so the fastest thing you can do is send a complete first message.

Search the help centreEmail support@oneop.ioOpen your workspace

Worth including

  • The email you log in with
  • The URL of the screen it happened on
  • What you expected, and what happened instead

Goes somewhere else

The Oneop platform

Everything your teams need.
Built to work together.

Most "all-in-one" platforms are a bundle of products with an integration between them. Oneop is one database. A conversation, the deal it created, the invoice it produced and the stock it moved are rows in the same schema, under the same tenant boundary, visible to the same roles.

Free forever · 2 seats · No credit card

One customer. Every team has the context.

  • 12Connected modules
  • 4Business areas
  • 19Native integrations
  • 68Built-in reports
  • 1Connected platform

Different teams, same business

Five people, five questions, one record between them

Every team below is looking at the same customer. Nobody is looking at a copy, and nobody had to be told what the other four already knew.

Choose a role to see the same customer from their side
Anchored · this does not change with the role
Dana KimNorthstar Commerce · dana@northstar.example
Customer #10294
Navy Hoodie · MediumNH-MED-001 · $68.00Opportunity
Available 17Live warehouse figure, not a nightly exportIn stock
Stage gate: expected close date requiredThe move to Proposal is blocked until it is setEnforced

Sales quotes against the stock figure operations is holding, so a promise made here is one the warehouse can keep.

Do you have the Navy Hoodie in medium?TKT-4581 · ResolvedConversation
ORD-2398 · ConfirmedSHP-812 · Standard · 2–4 daysOrder
SLA: business minutes, not wall clockCounted against your working days and holiday listOn track

The agent answers "where is my order" without asking for an order number, because the order is on the record the ticket already belongs to.

ORD-2398 · ConfirmedReserves 1 × NH-MED-001Order
Available 17 → 16On-hand minus reserved. The reservation is the difference.Reserved
SHP-812 · Label createdStandard · 2–4 daysFulfilment

The unit is committed the moment the order is, so nothing else in the business can sell it twice — including the salesperson looking at the panel above.

INV-1842 · Sent$73.10 · Net 14Invoice
Revenue $68.00 · Tax $5.10Sums to $73.10, the figure on the orderBalanced
Posted from the order, not re-keyedDebits equal credits or the row is refusedJournal

Finance can trace the invoice back to the order, the order back to the conversation, and the conversation back to the customer — without leaving the record.

Northstar Commerce · Customer #10294One row, four teams reading itCustomer
Conversation → order → invoiceThe same identifiers the whole way throughTraceable
68 built-in reports across 11 module packsEvery module is already a queryable datasetReporting

Nobody reconciles four exports to answer a question about one customer, because there were never four copies of the customer to reconcile.

How the twelve are organised

Four business areas, and none of them is a separate product

Customer

4 modules

Everything that happens before and around a sale: the conversation, the record it belongs to, the pipeline it becomes, and the support that follows it.

Operations

3 modules

Turning what was sold into what was delivered — stock that can be promised, work that can be scheduled, and reporting that reads the result without a spreadsheet.

Finance

1 module

One module, and it is a real double-entry ledger rather than an invoice generator. Operational transactions continue into financial records instead of being re-entered as them.

AI & Automation

4 modules

Work that moves without someone chasing the next person, and AI that acts inside published limits on the same records the rest of the platform uses.

Explore all modules

All twelve, and what each one actually does

Filter by business area or read the lot. Every module is part of the same application on the same database — the plan sets the ceiling, and a few operational modules are activated separately because they can create financial, outbound or operational side effects.

Filter the twelve modules by business area

Connected by design

The connection is a layer, not a feature

Nothing above is true because twelve teams agreed to keep their data tidy. It is true because the twelve surfaces sit on one shared context, and that context sits on one database with one boundary and one commit.

ExperienceWhere people work — twelve surfaces, not twelve products
CRMHelp deskLive chatSequencesProject managementInventory & warehouseReportingFinanceAI chatbotAI agentsAI governanceAutomation
Shared business contextThe reason there is nothing to sync
One customer recordThe person in a chat, the requester on a ticket, the buyer on a deal and the bill-to on an invoice resolve to the same rows.
One permission modelRoles and the tenant boundary are checked at the data layer, not per product.
One customization layer13 field types across 10 entity types, with required flags, defaults, role restrictions and conditional visibility.
One language layer8 fully translated UI languages, 2 of them right-to-left, reaching into rendered invoice PDFs rather than only the app chrome.
PlatformOne database, one boundary, one commit
One PostgreSQL schema329 tables. 275 carry a tenant ID.
One tenant boundaryEnforced on every query at the data layer.
One transactionA stock decrement and its ledger posting commit together or not at all.
One metered AI pathEvery model call is charged to a named workspace before it runs. Refusal at the cap is a switch.

Connections

Nineteen integrations, grouped by the job they do

The twelve modules do not need integrations between themselves. These are for the software you are keeping — every one exists in the product and is verified against the code that runs it.

Credentials encrypted per workspace · webhooks signature-verified and fail-closedAll nineteen, in detail →

FAQ

Common questions about the module set

How many products am I actually buying?

One. Oneop is a single application with twelve module surfaces on one database, priced flat per workspace rather than per module. There is no per-module SKU and no connector to license between them.

Do I have to use all twelve modules?

No. All twelve are surfaces of one application on one database, so ignore the ones you don't need — nothing is priced or licensed per module. Some operational modules, finance, project management and sequences among them, are activated separately because they can create financial, outbound or operational side effects. Beyond that what varies is the plan entitlement, not whether you bought a module.

What does "one record" actually mean in practice?

That the person in a chat, the requester on a ticket, the buyer on a deal and the bill-to on an invoice are the same rows, not four copies kept in step by a sync job. Oneop stores every module in one PostgreSQL schema of 329 tables, 275 of which carry a tenant ID enforced at the data layer on every query. When a sales order ships, the stock decrement and the ledger posting happen inside the same database transaction — either both or neither.

Which parts are genuinely AI?

Chatbot flows, AI agents, AI reply drafts, ticket triage on existing tickets, document OCR, expense categorization and the Business-plan report narrator are real model calls through Google Gemini. Cash-flow forecasting, duplicate-bill detection and the analytics insights panel are deterministic calculations and we don't call them AI. AI governance explains how every model call is bounded.

What actually varies by plan?

The ceiling, not the switch. Invoicing runs on every tier, while payables, expenses, tax and bank reconciliation start at Pro, and multi-currency at Business. Most plan limits show up in your navigation rather than a server refusal, and Free plan numeric caps are not hard stops — we would rather say so than let you infer a wall that is not there. The report builder, dashboards, scheduled delivery and AI reporting are the exception: those gates are checked server-side.

Can I add my own fields?

Yes. Thirteen field types across ten entity types, with required flags, defaults, filtering, role restrictions, grouping, ordering and conditional visibility. Deleting a field hides it rather than destroying its history, so a report run against last quarter still resolves.

Does it work in my language?

Eight fully translated UI languages — Arabic, German, English, Spanish, French, Turkish, Urdu and Simplified Chinese — with full right-to-left layout for Arabic and Urdu that reaches into the rendered invoice PDFs, not only the app chrome.

Does it connect to what we already run?

Nineteen native integrations, each with a verified entry in the product rather than a logo on a page. Credentials are encrypted per workspace and inbound webhooks are signature-verified and fail closed — an unverifiable payload is rejected, not processed on trust.

Get started

Start with one problem. Build toward one connected business.

Two seats on the free plan, or a guided tour of the modules you care about.

Free forever · 2 seats · No credit card