Mint® Moments – February

Expanding Visibility Where It Matters

For many growing organisations, a single Salesforce® object often serves multiple teams, processes and reporting needs. But with standard field history tracking capped at just 20 fields per object, you’re forced to pick what to monitor – leaving critical insights unseen and audit trails incomplete.

One client we recently partnered with faced this exact challenge. Teams relied on the same core objects but had different priorities and compliance needs. The platform’s limits meant valuable change data was lost – visibility dropped, manual checks increased and reporting confidence suffered.

Our solution breaks through that ceiling. With an extended tracking framework, the client now monitors far more fields through a clean, intuitive interface. Reporting is sharper, field audit history is comprehensive, and historical record archiving is fully under control. Analysing changes is quick, actionable, and fully auditable – no more blind spots.

This is a practical enhancement with immediate impact: teams gain transparency, decision-making improves and governance strengthens. Even better, the solution rolls out fast – typically in just 2–3 hours.

If greater visibility sounds valuable, reach out to support@mintcrm.co.uk and we’ll help you get started.

How Bender Inc Supercharged Their Sales with CPQ

Bender Inc is a global leader in electrical safety, delivering complex solutions with precision. To match their ambition, they partnered with Mint® to implement Salesforce® CPQ – creating a faster, smarter quoting process that keeps their sales team ahead of the curve with professional quotes in minutes, not hours.

The results speak for themselves:

• Faster Quotes – no more manual errors
• Higher Productivity – sales reps focus on selling, not formatting
• Better Insights – managers see real-time pipeline and pricing data

As Bender’s Customer Experience Director said: “This CPQ solution has transformed our quoting. It’s quicker, more consistent, and reflects exactly how we work. Mint® nailed it.” 

Want to read more click here.

If your team struggles with slow or inconsistent quotes, a CPQ solution could be your game-changer. Ready to see how it works for you? Let’s talk.

Lessons from the Odido Incident

A recent cyber‑security story has caught the attention of organisations everywhere including here at Mint®. Dutch telecommunications provider Odido, formerly part of T‑Mobile Netherlands, experienced a significant cyberattack in early February 2026 that exposed the personal information of over six million customers stored in its Salesforce® system.

What makes this case particularly instructive for Salesforce® users wasn’t a flaw in the platform itself but rather how attackers gained access. The perpetrators used social engineering techniques, including phishing and impersonation of internal IT support, to trick customer service employees into surrendering sensitive credentials and authorisation codes.

So What Happened?

• Hackers targeted individual employees with phishing attacks to steal login details.
• They then posed as internal IT staff to bypass multi‑factor authentication (MFA).
• This allowed them to access Odido’s Salesforce® instance and scrape customer data.

While Odido quickly shut down the unauthorised access and engaged external cybersecurity experts, this incident underscores a simple truth: no platform – even one as robust as Salesforce® – is immune to threats that exploit the human element.

Why This Matters to You

For Mint® clients using Salesforce® or planning digital transformation projects, this serves as a timely reminder that security isn’t just about technology – it’s about people, permissions and processes. Here are a few key areas to review:

1. Internal Communication & Security Culture
   Phishing and social engineering attacks are among the most effective tactics threat actors use. Regular, up‑to‑date training helps teams recognise suspicious activity before it becomes a breach.
2. User Permissions & Least‑Privilege Access
   Restricting what users can see and do – especially around sensitive customer records – limits the potential impact of compromised credentials. Conducting an audit of Users in the system and their permissions can help identify areas to tighten up.
3. Connected Apps & Installed Tools
   Review all apps connected to your environment. Remove unused or unknown applications and ensure only authorised tools with clear purposes and governance are in place.
4. IT Security Policies & Audit Practices
   Regular audits of login methods, MFA enforcement, session management and abnormal access patterns aren’t optional; they’re essential parts of a resilient security posture.

Bottom Line

The Odido incident isn’t a reason for alarm – but it is a call to action. It highlights once again that security is a shared responsibility: technology platforms provide strong foundations, but organisations must build a secure structure on top of them with clear communication, governance and vigilant review practices.

If you’d like support with reviewing your Salesforce® security posture, internal user governance, or connected app policies, Mint® is here to help.

Keep Your Data Serving Only the Finest

As any support team will tell you, great CRM performance starts with great data. One of the simplest yet most powerful ways to protect data quality in Salesforce® is by utilising standard Duplicate Rules. They act as a gatekeeper, identifying potential duplicates before they enter your system and helping teams maintain a single, reliable view of every customer.

The benefits are immediate and far-reaching. Cleaner data means more accurate reporting, better segmentation and a smoother experience for both users and customers. It also reduces time spent untangling records, allowing teams to focus on meaningful work instead of maintenance.

The best part? Duplicate Rules are quick and straightforward to configure. With just a few thoughtful decisions, you can introduce a robust safeguard that works quietly in the background while delivering long-term value.

 Duplicate Rules Quick Start Checklist

1. Identify Key Fields – Decide which fields matter most for matching (e.g., Email, Phone, Company).
2. Create Matching Rules – Define what counts as a potential duplicate.
3. Configure Duplicate Rules – Choose whether to block, warn or allow with alerts.
4. Test with Real Scenarios – Validate using sample records to ensure the logic works as expected.
5. Activate & Monitor – Turn rules on and review reports to refine over time.

Putting these controls in place is a small step that pays dividends in efficiency, trust, and confidence across your organisation.

Reach out to Support if you’d like help in getting these set up or want to talk broader data cleaning options.