I've designed software to protect you from dialing or texting people outside of the tcpa calling hours. I'm really trying to show some comparisons between it and any other programs or crms that have similar features. Usually that's a dialer. If any of you are curious and willing to try the experiment, then the tests are simple:

Make a test lead and use a dummy phone number like (areacode) 555 0157. That range of numbers are not given to real people so they can be used in movies etc.... The area code you choose shouldn't matter since the service should go by state/zip with people moving around.

Set the state for RI zip code 02901 and try to call it after 6 pm EST. Your system should block you.

Set the state for FL zip code 32003 during the day and try to call it 4 times. It should block you on the 4th try.

Set the state for AL zip code 35004 and try to call it on Sunday. Your system should block you.

If any one of those goes through, then your system isn't blocking correctly. If all of them go through, then your system probably doesn't block calls based on state rules at all. 23 states are more restrictive than the federal guidelines. If you can call or text earlier than 8 am or later than 9 pm, then your system doesn't block Federal law either.

Please post the results here or send me a DM. I'll give you a free subscription to my software for a year for testing, but I don't need too many people to test each one so first come first served.

I'm throwing this out there as my team uses GHL but I hate the CRM and its clunky to use.

So I went down the path of using API's from it to custom build a layer that allows me to send notes back to GHL, search, and create daily call lists so much faster than GHL.

All of this was done with Claude Code.

If you're CRM has API's just build something custom that is tailored to your workflow and setup.

I am frustrated with every CRM marketing to me that they will save me time and increase productivity but as soon as I sign up I have to relearn their whole system and create workflows by their rules. What CRM frustrations do you have?

I can't be the only one who is fed up. Am I crazy?

Bill McDermott was pretty blunt on ServiceNow's results call. His pitch is that the old CRM was built for sales teams, and that service is where the customer relationship actually lives. He's openly talking about rip and replace, and says deployment times are now 30 or 60 days for a serious company at serious scale.

There are some numbers behind it. CRM showed up in 13 of ServiceNow's top 20 deals last quarter and CRM AI net new ACV tripled. HPE signed up for its Cloud and AI support services, and Stagwell is consolidating four legacy service desks across more than 70 agencies.

I'm sceptical of the 30 day bit. Data migration and integrations are what kill CRM projects, not the software.

Has anyone here moved service off Salesforce or Dynamics onto ServiceNow? How long did it really take?

So many CRMs list Google Calendar as a supported integration. But “integrates with Google Calendar” can actually mean very different things in practice.

For some tools, it means that events added to Google Calendar show up in the CRM. For others, it means that changes sync in both directions. And the difference between these only really surfaces the first time a rep moves a meeting in one of the apps, and the update doesn’t happen in the other app. It still shows the old meeting time.

Teams often evaluate the integration by whether it connects at all, rather than how the tools communicate changes between each other. But connecting is the easy part. The rest is where the real test is.

Consider, for instance, if a meeting is rescheduled, an invitation is declined, someone cancels at the last minute, or a rep edits the meeting details from their phone instead of at their desk. The test then is whether the other system finds out quickly and whether it attaches the change to the correct contact record.

What tends to happen when it doesn't is that reps start losing trust in one of the two tools. Typically, they’ll continue to check the calendar for the real schedule and treat the CRM as something they update later, if at all. When that habit sets in, the data in the CRM falls behind, and nobody can say exactly when it all began to fall apart.

So, if you're evaluating CRMs for a team on Google Workspace, what's the one thing you'd test before you call the Calendar integration good enough? And has anyone been burned by one that looked fine in the demo?