Add your first client

In OpsMerge, every endpoint, ticket, contract, and invoice belongs to a client. Before you can install agents, raise tickets, or send invoices, you need at least one client to attach them to.

A client is a single end-user organisation you serve — typically one legal entity, one logical "company".

Step 1 — Create the client

1. Open Clients in the left sidebar.
2. Click + New client.
3. Fill in:
   • Name — the client's company name as you'd say it. Used in tickets, invoices, and the client portal.
   • Domain — primary email domain (e.g. acmecorp.co.uk). Used to auto-match inbound email tickets to this client. Optional but strongly recommended.
   • Contact email — main email for the client. Usually the primary contact's address.
4. Click Create.

Done. The client now exists, with a default no-frills setup.

Step 2 — Add contacts

A contact is a person at the client — typically the people who'll raise tickets, log into the portal, or receive invoices.

1. From the client page, click the Contacts tab.
2. Click + New contact.
3. Fill in name, email, and (optionally) phone and job title.
4. Tick VIP if this contact gets priority handling — see VIP contacts for what that does.
5. Save.

You can add as many contacts as you like, and you can mark any of them as a Portal user to give them magic-link access to the client portal.

Bulk-import contacts from M365

If the client uses Microsoft 365 and you'll be connecting their tenant via CIPP anyway, skip the manual contact entry — the CIPP integration imports user lists for you. See Connect Microsoft 365.

Step 3 — Decide on asset grouping (optional but useful)

By default every endpoint at this client lands in one big pool. For most clients that's fine.

For bigger or geographically-spread clients, you can group endpoints into sites (e.g. "London office", "Manchester office", "Home workers"). Sites are purely organisational — they don't change billing or RMM behaviour by default — but they make searching, reporting, and policy application much easier.

To add sites: client page → Sites tab → + New site.

You can skip this and come back later — endpoints can be moved between sites at any time.

Step 4 — Set a contract (if you've got one ready)

Every billable client should have a contract in OpsMerge. A contract defines:

• What you charge them per month (recurring fee).
• What's included (e.g. unlimited support hours, 50 hours/month block, or per-asset).
• How asset counts feed into the bill.

You don't have to set a contract on day one — you can run the client on "no contract, bill ad-hoc" indefinitely. But for any client paying you a monthly fee, set the contract before the first invoice runs.

See Contracts for the model and Recurring invoices for how contracts feed billing.

Step 5 — Install the agent(s)

Now you've got a client to attach endpoints to.

• Windows
• macOS
• Linux
• MSI deployment for fleets via GPO or Intune

Generated tokens from the Add agent dialog are automatically scoped to the client whose page you launched the dialog from.

How clients differ in OpsMerge

If you've used another PSA before, OpsMerge's "client" is roughly the same concept — but a few specifics differ:

• No nested clients. A client is flat. Big enterprise structures (parent + subsidiaries) become separate clients, optionally cross-linked.
• Asset counts are live, not snapshot. Recurring billing pulls the current count of billable assets from the RMM at the moment the invoice is generated — you don't manually maintain a "seats sold" number. See Recurring invoices for proration details.
• Contacts can have multiple roles. A single contact can be a billing recipient, a portal user, a primary technical contact, and a VIP — all on the same record.

Common issues

The client appears twice / duplicates after CIPP sync. OpsMerge dedupes by name, then by domain — if the CIPP-imported name differs from your manually-entered name even slightly, you'll get two records. Merge from the client list (select both → Merge).

Email tickets don't auto-attach to this client. Check the client's domain field matches the sender's email domain exactly. The email gateway routes by domain match — see Email gateway.

Can't delete the client. Clients with associated tickets, invoices, or assets can't be deleted, only archived. Archived clients vanish from default views but their data stays.

Next

• Connect Microsoft 365 — pull users, mailboxes, and security data from M365 via CIPP.
• Install the agent on Windows — drop the agent on a real endpoint.