I have been working around CRM systems and noticed something interesting: businesses often spend a lot of time asking whether a CRM has every possible feature, when the features they actually use regularly are much fewer.
For example, things like:
Lead and contact management

Pipeline/deal tracking

Follow-up reminders

Email integration

Task automation

Reporting

But then there are dozens of advanced features that sound useful during the buying process but may not get much real-world usage.
I’m curious about the experience of people here:
What CRM feature did you initially think was essential but later realized you rarely use?
And on the other side, what’s one simple CRM feature that has had a much bigger impact on your daily workflow than you expected?
Would be interesting to hear experiences from both small teams and larger organizations.

I have a unique instance we're struggling to work through and was hoping someone might have ideas.

We use Salesforce for sales and our record of truth, and we us HubSpot for marketing. We are moving sales into HubSpot just for sequences (moving them from Outreach), SF will remain their primary CRM.

Here's the weird and annoying part. Our Salesforce doesn't use email as a unique identifier, it uses a combination of email + lead source + line of business. So John could easily have multiple records that would look like:

- John / Webinar / Product A (Lead Status: Open)

- John / Webinar / Product B (Lead Status: Unqualified)

- John / Tradeshow / Product A (Lead Status: Open)

- John / List / Product B (Lead Status: Contacted)

- etc.

Currently all info is aggregated on 1 HS record, so HS shows 1 John with Webinar, Tradeshow, and List as lead sources and Product A, Product B for LOB, and Lead Status doesn't really matter to marketing.

With all this in mind.... How do we get sequence activity to log to the correct SF record? How can we say enroll John in Sequence 1, and then that activity should go to John / Webinar / Product A (Lead Status: Open) and not a different one? Using the most recent lead isn't reliable enough and we're at a loss for what other logic could be used.

Any help or ideas would be much appreciated!

This is a weekly post for you to let out about something which happened this week for you in CRM that mattered: features, client requests that were either great or awful this week, and just generally chat CRM / CRM consulting chatter.

No self promo, just a place to share tales from the front-line of CRM!

[ Removed by Reddit on account of violating the content policy. ]

Hey everyone! I'm a marketing student and I've been trying to understand sales operations better from people who actually work in this field.

One thing I keep hearing about is how scattered everything can get between the CRM, emails, meetings, pipeline and account activity. Then you end up with things getting missed, CRM data not always being accurate, deals going quiet, missed follow ups, or just not knowing what actually needs attention.

But I'm curious, is this actually a big problem for you guys? Or are there other problems in Sales Ops that are way more painful day to day?

Also what software are you currently using to manage all of this? Is there anything you actually love or couldn't work without? There is a wide range of software that sales and revenue managers are using these days so what is something you guys are looking for when trying to choose one?

And I'm curious about pricing too. For software that genuinely solves an important Sales Ops/revenue problem, what would you consider a reasonable monthly price for a team?

Just trying to understand how this actually works in real companies rather than guessing from the outside and classroom.

​

I’ve been thinking about this lately because a lot of CRM discussions focus on choosing the right platform, features, integrations, and pricing.

But I’m curious about the problems that happen after the CRM is already set up.

Things like:

- Duplicate contacts entering the system

- Leads coming in with missing information

- Bad or outdated contact details

- Leads sitting unassigned

- Sales reps manually checking and cleaning records

- Information getting lost between forms, email, CRM, and other tools

- Having to manually decide where each new lead should go

Which of these causes the most headaches for you?

And if you could completely eliminate one repetitive CRM task tomorrow, what would you choose?

Hey everyone —

I’m the founder of ServiceFlow Pro (scheduling, estimates, dispatch, invoicing, payments — built for trades like HVAC, plumbing, electrical, garage door, etc.).

I’m looking for a small group of real operators (owner / office manager / dispatcher) to use it on live work for 30 days, free, and tell me what’s good, what’s broken, and what’s missing.

What you get

• Full access for 30 days (no card required for this pilot)
• Help getting set up (customers, schedule, estimates)
• Direct line to me if something’s annoying

What I ask

• Actually use it for real jobs for ~30 days
• A short check-in mid-way + a honest debrief at the end (15–20 min call or written notes)
• Permission to use anonymized feedback to improve the product (no public testimonials unless you say yes)

Ideal fit

• Small–mid service business already scheduling jobs somehow (Jobber, ServiceTitan Lite, Google Calendar, paper, etc.)
• Willing to try something new for a month

Not looking for tire-kickers or “just send me a login.” Prefer people who’ll put a few real jobs through it.

If you’re interested, comment or DM with:

1. Trade / industry
2. Rough crew size
3. What you use today for scheduling/invoicing

I’ll pick a few people and get you set up this week.

Thanks.

I want to pull Google reviews into the dashboard for basic analytics. Looking for genuine recommendations from people who have actually implemented this, not vendors promoting their own tools.

What’s the most reliable approach: Google Places API, established third-party API or maybe something else? I’m particularly concerned about ToS/legal risks, data storage restrictions, and long-term reliability.

For those of you who use a recruitment CRM/ATS with email campaigns, how does it handle replies?

I’m building a CRM/ATS and I’m currently working through how bulk email campaigns should behave compared with normal 1:1 emails/sequences.
For sequences, I already send emails through the recruiter’s connected Outlook/Gmail provider. That means the message is genuinely sent from their mailbox, appears in Sent Items, and replies naturally remain within the normal mailbox conversation.
We also monitor sending volumes at mailbox level and throttle/queue sequence emails in line with the provider’s API rate limits and mailbox sending limits, rather than simply firing every due sequence email at once.

That works well for sequences, where the number of emails being sent from an individual recruiter’s mailbox is relatively controlled.

The question is what to do with larger campaigns.
Microsoft 365 and Gmail aren’t really intended to be bulk email infrastructure, so for campaigns potentially going to hundreds or thousands of candidates I’m considering using something like AWS SES instead.

For example:
From: Sarah Jones [[email protected]](mailto:[email protected])⁠
Reply-To: [[email protected]](mailto:[email protected])

The organisation would verify its domain or provide SMTP credentials, so to the candidate the email still appears to come from Sarah at the agency. If they click Reply, their mail client would address the reply to Sarah’s normal email address and it would arrive in her Outlook/Gmail inbox.

The obvious difference is that the original campaign email wasn’t actually sent through Sarah’s mailbox, so it wouldn’t naturally appear in her Outlook/Gmail Sent Items and therefore the reply would appear without context if the sent message.

The CRM would retain the exact outbound campaign email against the candidate. Because their mailbox is also synced with the CRM, the candidate’s reply could then be associated with that outbound campaign message and displayed as part of the same conversation/activity history inside the CRM.

For people using systems such as Bullhorn, Vincere, JobAdder, Recruit CRM, Loxo, etc., I’d be interested to know how your current system handles this in practice.

- Does a campaign reply simply arrive in your normal Outlook/Gmail inbox as well as the CRM?

- Can you see the original campaign email in Outlook/Gmail, or only within the CRM?

- If you receive a reply and need context, do you generally open the candidate in the CRM to see the original email?

- Does your CRM somehow add bulk campaign emails to your Sent Items? Or are replies routed through the CRM itself rather than directly back to your mailbox?

My current thinking is essentially:

Sequences: connected Outlook/Gmail mailbox, with sending volumes monitored and throttled according to provider/API limits.

Campaigns: bulk delivery infrastructure such as SES, but still using the recruiter’s name/domain and directing replies back to their real mailbox.

I’m trying to work out whether the fact that campaign emails don’t appear in Outlook/Gmail Sent Items is actually an issue for recruiters in practice, or whether people naturally use the CRM conversation history for that context anyway.

Hi everyone! I've spent the last 2 years building a CRM for entrepreneurs and small businesses. I'm a technical developer, I really love the product, and I know it has potential, but I have zero sales skills and I have no idea where to start.

I'd really appreciate any advice on how to land my first customer.

CRM demonstrations usually focus on what happens inside the platform.

But many of the real problems appear between systems: customer-service records, contact-centre conversations, billing data, analytics, marketing activity and knowledge bases.

If you were evaluating a CRM or CX platform, which integration would you insist on seeing live rather than accepting a slide that says “seamless integration”?

And what failure or limitation would you specifically test?

I’m helping organise an online CX technology event where providers will give focused demonstrations followed by Q&A.

Disclosure: I’m involved in organising the event.

Curious how common this actually is outside my own head: how much time do you (or your team) spend re-typing a Jira ticket update into an email or Slack message so a customer knows what's going on with their issue?

I kept hearing this from CSM/support-lead friends — engineering updates a ticket, nothing reaches the customer unless a human relays it, on a delay, inconsistently, and there's no real record afterward of what was promised vs. what shipped.

So I built X2Bridge to close that gap. It's not another chat tool and it's not asking your engineers to change anything — it sits on top of your existing Jira, polls it, and auto-translates ticket status into plain language for the customer. You (the vendor) control exactly what's visible — every comment has a visibility toggle, so internal debugging notes stay internal by default. The customer gets one clean view of their own issues, no Jira seat needed, can reply or drop in a screenshot/log file, and it syncs back into the ticket automatically so engineering isn't checking two places. There's also a release-notes feature — auto-drafted per-customer summaries of what shipped, that you review before sending, with a sign-off/acknowledgment trail you can point to later.

It's live and self-serve: x2bridge

I'd really value your take, especially if the answer is "we don't actually have this problem" or "we solve it a totally different way":

• Does this match how status updates actually work on your team, or am I off base?
• What's your current workaround, if any?
• What's missing that would make this a non-starte

I’m curious about the gap between what looks useful during the CRM buying process and what actually becomes part of your day-to-day workflow.

I’ve also been experimenting with ChatGPT for AI-related tasks like organizing information, brainstorming workflows, and simplifying repetitive work, which has made me think more about which CRM features genuinely add value versus which ones just look impressive on a feature list.

What’s a CRM feature you initially considered a must-have but rarely use today? And why?

If you look at most small service outfits or clinics, the bottleneck isn't getting inbound inquiries—it's that daytime operations turn into pure triage.

When call volume spikes, operations usually break in one of three ways:

The front desk has someone standing right in front of them, so two high-intent phone calls roll straight to voicemail.

An AI voice tool is tested, but customers hang up after five seconds because it mangles their address or can't handle nuanced questions.

An answering service is hired, but they just email a vague slip saying "John called about a water heater," leaving the owner with 15 callbacks to make at 6 PM.

A few months ago, we completely reworked how we handle intake and scheduling directly inside dispatch/CRM software (Jobber, ServiceTitan, Dentrix, etc.).

Instead of an answering service or a bot, we set up a dedicated human front-office layer that lives inside the software with built-in redundancy:

Real-time calendar booking: Calls are qualified and booked directly into the dispatch screen rather than taking paper messages.

Working the back-office backlog: When phones aren't ringing, that time isn't dead—it's used to actively work open estimates, stalled treatment plans, and cancellation waitlists.

A shadow backup model: The primary admin has a pre-trained secondary synced to the exact same standard operating procedures, so a single sick day doesn't bring intake to a dead halt.

The most eye-opening metric wasn't just catching missed calls. It was realizing how much money was quietly rotting inside the CRM simply because the on-site team never had 30 uninterrupted minutes to follow up on sent quotes.

For those running 5 to 15 field techs or clinic staff: how do you currently handle outbound follow-ups on open quotes when the front desk is pinned down all day?

​

I'm curious what people here think about pricing for a small-business CRM.

Let's say the product includes:

- basic CRM (contacts, companies, leads, tasks)

- sales pipeline / Kanban

- calendar

- invoicing

- customer & invoice management

- a few automation features

Would $30/month feel expensive for something like this?

I initially thought about pricing it at $25/month, but I'm wondering if the extra $5 actually makes a meaningful difference in how people perceive the price.

For a small business what would feel like a reasonable monthly price?

$15 / $20 / $25 / $30 / $40+?

Curious to hear what you'd personally be willing to pay and what would make you choose one price over another.

The tool is primarily aimed at Polish companies and also handles invoicing requirements related to the EU's standardized invoicing system: https://ksefgpt.pl

The systems that work best are usually not the ones with the most features.

They are the ones people actually use every day.

We have seen businesses buy a CRM, then keep the real customer history in inboxes, spreadsheets, personal notes, text messages and someone’s memory. The CRM becomes a reporting tool nobody trusts because it is updated after the fact, if at all.

What works is keeping the process simple. One place for the customer record, clear ownership of the next step and a follow up task that cannot disappear when the day gets busy.

The technology matters, but the workflow matters more.

if u r starting a new job or switching roles right now how are you preparing yourself? With AI, automation and CRM platforms evolving so quickly what r the skills u are actually focusing on to stay relevant?

Getting your CRM to fit your process feels like a win in the moment. When you add a field, rule, or stage, each one solves a real problem when it's created.

But teams often overlook scheduling a follow-up conversation about whether it's still solving that problem a year later. What happens then is that the system just continues to accumulate weight until it's far more complex (and harder to use) than the generic version you started with.

The teams that seem to avoid this treat customization as something with an expiration date by default (so, not a permanent thing). Every field or automation is tied to a person and a reason when it's built, and there's an actual recurring checkpoint where someone asks whether it's still earning its place.

The harder question is determining who owns that review. It's rarely anyone's actual job. The person who built the automation may have moved teams, and the admin consequently inherits a system full of decisions they didn't make. Cleaning it all up always seems to lose to whatever's on fire that week.

How do you handle this in practice? Is there a real cadence for auditing what's actually being used versus just left over, or does it only happen when the system gets bad enough that someone finally forces the issue?

Trying to figure out if Ahrefs Brand Radar makes sense on its own. The CRM is already covered. SEO tooling only gets used here a couple times a quarter so buying a full marketing platform just for AI visibility does not really make sense.

What caught my attention is that Ahrefs has custom prompt tracking as a separate option. It also seems to sit outside the credit system used by the wider platform.

For people who have actually looked at Ahrefs Brand Radar standalone, does it feel worth paying for or is it one of those things that sounds more useful than it ends up being?