What is CRM? How customer records, sales and follow-up fit together

01

Start with the questions a customer record should answer

A useful record explains who the customer is, which company they belong to, who owns the relationship and what was discussed most recently. Start with information your team actually uses. Requiring many fields does not automatically make a record helpful. A service team may need an agreed scope, while a salesperson needs a follow-up date. Both should be able to understand the relationship without asking the customer to repeat the entire history. Review fields that are collected but never used in a decision or task.

02

Keep contacts, opportunities and tasks distinct

A contact represents a person. An opportunity represents a possible piece of business. A task represents a specific next action. One company can have several people and several open opportunities with different values and decision dates. Storing everything in a contact note mixes these meanings. Creating an opportunity for every conversation can also misrepresent the pipeline. Agree when an opportunity should be opened, then assign a concrete follow-up task with an owner and a date. Use the relationship between these records instead of making one record carry every purpose.

03

Walk through a service-team example

Imagine an illustrative design team receiving an inquiry about a website. The company and contact are recorded, the needs discussion is summarized, and a website opportunity is created. A task is assigned to clarify the scope. If the customer later asks about ongoing maintenance, that second need can be evaluated separately. This is a working example, not a customer reference or an outcome claim. The important check is whether a colleague can take over the conversation with enough context to prepare properly, rather than asking for the same information again.

04

Agree a small set of working rules

Decide who can create records, how company names are written and who reviews possible duplicates. Then define what counts as a completed task and when a sales stage should change. Try these rules on a small set of illustrative records before importing everything. A system that asks people to enter information without making daily work clearer is likely to become stale. Begin with one handover that the team can complete consistently. Make the owner of the process visible so that future questions have somewhere to go.

05

Check the features available in Hubz

Hubz contact and company records and basic opportunity tracking provide a starting point for customer context and follow-up. Product catalogs, quote preparation and contracts belong to Professional and Business in the published package descriptions. Choose a package for the tasks your team needs to complete, as well as the number of records it must hold. Use illustrative information when reviewing the workflow. The first goal can be a well-prepared next conversation rather than an immediate transfer of every historic file. Review the detailed module guide before making assumptions about access.

06

Try it with your team

Ask one colleague to create an illustrative customer and another to take over the conversation. The second person should explain the company relationship, open need and next task without asking the creator to retell the history. Note which information was difficult to find. Change the record convention where that helps the handover, rather than adding fields simply because the software permits them. Repeat the exercise with a second piece of work for the same company to check that the two opportunities remain distinct.

Frequently asked questions