Know · GrowthOps
Customer info lives in ten different places
The email is in one inbox, the quote in a folder, the invoice in accounting. Why customer facts scatter, and how one record per person pulls them together.
Starts on Hue Pro · $350 a month
In your words
A customer calls and asks where her order is. To answer, I check the shared inbox for her last email, the quoting spreadsheet for the price we gave, the accounting software for whether the deposit came in, and then I text the technician. Four screens and a text message to answer one question.
When the person who usually handles her account is on holiday, nobody knows that she prefers French, that she complained about the last delivery, or that she has a second site in another town. All of it is written down somewhere. Just not anywhere we can see at once.
Why it happens
Every tool a growing company adds solves one job well and keeps its own list of customers: the inbox has addresses, the accounting software has billing names, the field app has job sites, the phone has numbers. Nobody decided to scatter the customer; each purchase was reasonable on its own.
The lists also disagree about who the customer is. The same company is “Groupe Morin inc.” in accounting, “Morin” in the CRM and an email address in the inbox, so even a careful person cannot be sure two records are the same account. Without a shared key, the pieces stay apart.
What it costs
Every customer question costs several minutes of searching, and the answer depends on who is at the desk. Customers notice when they have to repeat themselves, and they notice even more when a promise made by one person is unknown to the next.
It also blinds the owner. You cannot see which accounts are growing, which are slipping, or which complaint is about to cost you a contract, because no single place holds the whole story of a customer.
How Humonix fixes it
01Agent
One list of people
People in your workspace gathers everyone you deal with: contacts in your customer records, people on your CRM deals, inbound requests and outbound replies. Records that share an email are one person; without an email, the company and name decide.
02Agent
One timeline per person
A person’s page shows, in order, their requests, calls, messages, quotes, jobs, invoices and payments, deals, your team’s notes and the decisions on your ledger tied to them or their company.
03Agent
Every module writes to it
Hue’s conversations, quotes, jobs and invoices land on the same record as they happen, so the timeline fills itself instead of waiting for someone to copy it in.
04Agent
Your other tools stay connected
Your CRM, accounting and field-service systems keep running; their customers come in through the connectors, and your own systems can read the record back through the API, webhooks or MCP.
01Agent
The department
This is Know, the one record under the six departments, included in every plan. GrowthOps keeps it clean each week and proposes merges when the same customer appears twice.
02Hue
Hue’s part
Hue reads the same record when it answers, so your team can ask “what does Morin owe us, and which quotes are still open?” and get the answer with the records it came from. What each person may see follows their role.
03You
Your yes
Merging two records is never automatic: a person approves it after seeing what moves, and the merge is on the ledger. Nothing is deleted; the merged record is kept as history.
What you see
Inbox: requests from chat, forms, calls and texts in one list, written to the same record the rest of the workspace reads.
Where to start
Hue Pro
Hue on your site without the badge: chat, forms, texts and calls in one record, AI answers checked every week. Month to month.
Questions
Do we have to stop using our CRM or accounting software?
No. They stay where they are. The record reads from them through connectors or an import, and every module writes the new activity in one place.
How do you know two records are the same person?
A shared email address first; otherwise the company and the person’s name, with accents, punctuation and words like “inc.” removed. When it is unclear, a merge is proposed for a person to decide.
Who on our team sees what?
Each person sees what their role allows. An owner sets the roles; invoices and revenue, for example, only show to people whose role includes them.
Where is the data kept?
In your own workspace, hosted in North America (Toronto by default), separate from every other company’s.