A CRM is useful when it reflects a clear process. If the team has not agreed on statuses and responsibilities, buying a tool will not solve the organisational problem.
Define the minimum record
An enquiry needs contact details, topic, owner, current status and next action. Add fields only if they help with the task. Do not turn the record into a store of all the customer's personal information.
Agree on the transitions between statuses
Describe what a new, clarifying, agreed and completed enquiry means. Specify who changes the status and on what basis. Check the choice of service, access rights and data processing against how the team actually works.
How to agree on what statuses mean
Describe each status through an observable event. “New” means a registered enquiry that has not yet been reviewed; the next status should show who is acting and what is being waited for. Do not use “in progress” for every open record if it does not tell you what to do. When waiting for a reply, set a date to check. Distinguish between a completed service, a refusal and an unsuitable enquiry. Agreed definitions are more useful than a complex scheme that each employee interprets differently. They make reports and handovers clear without extra explanations.
How to test a record when handing it over to a colleague
Ask a team member who is not handling the enquiry to open the record and explain its current state and the next step. If they need to ask questions in a private chat, add the missing working information. Do not turn the record into a complete customer archive: links and access should match the task. Check that the new owner has actually been notified and can open the necessary materials. Review access when someone stops working on a project. A CRM should preserve the history of the company's actions, not depend on one person's memory or personal account.
What to check
- Assign an owner to every enquiry.
- Do not leave an active record without a next action.
- Distinguish between reasons for closing.
- Review access rights after changes to the team.
The minimum enquiry record
Start with a small set of data and update rules. Add fields when a specific working need arises, not to make reports bigger.
| Field | What to store | Rule |
|---|---|---|
| Enquiry | Short topic and source | Each enquiry has a clear history |
| Owner | The person handling the next step | No active record is left without an owner |
| Status | Who needs to act now | The meaning is the same for the whole team |
| Next action | A specific task and date | Waiting also has a date to check |
| Materials | Links to the necessary set | No excessive access to personal data |
| Closure | Reason for closing | A completed order is distinguished from a refusal |
Example situation
The status “in progress” hides everything. It is more useful to see whether the team is waiting for the customer's reply or has to send an offer itself.
Next step
Start your CRM with the rules of the process, and only then automate repetitive actions.
Official information on this topic
Checklists and examples are organisational recommendations. Requirements depend on the procedure, the city and your situation; check them with the relevant office before you act. Please discuss legal and tax questions with an authorised professional.
This article was prepared with the help of AI. The example illustrates the approach and does not describe a client case.