# CRM Onboarding

> CRM integration scoping & onboarding playbook. Use when scoping a NEW CRM integration, running a discovery/feasibility/spec meeting, or choosing between API vs Chrome extension vs local BAT, Push vs Pull, and CRM-owned vs Voicenter-owned screen pop. Covers: CRM type detection (on-premise vs web), entity/field mapping, Click2Call station-code setup, screen pop architecture (who owns it), trigger-stage rules (ring/answer/hangup), call history method (CDR Push vs Call Log Pull), and full decision checklist. Trigger on: new CRM, CRM onboarding, integration spec, feasibility, station code, screen pop ownership, on-premise vs web CRM, Push vs Pull.

## Facts
- Page: https://tashan.sh/capability/skill-voicenterteam-crm-onboarding
- tashan id: skill:VoicenterTeam/crm-onboarding
- Source: https://github.com/VoicenterTeam/claude-marketplace
- Type: skill
- Category: other
- tashan score: not scored (catalogued only — too little public evidence)
- Adoption: 9.0
- Upkeep: 96.0
- Freshness: 91.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- License: MIT
- Official: no

## Install

```sh
cp -r crm-onboarding ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-08-20 by tashan (https://tashan.sh) from public evidence. Scorer s5.