One customer record, and what a rep does with it
What a salesperson actually sees when a OneHash record opens — last quote, open invoice, unresolved ticket — and how it changes the call.
The phone rings, a name appears, and you have about eleven seconds before you have to say something. Everything a CRM is worth comes down to what is on the screen in those eleven seconds. “Centralised customer data” describes the plumbing; this article is about the screen.
What is on the record
Open an account in OneHash CRM and you are not looking at a contact card. You are looking at the last quote you sent and what it was priced from, the orders that quote became, the invoice that is nineteen days overdue, a support ticket someone opened three weeks ago and nobody closed, a field visit a colleague checked into from their phone last month, and whether this person opened your last two emails.
Why that changes the call
Because you now do not open with “how can I help you today?” to a customer whose ticket has been sitting unanswered for three weeks. You open by mentioning it. That single change — not asking a question the system already answered — is what personalisation actually means in a business sale. The first names in email templates are decoration.
It also changes the negotiation. Knowing you quoted this buyer eleven months ago, and at what price, and that they went with someone else, is worth more than any amount of demographic segmentation. So is knowing that the invoice is overdue before you offer a discount on the next order.
The objection: nobody updates the record
This is the honest counter-argument, and it defeats most CRM rollouts. A 360-degree view assembled by asking salespeople to do data entry after every call will be half-empty within a month, and a half-empty record is worse than none because people stop trusting it.
The answer is that most of what makes a record useful should never be typed. Leads arrive from web forms, email, calls and campaigns into one queue by capture, not by transcription. Quotes and orders write themselves onto the account because that is where they were raised. Tickets attach because the helpdesk sits on the same record. Field visits log from the phone, geo-tagged, at the door. What a rep types is the part only a human knows — what the buyer actually said.
The pipeline is the same argument, one level up
A manager opening the pipeline wants the equivalent of those eleven seconds: which deals have not moved in three weeks, and who is behind on plan. Stages you defined yourself make that readable, because “stalled at sample stage” means something in your business and “stalled at Negotiation” usually does not.
Automated follow-up reminders do the rest. Most deals go quiet rather than being lost, and the reminder is the difference between noticing that in week two and noticing it in the quarterly review.
Who sees which record
The flipside of putting everything on one record is that everything is on one record. Roles, permissions and approval chains you set yourself decide who sees what: a rep sees their own pipeline, a finance lead sees the numbers, and neither has to ask the other. What OneHash does with the data itself, and what you can ask it to delete, is in the privacy policy.
Open the live demo, load one real customer, and see whether the record tells you something you would have had to ask for. That is the whole test. Pricing is on the pricing page.