This discovery framework is designed to help facilitate a collaborative conversation regarding Salesforce Shield. By exploring these operational scenarios, Pet Insurance Companies can accurately assess internal workflows and identify how specific Salesforce Shield capabilities can support their unique clinical and administrative needs, starting with areas of highest impact to practice revenue and patient care.
How is the organization mitigating the financial and reputational risks associated with unauthorized internal access to policyholder financial data and pet health records?
Scenario A: Unseen Data Exfiltration
"We recently discovered a data leak where an internal user accessed and exported premium payment details, resulting in severe regulatory scrutiny and loss of client trust."
Scenario B: Limited Audit Visibility
"We rely on standard login tracking, but we lack visibility into what specific records or sensitive fields employees view once they access the system."
As the company scales operations across multiple states with varying insurance regulations, how do you ensure ten-year data retention compliance for policy disputes?
Scenario A: Overwritten Historical Data
"We face massive penalties because our system overrides old policy data, making it impossible to prove what coverage a pet had five years ago during a legal dispute."
Scenario B: Manual Compliance Reporting
"We store old policies in a separate, offline database, but querying it during a state audit is a slow, manual process that ties up our administrative staff."
What mechanisms are currently deployed to track and audit manual overrides to pet insurance premium rates or deductible thresholds?
Scenario A: Untraceable Field Adjustments
"Agents are occasionally changing deductible fields to appease frustrated customers, and we have no way to trace who made the change or when it occurred."
Scenario B: Inadequate Retention Limits
"We track field changes for a few months, but standard history tracking drops off too quickly to support our annual regulatory audits."
How do claims administrators protect sensitive veterinary medical records and policyholder payment data from internal misuse?
Scenario A: Unrestricted Record Browsing
"We cannot confidently state that our claims handlers are only viewing medical records for cases they are actively assigned to work on."
Scenario B: Delayed Access Reporting
"We trust our staff, but if a policyholder asks for an access log of their pet's claim file, generating that report takes our IT team weeks."
To what extent is policyholder Personally Identifiable Information (PII) encrypted at rest without degrading the performance of claims routing rules?
Scenario A: Broken Automated Workflows
"Our current encryption method breaks our automated claims routing, forcing us to choose between data security and operational efficiency."
Scenario B: All-or-Nothing Encryption
"We encrypt data at the volume level, but we have no granular control over specific sensitive fields like bank account numbers for claim payouts."
How is the technology team monitoring API consumption from external veterinary clinic portals and pet quote engines to prevent malicious extraction?
Scenario A: Exploited Integrations
"A third-party veterinary portal was compromised, and attackers used our API to rapidly drain thousands of policyholder records before we noticed the spike."
Scenario B: Reactive Usage Monitoring
"We look at API limits at the end of the month, but we lack real-time visibility into which external integrations are consuming the most data."
When underwriting rules change based on new breed-specific risk models, how do you preserve the historical state of a policy at the exact time it was issued?
Scenario A: Loss of Contextual History
"Whenever we update breed risk categories, it overwrites the historical data, making it impossible to evaluate the accuracy of our past underwriting decisions."
Scenario B: Manual Data Snapshots
"We take manual snapshots of policies at renewal, but we lose visibility into any mid-term adjustments made by agents."
How do actuaries verify the integrity of historical claim frequency and payout data when developing new pricing models for specific pet breeds?
Scenario A: Skewed Predictive Models
"Our pricing models are skewed because historical payout fields were accidentally updated in bulk, and we cannot revert to the original, accurate figures."
Scenario B: Isolated Data Warehousing
"We export claims data monthly into a separate data warehouse to ensure it does not get changed, which creates frustrating data silos."
How does the organization ensure that support agents can verify policyholder identities without exposing full payment details on their screens?
Scenario A: Exposed Financial Data
"Support agents can see full credit card numbers and bank routing details in plain text when verifying a customer's payment method, which is a massive liability."
Scenario B: High-Maintenance Custom Code
"We use custom code to hide certain fields, but it requires constant developer maintenance every time we add a new payment type."
What processes are in place to audit the actions of claims adjusters who frequently download large volumes of veterinary invoices?
Scenario A: Malicious Offboarding Behavior
"An adjuster resigned and downloaded hundreds of confidential veterinary claim files on their last day, and we only found out months later."
Scenario B: Blind Spot in File Access
"We review a random subset of claims each month to check for proper procedure, but we cannot proactively see if an adjuster is reviewing claims outside their territory."