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.

been doing this for a few years now and kept running into the same problem. quote a timeline, client agrees, then week three happens and suddenly we're explaining why it's taking longer.

took me embarrassingly long to figure out the pattern.

it's always the integrations. not the modules, not the theme, not even the content migration. it's always some connection to a third party system that nobody documented because the person who built it left two or three years ago.

last one was a CRM integration that was still firing on every form submission. CRM itself had been discontinued. nobody on the client side knew it was there. showed up in the server logs as a timeout error that everyone had just... learned to ignore.

started doing a proper integration audit before we write any estimates now. just mapping everything that talks to everything else. takes a few days but it's saved us from at least three nasty surprises this year.

curious if others have a good process for this. especially for sites that have changed hands a few times and have basically no documentation. feels like every D7 site we touch has at least one of these buried in it somewhere.

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?