CrawlDex
Preflight detail

linkedin.com

customer_support.account_or_premium_help

degraded recipe://linkedin.com/customer_support.account_or_premium_help/public-preflight-v1
Hold / Collect evidence first

Do not trust this route yet

The current evidence set is too thin for a confident agent decision.

Next: Run a canary or submit a trusted outcome before allowing an agent to attempt this unsupervised.
75AES
75% outcome rate
Evidence and trust

low trust

32%
basisBased on 2 evidence samples from catalog reporters.2
sourceSources: public web observation.
nextTreat this as directional until trusted canaries or operator reports arrive.
Confidence low 28%
Evidence 2 public web observation
Freshness 0d fresh
Blockers 2 known friction
Recipe

LinkedIn official public help/contact source -> select account, order, billing, refund, warranty, complaint, or service issue -> collect required identifiers and stop before submitting any support request, chat, claim, appeal, or account-recovery action.

active
recipe://linkedin.com/customer_support.account_or_premium_help/public-preflight-v1
  1. Open the documented public path for LinkedIn: LinkedIn official public help/contact source -> select account, order, billing, refund, warranty, complaint, or service issue -> collect required identifiers and stop before submitting any support request, chat, claim, appeal, or account-recovery action. Public source or help surface is visible.
  2. Check the listed blockers and policy constraints before entering account, payment, booking, or cancellation state. login_required, human_handoff_required, policy_parseable, confirmation_email_clean
  3. Stop before any irreversible or user-sensitive action and ask for explicit approval. User approval is captured before final action.
Human approval
Keep the user present for authentication. Do not request, store, or replay credentials or one-time codes.
Do not cross
  • Use public help/contact pages only until the user is present and has authorized account-specific support.
  • Do not submit contact forms, support chats, warranty claims, refunds, complaints, chargebacks, or account-recovery requests during corpus collection.
  • Capture required information, escalation path, and case-ID/confirmation expectations before any user-approved handoff.
Success signals
  • Support case number or reference ID
  • Confirmation email or transcript
  • Visible ticket, refund, warranty, complaint, or account-recovery status
Dimension scores

Why the route scores this way

reachability 63
navigability 75
task completability 63
transactability 75
recoverability 63
policy parseability 75
trust safety 75
efficiency 63
Issue flags

Known blockers

login_requiredhuman_handoff_required
Policy notes
public pathLinkedIn official public help/contact source -> select account, order, billing, refund, warranty, complaint, or service issue -> collect required identifiers and stop before submitting any support request, chat, claim, appeal, or account-recovery action.
task familysupport
seo angleLinkedIn customer support preflight for AI agents: account gates, handoffs, and case signals
confidence noteOfficial public support/help source was used for a read-only preflight. Account-specific support, refunds, disputes, recovery, claims, and final submissions require user-present authorization.
launch setfirst 300 public preflight
Recommended actions

Remediation queue

  • mediumagent
    Use public help/contact pages only until the user is present and has authorized account-specific support. Keeps the agent inside documented, reversible, user-approved boundaries.
  • mediumagent
    Capture handoff evidence and pause before accepting retention offers. Keeps user intent explicit during adversarial cancellation flows.
Agent handoff

Copy this into an agent runbook

customer_support.account_or_premium_help
Before attempting customer_support.account_or_premium_help on linkedin.com, check CrawlDex. Current verdict: Collect evidence first. Run a canary or submit a trusted outcome before allowing an agent to attempt this unsupervised.
curl -sS -X POST /api/v1/preflight \
  -H 'content-type: application/json' \
  -d '{"site":"linkedin.com","task":"customer_support.account_or_premium_help","agent_profile":{"stack":"browser-use","browser_runtime":"playwright"}}'
Preflight contract 
{
  "site": "linkedin.com",
  "task": "customer_support.account_or_premium_help",
  "agent_profile": {
    "stack": "browser-use",
    "browser_runtime": "playwright"
  }
}