The CRM features that matter, and the job each one does

What counts as a CRM feature?

A CRM feature is a job somebody in the business would otherwise do by hand. That is the only useful way to read a list of them, and it gets easier once you have settled what CRM is and what a company does with one. A checkbox on a comparison grid is not a feature. Storing a phone number is not a feature either. Making sure everyone who calls that number sees the same history is.

The nineteen below appear, under different names, in nearly every product on the market. None of them belongs to one vendor. What differs is how much configuration each takes before it works, which plan it starts on, and whether it exists today or is a line on a roadmap.

The seven groups at a glance

Nineteen items is too many to hold in your head, so they group into seven jobs. Read the group first, then the items inside it. If a group does not describe work your business does, you can skip four features at once.

Group	Features	The question it answers
Records	1–3: accounts and contacts, leads, custom fields and objects	Who is this, and what do we already know?
Pipeline	4–7: deals and stages, multiple pipelines, activities, forecasting	What is in play, and what happens next?
Quoting	8–11: catalog and price books, quotes, approvals, contracts	What did we offer, at what price, approved by whom?
Communication	12–13: email sync, messaging channels	What was said, and can anyone else see it?
Automation	14–15: workflow rules, assignment and routing	What should happen without anyone remembering it?
Reporting	16–17: reports and dashboards, AI	What was true this month, and what do we do about it?
Administration	18–19: permissions and audit, integrations and API	Who can see what, and what else does this connect to?

The 19 features, one by one

Each one is described as the job it does and what to look at when you compare products. The order runs from the record outward: what you store, what you do with it, what you send, what you say, what runs by itself, what you read afterward, and who is allowed to do any of it.

1. Accounts and contacts on one record

The base of every CRM: one record for the company, one for each person in it, and everything else attached to them. It sounds trivial until you watch a team without it: three versions of the same customer in three inboxes, and nobody sure which phone number is current. What to look at is not the field count but the timeline underneath: notes, files, emails and past deals in one place, so a rep who has never spoken to this customer can read the history and pick up the thread. How that record is structured is its own subject, covered in the CRM database guide.

2. Lead capture and qualification

A lead is an inquiry you have not decided about yet. The feature is a holding area: a record carrying where the inquiry came from, what it asked for and who owns it, plus a way to convert it into an account, a contact and a deal without retyping anything. Look hard at that conversion step. When converting means copying fields by hand, logging quietly stops, and a source nobody counted is a marketing budget nobody can defend.

3. Custom fields, record types and custom objects

Every business has vocabulary the vendor never heard of: hull number, cohort, territory, freight terms. Custom fields let you add it. Record types let two kinds of customer carry different layouts. Custom objects let you store something the CRM has no name for at all (a property, a vehicle, a course) and link it to the customer. The first is standard, the second is common, the third usually sits on a higher plan. If your business runs on an object that is not a deal, check that one before anything else.

4. Deals and pipeline stages

A deal is a potential sale with an amount, an owner, a close date and a stage. Stages are the underrated half: they are how a whole team reads the same board the same way. The useful test is whether a stage means something observable (“Proposal sent” should mean a priced document actually reached the customer), because a stage defined by feeling produces a forecast made of feelings. Defining stages by exit criteria anyone can verify is one of the CRM best practices worth settling before the first deal is logged.

5. More than one pipeline

One pipeline works until you sell two things that behave differently: new business and renewals, projects and retainers, direct and dealer. Push both through one set of stages and every report becomes an average of two unlike things, describing neither. Separate pipelines, each with its own stages, fix it. This is often the first capability above an entry tier, so check how many pipelines your plan allows rather than assuming the product page applies to you.

6. Activities: tasks, calls and meetings

The pipeline says what is in play. Activities say what happens this week. Every open deal should carry a dated next action attached to the record rather than to somebody’s personal to-do list, with a calendar view, reminders, and completed work logged where the next person can see it. The share of open deals carrying a dated next action is the quickest read on whether a CRM is genuinely in use.

7. Forecasting

Forecasting turns the pipeline into a number somebody will be held to: a forecast category on each deal, a quota per rep, a manager’s adjustment, and last month’s forecast kept so it can be compared with what happened. Without that history you cannot separate an optimistic team from an unlucky one. Forecasting is frequently a higher-tier capability, so if the monthly number is the reason you are buying software at all, find out which plan carries it first.

8. A product catalog and price books

Once quotes matter, the catalog matters. A product list with codes, units, list prices and currencies stops three reps from inventing three prices for the same item. Price books let a dealer and an end customer see different terms without a private spreadsheet keeping score. This is also the point where the CRM stops being a sales notebook and starts touching finance, which means somebody has to own the list and keep it current.

9. Quotes with versions and a PDF

Quoting is where a demo tends to look its best and where day-to-day work quietly stalls. Check four things: can you build the quote from the deal, discount a line, produce a PDF you would actually send, and keep version two without destroying version one? Version history is the part people skip and then need. “Which price did we send them in March” is a question every business eventually has to answer, and the answer should not live in a sent-items folder.

10. Approvals for the exceptions

An approval is a gate: a discount past a threshold, a nonstandard term, a payment schedule finance has to see. It is worth having only if it is fast: defined steps, named approvers, and a record of who said yes and when. Slow approvals get routed around by phone, and the record you were trying to create never appears. Because approvals imply roles and permissions underneath, vendors usually put them on a higher tier than quoting.

11. Contracts, orders and invoices

Some businesses stop at the accepted quote. Others need what follows: a contract, an order and an invoice carrying the same lines rather than being retyped into another system. If your finance team currently rekeys won deals into accounting, this is the capability to look at first. If those documents already live in an ERP, the handoff matters more than the module does. Either way, generated PDFs and uploaded files belong on the record they came from.

12. Two-way email sync

Connecting a mailbox is what keeps a CRM current without anyone maintaining it. Sent and received messages land on the contact, account or deal they belong to, so the history exists whether or not a rep remembers to log it. Ask which providers are actually connected: Microsoft, Google and plain IMAP or SMTP are separate integrations, and a vendor that has shipped one has not necessarily shipped the others. Ask the same about calendars, which are separate connections again. Then confirm inside a trial that sync runs both ways rather than copying in one direction.

13. Messaging channels and a shared inbox

In many markets the customer is on WhatsApp or Instagram long before email. A CRM that pulls those threads onto the record closes a blind spot most systems still have: the conversation that exists only on one person’s phone. It is also one of the capabilities most often shown before it ships. Treat a channel as available when you can connect it inside a trial account, not when it appears on a slide with a logo next to it.

14. Workflow automation

Automation is a rule: when this happens, do that. Assign the record, create the follow-up task, notify the manager, move the stage, raise the internal alert. Two things separate a useful automation feature from a decorative one: a builder somebody non-technical can read, and a run log showing what fired, what failed and what was retried. Automation nobody can audit is automation nobody trusts, and untrusted automation gets switched off.

15. Assignment and routing rules

Who picks up a new inquiry, and how fast. Routing by territory, product, segment or round-robin removes the pause where a lead sits unowned because two people each assume the other has it. It is a small capability with an outsized effect on response time. It is also a common entry in a vendor’s “coming soon” column rather than the shipped one, so verify it in the product itself.

16. Reports and dashboards

The point of a record is the question you can ask of it: conversion by source, win rate by rep, average days in each stage, deals that have not moved in weeks, and why you lose. Look for saved reports, scheduled delivery that respects each user’s permissions, and dashboards built from those reports rather than a fixed set of charts you cannot change. Reporting is also the honest test of your data, because reports look wrong exactly when the records are wrong.

17. AI features

AI inside a CRM earns its place when it prepares work rather than performing it: a summary of a long thread, a first draft of a reply, a digest of what needs attention today, a suggested next step on a stalled deal. What to check is where it reads from and what it is allowed to see: a summary should never surface a record the user could not open themselves. Teams that get value treat the output as a draft, which is the argument made at more length in AI CRM.

18. Permissions, roles and an audit log

Who can see which records, who can change them, and what happened afterward. Roles and record ownership decide visibility; field-level permissions decide whether a rep sees cost as well as price; an audit log, a recycle bin and a restore decide whether a mistake can be traced and reversed. Small teams skip this and regret it at the first departure, since exported or deleted customer data is a governance problem before it is a technical one.

19. Integrations, import and export

A CRM is never the only system in the building. Three things matter: an import that survives your existing files, an export you can run yourself at any time, and connectors or an API for the tools you are keeping: accounting, marketing, support, calendar. Ask which objects the API actually covers, because “we have an API” often means the core records (contacts, accounts, deals and activities) rather than every record type behind them. Test the export during the trial rather than after, and read CRM integration before you promise anyone a two-way sync.

Which features should you set up first?

Almost nobody needs nineteen features in month one. The pattern that works is small: get the record right, make the pipeline honest, connect email, then add one capability at a time as a real complaint appears. Features turned on before anyone asked for them are the ones that end up half-filled and mistrusted, and a half-filled field is worse than an empty one because people read it as true.

Where a team is today decides which features earn their place first, so read the list below as a starting point rather than a rule. Sequence matters more than coverage, and CRM implementation covers the order that work usually takes.

• Two or three people selling, no system yet: set up accounts and contacts, deals and stages, and activities; leave multiple pipelines, forecasting and custom objects until later.
• Founder still selling, first sales hire made: set up the three above, plus two-way email sync; leave approvals, assignment rules and AI until later.
• A handful of reps and a manager who reports upward: set up multiple pipelines, reports and dashboards, and forecasting; leave custom objects and API projects until later.
• Every deal needs a priced document: set up the product catalog, quotes with versions, and approvals; leave contracts and invoices until quoting is steady.
• Won deals become contracts or invoices: set up contracts and orders, documents, and the accounting handoff; leave AI features until the record is trustworthy.
• Sensitive data, or several teams sharing records: set up permissions, roles and the audit log; leave automation until ownership rules are settled.

Plan tiers and “coming soon”

Two things bend a feature list out of shape. The first is plan tiers. A capability listed on a product page may begin two plans above the one you priced, and it is usually the same handful: multiple pipelines, approvals, custom objects and forecasting, because each implies administration underneath. Price the plan you will be on once the team has grown into the tool, not the one you sign up for on the first day. Building the shortlist itself is a separate exercise, set out in how to choose the best CRM.

The second is timing. Coming soon, in beta and on the roadmap all mean the same thing to a buyer: not now. Buy the product you can open in a trial account. If a promised capability is what makes your shortlist work, say so out loud and ask for a date in writing. And if you are testing entry tiers to see how far they stretch, free CRM sets out what those plans normally hold back.

What Senitix CRM covers today

Senitix CRM covers most of this list today, and all of it works on one customer record. Set against the seven groups above:

• Records: leads, accounts and contacts, custom fields and custom objects.
• Pipeline: deals with stages, multiple pipelines, activities with a calendar, and forecasting.
• Quoting: a product catalog and price books, quotes with versions and a PDF, approvals, contracts, orders and invoices, and the Documents module.
• Communication: connected email and calendar through Gmail, Google Calendar, Microsoft Outlook, Microsoft Calendar or any IMAP/SMTP mailbox.
• Automation: workflow rules built in a visual editor, each with a run history, and rule-based scoring of leads, contacts and deals.
• Reporting: reports and dashboards, plus Senitix AI for daily digests, email drafts and thread summaries.
• Administration: roles and field permissions, each record’s change history, a setup audit trail of admin changes, and CSV or Excel import and export.

Integrations run through a connected app that Senitix registers rather than a self-serve public API a developer signs up for and calls directly: talk to Senitix about the specific integration you need. What is not there yet is listed just as plainly. Messaging channels (WhatsApp, Instagram, Messenger and Telegram), shared inboxes, web forms that create leads, saved email templates, assignment rules, macros, sharing rules, configurable duplicate detection and outgoing webhooks are coming soon rather than something you can switch on, and this page promises no date for them. Until assignment rules arrive, an automation can set a new lead’s owner. Senitix CRM runs in a web browser; there is no native mobile app yet.

The paid plans have no free trial; Free is the way to try the product, for up to 2 users, with no time limit and no credit card. Every capability is listed in the Senitix CRM feature catalog, and what each plan includes and costs is on plans and pricing.

The list you should actually write

Write your own list before you read anyone else’s. Five lines is usually enough: the question your manager asks every month, the document you send most often, the handoff that keeps going wrong, the thing nobody remembers to do, and the report somebody rebuilds by hand. Match those five against the nineteen above and you have a requirements list no demo can flatter. CRM examples walks through five common workflows written out that way, and the benefits of CRM come from those five lines rather than from the longest feature list on the market.