I signed up for the Early Access, will do.
1 Like
This is a great example of something I really would like to be able to do with a simple gmail or gsuite account in the core plans. Certainly think itās very legacy to not be able to sync client db to something like google, or the CRMs themselves. I figure picking and choosing CRMs would not only be more work, but then people requesting āwhy not xyzā, so I think just google / microsoft standard accounts would solve the issue because most legit CRMs sync to them.
For my example, Iām currently using Hubspot, and itād be very nice to be able to sync fields in syncro directly to hubspot. Currently itās burning up zaps through zapier. So at minimum, thank you for the zap integration! At least letās me shoe string things together haha.
Yep, Halo did require an onboarding fee.
The experience of going through the 10+ hours of onboarding via MS Teams (plus unlimited email onboarding) which included having all the complexity and customisation explained plus helping us to understand how our existing processes could be automated was amazing.
@Andy I know from other posts, that you will disagree with me, but after my starting experiences with both Halo and Syncro I would have preferred to have had paid onboarding with Syncro.
Agree, there shouldnāt be an additional cost for this.
Halo sends notifications of new tickets using their Azure Integrationā¦so the sent emails sit in the exchange mailbox in the sent items folder.
I see no value in that (though I have no issue with you if you do). Iām just tired of the SyncroMSP notification emails being quarantined as high risk for not being able to pass DMARC. I could exempt SyncroMSP domains from such checks, but that reeks of contributory negligence in a world where MSP RMMs are a high value target for BEC attackers.
3 Likes
Merely an observation at this stageā¦
But brain stormingā¦here are some possible benefits of using the Syncro Azure Integration instead of Syncro sending the email and pretending to be the MSPs domain, or using a BYO SMTP option.
Given all emails from Halo are sent via their Azure Integration a log of them being sent is kept in the O365 audit log. If a client says they didnāt receive the quote from Halo we triggered for esigning our T&Cs, then we can check the O365 message trace in EAC.
Maybe something went wrong, at the receiving email server, then we can easily obtain the email from the sent folder and then resend it manually.
If we like we can backup the sent emails.
In the future we may think of something useful to implement with Power Automate to perform some action when the emails created by Halo hit the sent folder (after being sent to the client).
1 Like
How many post have we seen of people asking the same questions because they donāt know something exist or doesnāt exist. Switching RMM and PSA is a huge deal and to not have someone holding your hand through the process can be intimidating. Iāve seen post of people transition over a long periods of time, people that will use the RMM only for a year+ because they are afraid to start using the billing and ticketing system on the PSA side because they donāt fully understand it.
1 Like
Question on the Azure sync. Letās say we have a client with 50 MS365 BP users and 5 Exchange only. We already sync that via the Pax8 integration for billing purposes. But what about user sync? Since we charge per user, would it be possible to setup a line item dynamically tied to only the business premium licenses for user billing?
3 Likes
Yes, it will pull licenses and you can add as many employee counters as needed to capture every license type as needed for dynamic billing purposes.
Ok thatās slick. Thanks for clarifying.
1 Like
Ian, I believe that EVERYONE using Syncro is a Business. Therefore we all need Splashtop Business with multi-monitor support; the exception will be multiple techs per session.
5 Likes
This is perfectly said. Iām only a month old and I feel like I just made a terrible mistake. Roadmap sounds like yellow brick roadā¦
No we arenāt, we are an internal IT department and itās annoying there are not PSA for actual IT teams.
In any case, multiple windows for the remote access is needed in todayās world.
2 Likes
that you are walking down in the dark, because Syncro refuses all requests to publish a roadmap.
The best we have managed to achieve is the priorities for the coming quarter. These are welcome, but hardly a roadmap.
Yeah but if priorities just mean a new tier thatās going to cost me more Iām out.
6 Likes
I have a list of features that I would like to see added to Syncro. None of them are on this list.
Iād like to see improvements to patch management, mainly, quicker insights into which systems are missing patches. Also, built in network scanning.
Any higher than what I am currently paying and Iām looking at more advanced solutions. At $180.00 a user, you are pricing yourself alongside more robust solutions.
You will start seeing clients jump to other platforms at that point.
I donāt think youāll receive a lot of positive feedback with this news. I think many of us feel like these features are typically standard with an RMM platform and instead of adding it to compete, Syncro is adding them as a way to justifying raising costs.
I am concerned that development on the base platform will stop and all QOL features will be behind the Team Paywall.
4 Likes
Itās moving at a snailās pace as is. Syncro used to be the top when it came to releasing features that userās want. Iām looking around and seeing release schedules every couple of weeks, roadmaps, and user voting systems. Iāll never understand the policy of being hush about development and not having a public roadmap. Their quarterly post have a lot of words on them, but hardly any content when you compare them to others. Just saw one that had 15 items listed on their quarterly report and Syncro is still listing RTF stuff, but they were able to get ticket tags out the door even though no reporting, no automations, but hey, it made the list! There is nothing wrong with slow development if the things released are high quality and thoroughly tested, but that just hasnāt been the case. Ticket tags came with a couple of bugs that weāve seen, easy ones that should have never made it through QC. The Teams tier is still built on the same shaky base as the Core tier, so itās not resolving the root of the issues.
4 Likes
I agree with you. I would much rather have quality releases than rushed feature sets riddled with bugs.
None of this is new tech so I donāt see the need for discretion with their direction either. No discernable competitive advantage that I can see with this approach.
Iād like to see the platform catch up a bit before I even consider the proposed price point for the Team tier.
Syncro has spent the last year overcoming technical debt because of the move to AWS, I hope to see more rapid development on core functionality. Like ACH (PAD in Canada) other than Worldpay, which doesnāt work in Canada. I tried for weeks to get someone to call me itās like Canada doesnāt exist.