Is anybody validating international addresses at scale, 60K+ contacts? US address I can validate against USPS, but I am working with a client that is truly global B2B and haven't uncovered an effective way to validate minimally that the city, state/province/county, postal code are all valid. About 50% of the 60K are European, any good low cost options?

Hi - We're soon launching a new Shopify Audience Insights app and we're wondering how we go about setting up an events/trigger-based CRM program and specifically, how we capture email opt-ins for recontact. Knowing that the email address captured when a Shopify merchant registers may not be the same as the email address as our user(s) - for example, a shop owner might register but a marketer would use our app - what is the best way to capture and email? Any tips on the best way to setup CRM within the Shopify ecosystem?

Appreciate any tips provided.

I do RevOps and CRM cleanup work for a living. Mostly HubSpot builds, untangling duplicate/messy data, and keeping Clay and HubSpot in sync. I've got a bit of slack this week and I learn more from real broken setups than anything else, so figured I'd trade.

→ Drop a comment with whatever's annoying you most about your CRM.

→ Tell me what your setup looks like and what's going wrong, and I'll reply with how I'd actually approach it.

specific, not "book a call."

First handful of comments I'll go deep on and happy to take it to DMs if it's got sensitive data...

See you in comments

Merging duplicate company records can clean up reporting while also collapsing details that were intentionally different: regional ownership, consent state, open opportunities, support history, external IDs, and field values from separate systems. What merge contract prevents silent data loss? I would expect a chosen survivor record, field-level precedence rules, a redirect from retired IDs, preserved source attribution, reassignment of related objects, and an audit record that can reconstruct the pre-merge state. How do you handle conflicting permissions and account hierarchies, downstream systems that still reference the losing ID, and the rare case where a merge must be reversed after new activity has already landed on the survivor?

Landscaping company in Utah here, I have used house call pro for a bit, I tried jobber, and I am just not happy with either of them. Jobber is good at a lot of things but not GREAT at anything in specific, and defintely lacks in a lott of areas. For example when i am routing my jobs on jobber it is just such a pain, and don't even get me started on the upcharges for every little thing. Has anybody had the same experience or am i just not using the software right? I have looked into a couple others like servicem8, SRVCE HQ, etc. But just seeing what everyones thoughts are and what they have tried/heard. Thanks.

We’re losing people between the start of registration and completed payment. Long forms and a payment experience that feels separate from the event both seem to contribute.

Eventify keeps the full checkout flow branded and connects directly to Stripe, while still allowing custom questions and ticket types without developer support. That combination appears to be why some organizers reported better completion rates after switching.

What registration setup have you used that felt simple for attendees while still giving you the data and ticket flexibility you needed?

Hi everyone

I have spent months to build crm for small agencies and real estate now I need few people to test my crm and give a feedback or opinions and say what is broken in the crm or what is missing in the crm

It is very simple to use and simple ui to understand and free to use not credited card or payment required to use it

Test it and give a feedback and opinions

Crm.hero-industries.in

Feedback and opinions is must

I spent the last few months building Griddus CRM — a CRM made for small and medium businesses anywhere in the world, with a visual pipeline, accounts, contacts, tasks, field visits, geolocation check-ins, and a layer of AI (lead scoring, sentiment analysis, and follow-up email drafting).

I set up a free demo environment — no account, no strings attached:

Griddus CRM

Accessing the main website, click the DEMO button.

All data is fictitious and is periodically updated. I am open to honest feedback (praise and, especially, criticism) — the goal is to make it truly useful for sales teams in their daily work.

What do you think? What's missing for a CRM for SMEs to be worthwhile?

I’ve been building Pobalt around a problem I kept seeing with home-service businesses: their customer management and their actual day-to-day operations often live in completely different systems.

Pobalt is designed to bring both sides together:

• CRM & customer management
• Jobs & work orders
• Scheduling
• Invoicing
• Team management & permissions
• Automations
• Business dashboard

The workflow I'm aiming for is simple:

Customer → Job → Schedule → Team → Invoice

All connected in one system.

I’m the founder, so I want to be transparent that this is my own product.

For people who work with CRM systems: what's one feature you think most CRMs still get wrong?

I'm a developer in the initial stage of building a CRM — before writing any code, I'm trying to find the users of these solutions for now.

No intentions to make a pitch here. I really need to know what is wrong.

Here are a few issues I've heard from people that I talked to:

- Pay-per-seat pricing that causes headaches in scaling

- Manual logging of the activities feels like doing the second job

- Documentation and email correspondence exists everywhere but not in the CRM

- Artificial intelligence is useless or demands transferring your data to some third-party

However, I want to hear your opinion:

What does your CRM fail completely? What is that issue you hear from your team during every stand-up?

Additional question: did data privacy or "Where is our client data actually stored?" become an issue ever? Or, probably, this is a non-issue in reality?

Every comment helps. Even the single one liner will be good.

For the devs/consultants here who've actually built these for clients: in your experience, do real estate owners (or whatever niche you work in) usually end up wanting something custom, or do they just take GHL/Zoho/HubSpot and configure it?

What tips them one way or the other, budget, missing features, or just not wanting to deal with a dev long term?

And if you've built custom for a client, did it actually hold up, or did they end up wishing they'd just used an off the shelf tool?

I’ve been using Reddit for customer acquisition, feedback, and talking to founders for a while, and one problem kept coming up:

Reddit is great for starting conversations, but terrible for remembering and organizing all the people behind them.

You talk to someone today, they comment again next week, you DM them later, and eventually you have dozens of usernames with no idea who was who or what you talked about.

I used to manage all of this in spreadsheets.

So I built Bantico, basically a CRM around Reddit relationships.

It helps you:

• Find potential customers already talking about problems your product solves, asking for recommendations, or looking for alternatives.
• Keep people and conversation context together, so you know who someone is, what you’ve talked about, and why they might matter.
• Organize potential customers and relationships instead of keeping Reddit usernames scattered across spreadsheets.
• Track your interaction history so you can see previous conversations and know where you left off.
• Use Watchlists for people who look interesting but aren’t ready right now, so you can keep track of them instead of forgetting them.
• Know who to follow up with as relationships develop over time.
• Keep beta testers, potential customers, community members, feedback conversations, and eventually paying customers in one place.

The basic idea is that a Reddit post or comment might be the first interaction, but the person behind it can turn into a much longer relationship.

So instead of treating every Reddit conversation as an isolated interaction, Bantico helps you build context around the person over time.

Would love to know if anyone here is currently using a traditional CRM for Reddit-sourced relationships, or if you’re still handling this manually with notes/spreadsheets.

Every few weeks, we see a post in this (or a similar) subreddit asking which CRM is the easiest to learn. Why people ask this is understandable. Nobody wants to sink a whole week into onboarding just to abandon the software later. But after seeing many teams go through the onboarding process, we believe that "easiest" might apply to more than just the tool’s interface.

The teams that struggle with the implementation and onboarding process almost always try to import their entire contact history on day one, build a pipeline with nine stages (because that's how their process "really" works), and turn on every notification and automation they can find before anyone has even touched a single deal. Then, two weeks later, the system feels like a second job, and they blame the tool.

The teams that stick with it and succeed actually do the opposite. They start by importing only a small portion of contacts they currently work with, keep the first pipeline to just a few stages, and don’t add any automations until the team has understood exactly which repetitive tasks are worth automating. Those teams may not necessarily describe the software as simple, but they'd likely describe their own approach as restrained.

This could be why CRM adoption stats are typically so low. It's not that the tools are secretly all terrible. It's just that the task of setting it up properly is treated as a weekend project instead of a month-long process. By the time teams are frustrated, they assume it's a product problem instead of a pacing problem.

Has anyone else seen the same pattern? Did switching to an “easier” tool actually fix adoption for your team, or did it just delay the same mistakes by a few weeks?

One thing I noticed while talking to small businesses is that WhatsApp often becomes their unofficial CRM.

A customer sends a message → someone replies → the conversation gets buried → nobody follows up → the lead is gone.

So we’re building Aerostic around that problem.

The idea is to bring WhatsApp, AI, CRM and automation into one place.

For example, a business can have an AI agent handle initial enquiries, qualify leads, follow up with people who haven't responded, and keep the customer information organized in a CRM. A human can step in whenever the conversation actually needs one.

The goal isn't to replace the sales team.

It's to remove the repetitive work around the sales team.

We're still improving the product, so I'm curious:

How do you currently manage customer enquiries that come through WhatsApp?

Spreadsheet? WhatsApp Business? CRM? Everything manually?

I'd especially like to hear what actually works and what doesn't.

Hi! we just rolled out a new CRM setup... and to be so real... it is a total flop. the sales reps are completely rebelling because the system requires way too many clicks just to log a basic update.

instead of using the platform... they've gone completely rogue. they are tracking everything in their secret Excel sheets... and they literally only log the deal into the CRM after it’s already closed-won... just to secure their commission check. like they are straight up refusing to touch the pipeline.

it's because our admin made the mobile layouts completely unusable... they added all these dependent picklists where you literally have to click through 12 dropdowns just to log a standard bolt-on attachment or a quick pricing tier change... so the reps just... don't do it.

management is completely blind to it because they only look at the final closed-won revenue numbers... but our pipeline forecasting is literally in the negatives. we have zero visibility because the system thinks we have $0 in the pipeline until a random $50k deal just spawns out of nowhere on Friday afternoon during the final vibe check... it's so bad.

has anyone successfully dealt with sales reps flat-out refusing to use a new CRM?? how do we fix the friction before this Excel shadow-IT completely takes over... it's getting weird.

You send over a strong candidate. Client says “great, we’ll review this week.” Then nothing.

How many days before you follow up? And is that an actual system a reminder, a recurring task or do you just remember eventually?

Asking because I’m researching how solo desks run day to day. Not selling anything.

No finance person on staff, just a founder wearing every hat. Curious how other small teams are actually managing idle cash without it becoming a part-time job. What are you using and is it worth the setup?

So I was manually testing emails forever and finaly found a better way. basically you find one verified email from the company (LinkedIn, press release, whatver) and then you can see their email pattern. like if you find [[email protected]](mailto:[email protected]), you know everyone else is firstname.lastname@

the annoying part is verifying each email after. i was using hunter for this but started getting too many bounces on thier "valid" emails. tried a few others too - Apollo shows you the company email format which is nice but the data quality has been hit or miss for me. someone on my team mentioned Prospeo does somthing similar, might check that out next

plus my manager keeps asking why our outbound bounce rate is so high and im like bro the email verification tools are lying to us lol

anyone else have tricks for this? especially for companies that use weird formats like first initial + last name or that dreaded firstname.lastname.countrycode@ format

Hey all, I do Dynamics 365 CRM development and could use a few extra projects. If your team's backlog is piling up or you need a second pair of hands for a sprint or two, I can help.

What I work with:

• C# plugin development (custom business logic, validations)
• Power Automate flows + Power Apps
• Dataverse config/customization
• Microsoft Graph API integrations with D365
• SLA/KPI troubleshooting and fixes

Happy to jump into an existing codebase, take on a defined ticket batch, or handle a scoped integration piece. Flexible on hours — treat this as overflow capacity, not a full-time ask.

DM me or comment if you want to chat scope/rate.

I’m trying to clean up what happens between finishing a discovery call and updating the CRM. Right now I usually end up with half a page of shorthand, then spend another 15---20 mins turning it into something the rest of the team can follow.

workflow I’m trying to get to is:

1. Record and transcribe the call.

2. Pull out pain points, budget, timeline, decision makers, objections and next steps.

3. Check anything related to pricing, dates or customer commitments.

4. Put the cleaned up version into the CRM and use it for the follow-up email.

The third step is where I’m stuck. AI note taking can turn “maybe in Q4 if security approves it” into “planning a Q4 rollout,” which looks harmless in a summary but changes the meaning once someone sees it in the pipeline.

Any advice on making this less manual without letting bad notes into the CRM would be appreciated. Thanks.