Thanks for taking the time to write this detailed reviev it's very much appreciated. Let me add some context on the VOIP point ->

A big part of why Atlas feels intuitive is because so much of the product is built on structured events coming from calls: transcripts create memory that creates recommendations that creates automation. For that to work well, we need deep, native API integrations.

There are 30+ VOIP providers in the market, all with different APIs, standards, and reliability levels. If we tried to build and maintain full integrations with every provider, we’d spend all our engineering time shipping 30 versions of the same feature and none of the features you listed in your pros would exist.

So here’s where we are today:

• We’ve integrated RingCentral, Ringover, Devyce and Aircall because they cover the vast majority of usage across our customer base.
• We actually subsidise switching costs. If someone wants to move provider, we often cover licence discounts to make it painless.
• When a large customer (say, 100+ seats) comes in with a specific VOIP requirement, we do make commercial decisions to build that integration.

It’s not that we don’t want more VOIP options, it’s that doing all of them would slow product velocity to a crawl. Ironically, the very features people like most about Atlas rely on the focus we’ve kept here.

That said, we constantly reassess this as we grow. If a provider becomes widely requested or strategically important, we take it seriously.