crm-onboarding

Guide CRM integration scoping, setup, and execution with mapping and configuration steps.

2|1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/VoicenterTeam/claude-marketplace --skill crm-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crm-onboarding
Source: https://github.com/VoicenterTeam/claude-marketplace/tree/main/plugins/voicenter-api/skills/crm-onboarding
Command: npx skills add https://github.com/VoicenterTeam/claude-marketplace --skill crm-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide for planning and executing CRM integrations, streamlining the process and reducing the risk of errors.

Core Features & Use Cases

  • CRM Type Scoping: Helps identify whether the CRM is on-premise or web-based and which components are applicable.
  • Entity & Field Mapping: Guides in mapping CRM data structure for efficient integration.
  • Click2Call Setup: Walks through the Click2Call process including station code setup and HTTP request requirements.
  • Screen Pop Configuration: Decides ownership and trigger methods for screen pops, whether CRM or Voicenter-owned.
  • Call History Logging: Determines the best method for logging call history between CDR Notification and Call Log API.

Quick Start

/activate crm-onboarding --start-integration "Customer CRM Name" --crm-type "On-Premise/Web-Based" --station-code "YourStationCode" --screen-pop "OwnershipOption" --call-history "LoggingOption"

Frequently Asked Questions about crm-onboarding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a CRM integration with Click2Call and screen pop features?

Planning a CRM integration involves detecting the CRM type, mapping entities and fields, configuring Click2Call, designing screen pop architecture, and selecting a call history logging method to ensure seamless service execution.

What is the difference between CDR Notification and Call Log API for call history logging?

When configuring call history logging, CDR Notification pushes call event data to your CRM in real-time, whereas the Call Log API requires the CRM to actively query and retrieve call records from the server.

How do I set up Click2Call configuration with station codes and HTTP requests?

Setting up Click2Call requires defining a station code and structuring HTTP requests to bridge the CRM interface with the telephony platform, enabling users to initiate outbound calls directly from CRM records.

Does CRM onboarding support both on-premise and web-based CRM systems?

CRM onboarding supports both on-premise and web-based CRM systems. The integration process begins with CRM type detection to evaluate the environment and determine which components, like Screen Pop and Click2Call, are applicable.

How do I map CRM entities and fields for a telephony integration?

Mapping CRM entities and fields requires aligning your CRM data structure with telephony endpoints to ensure screen pop triggers and call history logs accurately match customer records during integration execution.

When should I choose CRM-owned screen pop architecture over Voicenter-owned?

Choose CRM-owned screen pop architecture when your CRM can natively process trigger stage rules, and select Voicenter-owned when relying on external HTTP requests to push call data directly to the CRM interface.