Contents7
A salesperson calls a customer to offer a contract extension. The customer replies, politely, that their last invoice is in dispute and that their support ticket has been waiting ten days for an answer. The salesperson had no way of knowing: the invoice lives in the billing software, the ticket in the support tool, and the CRM knows about neither.
This guide from our CRM and customer data section explains what a single customer view changes for each team, the two ways to build it, and the rule that stops it becoming a fourth source of disagreement.
In short
A single customer view shows a customer’s deals, invoices and tickets on one screen.
Every team benefits: sales, accounting, support and management read the same thing.
Two routes: an ERP covering all three, or tools connected around the CRM.
Everything rests on a shared key to recognise the same customer everywhere.
Each piece of data has a single master tool; the view shows a summary, it does not copy everything.
What we mean by a single customer view
Definition
Single customer view
The screen where you see everything the business knows about a customer, whichever tool the information came from: contacts and deals from the CRM, invoices and payments from billing, requests from support. It is also called a 360-degree customer view.
It does not require a single piece of software. It requires that everyone opening a customer’s record reads the same version of reality, at the same moment.
What it changes, team by team
- The salesperson sees, before calling, that an invoice is overdue or a ticket is open. They choose their moment, or start by fixing the problem: their relationship with the customer comes out stronger.
- Accounting knows who looks after the customer, and whom to ask why an invoice has not been paid, instead of chasing blindly.
- Support knows who they are talking to: a five-year customer, an account up for renewal, a prospect on trial.
- Management reads the revenue, unpaid invoices and incidents of a single account without reconciling three exports.
There is a less expected benefit: knowing where a person’s data is. When a customer exercises their right of access or erasure, a view that connects the tools tells you where to look. We cover that side in our guide to GDPR in a CRM.
Two routes to build it
One tool, an ERP
Contacts, quotes, invoices and tickets in the same database
No sync to maintain between tools
Changing tools affects every team at once
Tools connected around the CRM
Each team keeps the tool it knows
Connections have to be built, monitored and maintained
You move tool by tool, without changing everything at once
The ERP route
A light or full ERP puts customer relations, billing and often support in the same database. Dolibarr, for example, covers third parties, quotes, orders and invoices, and offers a ticket module to run a help desk, with a public portal for requests. Odoo offers its sales, invoicing and Helpdesk applications; check on its editions comparison which ones the edition you are considering includes, because the licence changes the total cost.
This is the right route when teams already re-enter CRM quotes into billing, and the business is ready to change tools for everyone. Our comparison to choose between Twenty, Dolibarr and Odoo starts from that question.
The connected-tools route
When billing and support work well and nobody wants to change them, you connect the tools to the CRM instead. A CRM where everything is available through an API lends itself well to that role: this is the case with Twenty, which we have run in production since early 2025, and whose use as a back office for business data we describe elsewhere. Connections go through the API, webhooks or an orchestrator such as n8n.
The shared key: recognising the same customer everywhere
A view brings nothing together if the tools do not agree on who is who. “Dupont SAS” in the CRM, “DUPONT” in billing and a personal address in support: without a shared key, that is three customers.
- For a company, its website domain or its company registration number.
- For a person, their work email address.
- For an account, a customer number created once, in a single tool, and copied into the others.
Twenty, for example, treats a person’s email and a company’s domain as unique values, according to its documentation on uniqueness constraints: data arriving with a known email updates the record instead of creating a second one. A key that is not unique produces duplicates, which our guide to cleaning your CRM data shows how to handle.
One master per piece of data
This is the rule that makes the view reliable. Each piece of information has one tool that is authoritative, and only one; the others read it.
Which tool is authoritative for what
- The CRM
Contacts, companies, deals and next actions.
- Billing
Signed quotes, invoices, payments and delays.
- Support
Tickets, their status and their history.
- The customer view
A summary of each, and the link to the source.
The view does not need to copy everything. A few fields are often enough: amount due, date of the last invoice, number of open tickets, date of the last exchange. Copying less also means less personal data in circulation, and fewer connections to monitor.
From the field
On Palmora Property, a property listings portal we operate, the Twenty CRM is authoritative: the website updates from it, through a pipeline we brought back onto our own server in July 2026, and nobody enters anything twice. The same rule applies to corrections: a first bulk repair run without rate limiting produced 754 failures; rerun with rate limiting and automatic retries, it corrected the 837 records concerned without a single failure.
Email exchanges complete the view when salespeople’s mailboxes are connected to the CRM; our guide to syncing CRM and email explains how to do it without exposing everything.
Watch out
A connection that breaks silently is worse than no connection
A view that shows “no unpaid invoices” because the sync stopped three weeks ago misleads everyone. Every connection is monitored, with an alert sent to a named person, as our guide to monitoring n8n workflows describes.
Where to start
- Write down the three questions
Your teams most often ask another department about a customer.
- Choose the shared key
And check that it exists in every tool.
- Name the master tool
For each piece of data, in writing.
- Show a summary first
Two or three useful fields, not the full copy.
- Monitor each connection
From day one.
A view that shows unpaid invoices and tickets also makes follow-ups more accurate, as we explain in our guide to sales follow-ups that keep a human tone. The rest of the section covers Twenty in production, migrating from HubSpot, why salespeople do not fill in the CRM and automated decisions.
Connections to your tools and data migration are part of our CRM and ERP offer: Twenty at €4,500, Dolibarr from €6,500, Odoo in three tiers from €15,000. To describe your current tools, write to us.
Frequently asked questions
Do you need an ERP for a single customer view?
No. An ERP puts customer relations, billing and sometimes support in the same database, which avoids syncing. But if your billing and support tools work well, connecting them to the CRM through their APIs gives the same result on screen, without changing each team’s habits. The choice depends mainly on what your teams re-enter today.
Which key should connect the tools?
For a company, its internet domain or its registration number; for a person, their work email address. The safest option is often a customer number created in a single tool and copied into the others. The key must be unique and present everywhere: a key one of the tools does not know recreates duplicates at the first import.
Should every invoice be copied into the CRM?
No, and it is even best avoided. Billing remains the master tool for invoices; the CRM only needs a summary (amount due, date of the last invoice, any delay) and a link to the source. Copying less reduces gaps between tools, the personal data in circulation and the number of connections to monitor.
How long does it take to set up?
It depends on the number of tools and the quality of the data. Connecting a billing tool to an already clean CRM is a short project; deploying an ERP that replaces three tools takes several weeks, even several months. Our offer gives the range: two weeks to 90 days depending on the solution, with the scoping phase refining it for your case.
Sources
- Dolibarr wiki: Module Ticket (new tab)wiki.dolibarr.org
- Odoo, Community and Enterprise editions comparison (new tab)odoo.com
- Twenty documentation: Uniqueness Constraints (new tab)docs.twenty.com
Jim · founder of Brain Plus AI
Also in crm and customer data
Practical guide9 min
Twenty beyond the CRM: a back office for your business data
Properties, projects, equipment, case files: Twenty can hold far more than your contacts. What it takes to make it the back office for your business data, connected to your site, and where this use stops.
Choose and price7 min
Twenty, Dolibarr or Odoo: which one for your team?
Twenty, Dolibarr and Odoo are not in the same category: a pure CRM, a light ERP, a full ERP. Rather than a feature table, here is a decision grid by team size and by process, with what moves you from one level to the next.
Practical guide7 min
CRM and email: syncing without exposing everything
Connecting mailboxes to the CRM makes customer history readable by the whole team, provided you choose what comes in and what each person sees. The settings that decide, role by role, and what email must never replace.