Salto

Wondering whether Zendesk’s new Advanced AI tools are worth the cost for your team? Let’s crunch some numbers. ?? Cost of a Zendesk Agent Per Year (in USD)… Base salary: $33,000~ Pension contribution: $1,650 (5% of salary) National Insurance (or equivalent employer’s tax): $4,620 (14% of salary) Desk space: $3,600 ($300/mo) Zendesk license: $1,800 Total: $45K ?? Cost of Advanced AI Per Year (in USD)… Subscription: $50/mo Total: $600 With roughly 48 working weeks in a year and 40 working hours in a week, we can estimate that the average hourly wage of a Zendesk customer service agent in the US or UK is $23.25. That’s about $0.39 per minute. Advanced AI will cost you $0.31 per hour, per agent. Since the hourly cost of Advanced AI is roughly the same as the ‘per minute’ cost of an agent, Advanced AI really only needs to save your agent about a minute of work per hour to be worth the cost. If you’re finding Zendesk’s Advanced AI tools to be worth the investment for your team, let us know in the comments. We (and others) would love to hear from your firsthand experience!

Managing Salesforce permissions shouldn’t feel like a full-time job. Salto gives you an easier way to handle Permission Sets and Profiles while minimizing errors and saving your team time. In this blog post, we show you how you can use Salto to explore permissions, compare them across orgs, and even deploy only the permissions that are necessary. Read the full post here ?? https://hubs.ly/Q02YyqSQ0 #Salesforce #PermissionSets #ChangeManagement #DevOps

??8 Tips for Managing NetSuite User Roles ?? Making sure your NetSuite user roles are configured correctly is crucial not only for user experience, but also for the security of your organization. Overly permissive roles can expose sensitive information, but overly restrictive roles can hinder productivity. Here are some best practices to help you customize your NetSuite user roles and permissions more efficiently: ? Customize roles to align with job functions. This gives you granular control over user access and reduces security risks. ? Prioritize Role-Based Access Control (RBAC). Stick to the principle of least privilege by assigning only the permissions users truly need. ? Avoid role conflicts by analyzing responsibilities and enforcing clear access rules. ? Optimize forms for each role to improve efficiency and minimize errors. ? Grant appropriate currency permissions to users roles with the ability to modify transaction exchange rates. ? Leverage role comparison tools to identify discrepancies and streamline access. ? Future-proof customizations to adapt seamlessly to organizational changes. ? Avoid assigning built-in roles (except “Administrator” and “NetSuite Support Center”) to prevent vulnerabilities. These tips will help you manage roles like a pro while safeguarding your NetSuite environment. Which of these are you already doing? Got any other recommendations to share? Let us know below ?? #NetSuite #UserRoles #BestPractices #CloudERP

Ready to streamline your multi-org release process? Join our upcoming Salto demo featuring Dan Putman, where we’ll show you how to tackle promotions and back-promotions with ease ?? Register now and join us on November 20th! https://lnkd.in/ebcP8Yjq

We’re excited to announce our new partnership with 3RP - Oracle NetSuite Alliance Partner! Together, we’re committed to enhancing configuration management and deployment processes for our customers. By combining 3RP's expertise with Salto’s automated platform, we’re enabling fast, reliable, and risk-free deployments from Sandbox to Production environments. Read more about our partnership here: https://hubs.ly/Q02XWxbW0

Is your Zendesk support ready to scale? Join us Tuesday November 19th for a live webinar, where Salto Customer Engineer Scott Dixon and Zendesk Customer Success Director Tara Myles will dive into the strategies and tools you need to handle higher ticket volumes and more complex workflows with ease. Don’t miss your chance to learn from the experts and get your questions answered—sign up below! ??

?? Impact Analysis: The Essential Guide for Salesforce Admins Ever made a small tweak in Salesforce that seemed harmless but later caused ripple effects throughout your org? This is where impact analysis can make a world of difference. By identifying and assessing the impact of proposed changes to your Salesforce org, you minimize unexpected issues and set the stage for a smoother, more controlled deployment. Here’s how to approach impact analysis effectively: 1?? Map Dependencies Thoroughly – Before making any changes, identify related objects, fields, and automations to ensure nothing breaks downstream. It’s also important to assess the impact of changes on integrations connected to your Salesforce environment. To automate this mapping and get a clear view of all dependencies, you may also consider leveraging a tool like Salto. 2?? Simulate Changes in a Sandbox – Testing in a sandbox helps you see how changes will play out in real-world scenarios without affecting live data. It’s a crucial step that can help prevent costly mistakes before deploying changes to production. 3?? Document Everything – Keeping a detailed record of changes and their impacts is essential for ongoing maintenance and future updates. It also provides a valuable reference for stakeholders, helping your team understand what’s been modified (and why) and ensuring alignment across your entire team. Impact analysis isn’t just a “nice-to-have”—it’s essential for stability, efficiency, and smooth scaling in your Salesforce environment. With the right approach and tools, you can bring confidence and control to every change you make.

Scaling Zendesk operations can reveal hidden challenges that catch even the most experienced teams off guard. From poorly integrated third-party tools to compliance issues, there’s often a lot more to it than meets the eye. In this blog post, Zendesk consultant @Jude Kriwald uncovers these challenges and offers solutions so you can scale smoothly and create your best Zendesk environment to date. Read it below! ??

When it comes to building and sustaining a high-performing #NetSuite team, expert Eric T Grubaugh says a strong onboarding program is key. But what makes your onboarding program solid? And how do you build it? In this blog post, Eric outlines the steps you can take to develop an onboarding process that reliably produces effective, productive, and connected teams. Link in the comments! ??

Imagine going live with a #CPQ migration, only to discover critical errors that only became apparent after the fact. For example, you might realize an approved quote in your CPQ failed to trigger the necessary actions in your CRM, causing lost sales opportunities and increased operational costs. Where’d you go wrong? ?? Problem: Insufficient Testing Testing is a critical step that ensures your system functions as expected after migration. If not done correctly, you could end up with issues that only surface once you go live. If your CPQ system is integrated with other business systems (like your CRM), skipping detailed end-to-end testing could mean you miss critical issues in how these systems interact post-migration. ? How to solve it: - Develop a comprehensive testing plan - Conduct all testing in a sandbox environment using a variety of data sets and by simulating common customer interactions - Use iterative testing cycles; after each round of testing, review the results, identify any issues, and make necessary adjustments - Conduct a final round of testing that includes a full migration of a subset of data ?? TLDR; Proper testing is essential to ensure your CPQ migration works seamlessly across integrated systems. By simulating real-world scenarios in a sandbox environment, you can identify and fix potential issues before they disrupt your live environment.