Protecting VIP Customers
5 min read
TrustLens’s defensive features can occasionally produce false positives — legitimate customers caught by velocity rules, blocked at checkout because of an unusual order pattern, or incorrectly linked to fraud rings due to shared addresses. For your highest-value customers, even a single false positive can damage the relationship permanently. This walkthrough shows how to use TrustLens’s tools to protect your best customers from any unintended friction.
The Goal #
For VIP customers, you want:
- Never blocked at checkout
- Never caught by Card-Testing velocity rules
- Never penalized by Linked Accounts false positives
- Never held by automation rules
- Always fast-tracked through fulfillment
TrustLens provides multiple layers to achieve this; using them together is what produces robust protection.
Layer 1: Identify Your Top Customers #
The Customers list helps you find them:
- Open TrustLens → Customers
- Sort by Total Order Value descending
- Top 5%, 10%, or 20% — wherever you draw the line
Cross-reference with:
- Trust score (high — they should already be Trusted or VIP)
- Tenure (long — repeat buyers)
- Return rate (low — clean record)
- Disputes (zero or near-zero)
Layer 2: Allowlist Confirmed VIPs #
The strongest protection. Allowlisting:
- Locks the customer’s score at 100
- Forces segment to VIP
- Suppresses all negative signals — they cannot drop in segment regardless of future behavior
- Combined with VIP bypass: Card-Testing velocity rules never apply
To bulk-allowlist your top customers:
- Filter the Customers list to confirmed top customers
- Select with checkboxes
- Bulk Action: Allowlist
- Add admin notes documenting the decision (optional)
Be deliberate — don’t allowlist customers you don’t personally know are legitimate. The allowlist is a trust statement.
Layer 3: Verify VIP Customer Bypass Is Enabled #
Settings → Modules → Card Testing → VIP Customer Bypass
This setting is on by default. Confirm it:
- VIPs skip Card-Testing velocity rules
- Even during Panic Freeze, VIPs can complete checkout
- The bypass identifies VIPs by segment, so allowlisted customers are automatically protected
Layer 4: Exclude VIPs From Automation Rules #
Most enforcement-style automation rules should explicitly exclude VIPs:
- “Hold orders from Risk customers” rule should have condition
segment ≠ vip - “Block customers after dispute” rule should have condition
is_allowlisted = false - “Apply payment method controls” rules should have
segment ≠ vip
The double-check protects against edge cases where a VIP happens to match an enforcement condition.
Layer 5: Build VIP-Specific Automation Rules (Pro) #
Positive automation for VIPs:
VIP Fast-Track #
- Trigger: Order Placed
- Condition:
segment = vip - Actions: Tag order “vip-fast-track”; webhook to fulfillment system
VIP Segment Drop Alert #
- Trigger: Segment Changed
- Condition:
old_segment = vipANDnew_segment in [normal, caution, risk, critical] - Actions: Slack alert to customer success team — a VIP just dropped; investigate
VIP Recovery Recognition #
- Trigger: Segment Changed
- Condition:
new_segment = vip - Actions: Email to customer success — new VIP earned organically
Layer 6: Configure Pro Notifications #
Two Pro notifications protect VIPs:
Score Recovery Alert #
Fires when a previously-risky customer recovers significantly. Useful for spotting customers transitioning back to normal who might be candidates for proactive allowlisting.
High-Value Order Alert #
Fires on orders above a configured threshold. Lets you personally review and fast-track VIP orders even before they hit automation rules.
Layer 7: Document VIPs Internally #
Use admin notes liberally on VIP records:
- Why they’re VIP (lifetime value, strategic account, personal relationship)
- Verification history (e.g. “Confirmed identity via phone call on 2024-03-15”)
- Special handling instructions
- Contact preferences
The notes become institutional memory — when a new team member encounters the customer, they have context.
Layer 8: Quarterly VIP Audit #
Every quarter:
- Pull the list of allowlisted customers
- Sort by Last Order Date ascending — dormant customers first
- For each dormant VIP (no orders in 12+ months), decide whether to:
- Keep allowlisted (they might return)
- Remove from allowlist (likely churned; restore normal scoring)
- Add new candidates from your top customers list
The allowlist is a curated list, not a set-and-forget. Regular maintenance keeps it accurate.
Edge Cases #
VIP With Recent Signals #
An allowlisted VIP whose recent behavior has changed (refund spike, new shipping pattern) is still locked at score 100. You won’t see the signals on their profile because allowlist short-circuits scoring. To investigate:
- Temporarily remove from allowlist
- Force recalculation
- Review the underlying signals
- Re-allowlist if signals are spurious
VIP Disputing a Charge #
An allowlisted VIP filing a chargeback is a real event you want to know about, regardless of allowlist. The Chargeback Filed Alert notification fires for everyone — including allowlisted customers. Take the dispute as seriously as any other.
VIP Linked to a Fraud Ring #
If linked-accounts detection flags an allowlisted customer as linked to a Critical-segment account, the link is recorded but the VIP’s score isn’t affected (allowlist locks it). Investigate the linked account separately — it might be a household member who happened to enter the ring’s identity space.
What Allowlist Doesn’t Do #
- Doesn’t unblock an explicitly-blocked customer (block flag is independent)
- Doesn’t grant WooCommerce-specific privileges (no automatic discount eligibility, no free shipping)
- Doesn’t notify the customer
- Doesn’t prevent the customer from filing disputes or refund requests
Communicating With VIPs #
VIPs don’t need to know they’re VIPs in TrustLens — that’s internal. Use the segment to drive customer-facing experiences without revealing the underlying scoring:
- VIP-only email lists managed externally
- Loyalty program tiers driven by the same data
- Premium customer service workflows
Metrics to Track #
- VIP segment count (target: 2–10% of scored customers)
- VIP demotion rate per month (low = stable VIP population)
- VIP false-positive incidents (should be near zero with full setup)
- VIP lifetime value retention
