SAM - customer system of record

One customer record.
Not three copies of one.

Sales, marketing and service all work the same accounts and contacts. Orders, shipments, loans and assets are read live from the systems that own them. Turn on the modules you buy. None of them keeps its own copy of the customer.

Request a walkthrough All systems of record

What is shared ›

Two colleagues reviewing customer information together at a desk — One account, one timeline, every module.

Three modules, one core

Buy the module. Share the customer.

Turn on what you need. What you never get is a second copy of your own customer list. Accounts, contacts and the activity history are kept once and used by every module you switch on.

Sales

Pipeline

Leads, deals, pipelines, quotes, RFPs, forecasts and targets. All on the same accounts and contacts the rest of the system uses.

Marketing

Demand

Products, launches, promotions, creative, campaigns and spend. Conversions, attribution, web analytics and lead forms all feed the same record.

Service

Support

Cases, SLAs, queues, a knowledge base, satisfaction scores and contact-centre channels. This one is next.

Next on the shared core

The shared core

Kept once, used by everything.

A “single view of the customer” built by syncing three databases is not a single view. It is three views and a nightly job. These are kept once, in the middle, and every module reads them directly.

Accounts and contacts

One set of accounts and contacts, with your own fields, used by every module. No module keeps its own copy. That is the whole point.

One activity timeline

Calls, emails, meetings, chats, notes and tasks all land on the record. The history of a relationship stops being split across three tools.

Agents, queues and routing

Who works what, and in what order, set once and shared. Each module does not invent its own rules.

Channels in, evidence kept

Email, website chat and forms today, with voice, SMS and messaging to come. Each one lands on the customer record.

What it refuses to own

A smaller CRM, on purpose.

Most CRM suites grow by swallowing the systems next door, and each one adds another copy of data somebody already owns. We went the other way. SAM owns the customer and the conversation, and reads everything else from wherever it actually lives.

The needOwned byHow SAM uses it

Sign-in, roles and permissionsICERoles are set once for everything. SAM issues no logins of its own.

Decisions, routing rules, automation, chat hostingArinRules and workflows run over SAM's tools, not buried inside it.

Mailbox, calendar, telephony, messagingConnectorsIntegrated once, then the activity shows up here.

Agent shifts and availabilityHRMSRead, never copied. The HR record stays the HR record.

Orders, shipments, loans, patients, assetsRMS · TMS · LMS · HMS · EAMLinked on a case or deal and read live. Never duplicated.

Explicitly out of scope

Running a carrier or PBXWorkforce forecasting and schedulingField service dispatch and asset maintenanceThe order, billing or ledger records of another system

Campaigns you can audit

A running campaign keeps the rules it started with.

Playbooks come as templates, and your copy is yours. Editing one saves a new version, and a campaign already running keeps the version it started on. So attribution still points at the rules that were in force when you spent the money.

Products, launches, promotions, creative and spend on one record
Conversions, attribution, web analytics and lead forms feed the same accounts
An edit makes a new version. It never quietly rewrites a live campaign

A marketing team working at desks in an open-plan office — Versioned rules, traceable attribution.

Where the automation lives

The rules are not buried in the CRM.

Routing, escalation and automation live in Arin, not as scripts inside a CRM that only a CRM admin can read. And because the customer record, the order and the shipment are all reachable the same way, one rule can work across all three.

A deal or case links to orders, shipments, loans and assets, and reads them live
Mailbox, calendar and phone are integrated once, then show up as activity
Agent shifts and availability come from the HR record, never a copy

An abstract network of connected nodes — One decision model, every record it needs.

SAM in the customer stack

Who owns the customer.

SAM owns the customer and every conversation with them. Sign-in, HR, phone systems and other ledgers stay where they already are.

	SAM	CRM suites	Point tools
What it is	The customer system of record for an agentic stack	A broad CRM owning its own copy of most things	A sales, marketing or helpdesk tool solving one slice
The customer record	One set of accounts and contacts; no module keeps a copy	One model, usually with per-cloud duplication underneath	Its own contacts, synced to everyone else's
Operational data	Orders, shipments, loans and assets referenced by id and read live	Replicated in through integration jobs	Usually absent, or a stale sync
Automation	Decision models and workflows in Arin, over scope-gated tools	Built-in workflow builder and scripting	Webhooks and third-party automation
Boundary	Refuses to own identity, workforce, telephony or another system's ledger	Expands to own adjacent domains	Owns its slice only

One customer record.Not three copies of one.