원클릭으로
productive-dialer
Manage auto-dialer campaigns via the Voicenter Dialer API — add/remove destinations, control campaigns, manage agents
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Manage auto-dialer campaigns via the Voicenter Dialer API — add/remove destinations, control campaigns, manage agents
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Designs the structural skeleton of a Voicenter Bot via interview. Use this skill when the user wants to create, design, scope, or modify a Voicenter voice/chat bot — phrases like "design a bot", "create an agent spec", "build a Voicenter bot", "patch this bot", "add an intent", "change the bot's persona", "modify the flow graph", or any reference to the Agent Spec Designer / Skill 1 in the Voicenter bot generation pipeline. Produces an Agent Spec markdown file (sections 1-4, 4.5, section 5 stubs, section 6 initial, section 7 init). Two named entry modes — greenfield (no spec attached) and patch (spec attached). Does NOT author per-intent language content (validationPrompt, post-execution intentInstructions) — that's Skill 2 (Intent Detail Author). Does NOT emit wire-format JSON — that's Skill 3 (JSON Assembler).
Assembles a fully-detailed Voicenter Agent Spec into Bot JSON wire format — the final mechanical step in the three-skill pipeline. Use this skill when an Agent Spec exists with all section 5 entries marked `[detailed]` and the user wants the deployable JSON. Trigger phrases include "run Skill 3", "assemble the JSON", "emit the bot JSON", "publish the bot", "build the wire-format", "Skill 3 (JSON Assembler)", or any direct continuation from Skill 2's completion handoff. Produces a single `bot-<name>-<date>.json` file plus a banner identifying every fail-loud sentinel and any drift between spec section 6 and what Skill 3 regenerated. Refuses to assemble if any intent is still `[structural]` or `[detailed-revisit]`, or if the spec deviates from the strict template (Doc 2 §3.7). Runs the §15.4 cross-reference pass — 23 checks (8 §15.4 + 3 Compass + 3 botIntents-role + 1 duplicate-global-intent + 8 field-placement doctrine), checks 1–7, 11–13, 15, and 16–21 blocking. Does NOT author any text content (Skills 1 and
Authors the per-intent language content of a Voicenter Agent Spec — slot descriptions, validationPrompt, post-execution intentInstructions, and RT-specific Configuration text. Use this skill when an Agent Spec exists with section 5 entries marked `[structural]` or `[detailed-revisit]`, and the user wants to fill them in. Trigger phrases include "run Skill 2", "detail the intents", "fill in the per-intent fields", "Skill 2 (Intent Detail Author)", or any direct continuation from Skill 1's handoff hint. Walks intents in user-confirmed batches with a checkpoint after each batch. Reactivable — invoke as many times as needed; spec state is the resume point. Does NOT modify the structural skeleton (sections 1, 2, 3, 4, 4.5.1/.2/.4) — that's Skill 1 (Agent Spec Designer). Does NOT emit wire-format JSON — that's Skill 3 (JSON Assembler).
Pull call detail records (CDR) from Voicenter using the Call Log API
Receive and handle CDR push notifications from Voicenter after every call ends
Initiate or terminate outgoing calls using the Voicenter Click2Call API
| name | productive-dialer |
| description | Manage auto-dialer campaigns via the Voicenter Dialer API — add/remove destinations, control campaigns, manage agents |
Language. Reply in the user's language: detect what they write — Hebrew→Hebrew, English→English — and mirror it, switching if they switch mid-conversation. This shapes your prose, your questions, and your
AskUserQuestionoption labels only. It does not change the artifacts you produce — identifiers, JSON keys, BCP-47 language codes, API field names, and other data stay exactly as specified.
Help the developer integrate the Voicenter Productive Dialer API — manage campaigns, upload call destinations, control campaign state, and manage agent assignments from their CRM.
Use this skill when the user wants to:
VOICENTER_API_CODE=your_api_token_here
https://api.voicenter.com/ForwardDialer/Dialer/
All methods use POST-JSON. Authentication via Code field.
Code (not the name) in all subsequent calls.// Request
{ "Code": "MY_API_CODE" }
// Response
{
"ErrorCode": 0,
"Description": "OK",
"Data": [
{
"Name": "Campaign1",
"StatusName": "Enabled",
"TotalPendingCalls": 23,
"TotalAwaitingCalls": 23,
"MaxPriority": 1,
"MinPriority": 1,
"Code": "CAMPAIGN_CODE_HERE"
}
]
}
StatusName: "Enabled" = active, "Disabled" = stopped.
TotalAwaitingCalls for queue depth.TotalPendingCalls.URI: https://api.voicenter.com/ForwardDialer/Dialer/AddCall
{
"Campaign": "CAMPAIGN_CODE",
"Target": "972501234567",
"CustomerName": "John Doe",
"CallerID": "0722776772",
"Priority": 42,
"OriginateTime": 1702750000,
"IsDateLocal": "true",
"IgnoreDncStatus": "true",
"CustomData": {
"var_LeadID": 1234567,
"var_LeadSource": "Facebook"
}
}
| Field | Required | Description |
|---|---|---|
Campaign | ✅ | Campaign code from GetCampaignList |
Target | ✅ | Phone number (E.164 format; international prefix required for non-Israeli numbers) |
Code | ✅ | API authentication token |
CustomerName | ❌ | Customer name shown to agent |
CallerID | ❌ | Outbound caller ID shown to customer — must be a number in your account |
Priority | ❌ | Higher value = dialed first |
OriginateTime | ❌ | Schedule for future dial (Epoch time). Must include IsDateLocal. |
IsDateLocal | ❌ | "true" = use account's local timezone. "false" = GMT+0. Recommended: "true". |
IgnoreDncStatus | ❌ | "true" = bypass Do-Not-Call service |
CustomData | ❌ | Key-value pairs passed to Pop-Up Screen and CDR records |
URI: https://api.voicenter.com/ForwardDialer/Dialer/AddCallsBulk
Send an array of destination objects (same fields as AddCall):
[
{
"Campaign": "CAMPAIGN_CODE",
"Code": "MY_API_CODE",
"Target": "972501234567",
"CustomerName": "John Doe",
"Priority": 1,
"CustomData": { "var_LeadID": 111 }
},
{
"Campaign": "CAMPAIGN_CODE",
"Code": "MY_API_CODE",
"Target": "972501234568",
"CustomerName": "Jane Doe"
}
]
Limits:
"async": true to force detailed response (max 3,000)// Response
{
"ErrorCode": 0,
"Description": "OK",
"AddResult": [
{ "Target": "972501234567", "ErrorCode": 0, "Description": "OK" },
{ "Target": "972501234568", "ErrorCode": 0, "Description": "OK" }
]
}
URI: https://api.voicenter.com/ForwardDialer/Dialer/RemoveCall
{ "Campaign": "CAMPAIGN_CODE", "Code": "MY_API_CODE", "Target": "972501234567" }
URI: https://api.voicenter.com/ForwardDialer/Dialer/ClearCampaignCalls
{ "Campaign": "CAMPAIGN_CODE", "Code": "MY_API_CODE" }
// Start
// URI: https://api.voicenter.com/ForwardDialer/Dialer/StartCampaign
{ "Campaign": "CAMPAIGN_CODE", "Code": "MY_API_CODE" }
// Stop
// URI: https://api.voicenter.com/ForwardDialer/Dialer/StopCampaign
{ "Campaign": "CAMPAIGN_CODE", "Code": "MY_API_CODE" }
// Request: { "Campaign": "CAMPAIGN_CODE", "Code": "MY_API_CODE" }
// Response: { "Data": [{ "Member": "SIPSIP1", "DisplayName": "John Doe" }], "ErrorCode": 0 }
// URI: /AddMember
{ "Campaign": "CAMPAIGN_CODE", "Code": "MY_API_CODE", "Member": "SIPSIP1" }
// Response: { "Data": { "TotalAdded": 1 }, "ErrorCode": 0 }
// URI: /RemoveMember
{ "Campaign": "CAMPAIGN_CODE", "Code": "MY_API_CODE", "Member": "SIPSIP1" }
// Response: { "Data": { "TotalRemoved": 1 }, "ErrorCode": 0 }
URI: https://api.voicenter.com/ForwardDialer/Dialer/GetCampaignPendingCalls
// Response
{
"ErrorCode": 0,
"Data": {
"Campaign": { "Name": "Campaign1", "StatusName": "Enabled", "TotalPendingCalls": 4, "Code": "..." },
"Calls": [
{
"Phone": "972501234567",
"CustomerName": "John Doe",
"Priority": 42,
"OriginateTime": 1602819000,
"CallStatus": { "Status": 1, "Description": "Pending" },
"CustomData": { "var_LeadID": "1234567" }
}
]
}
}
const DIALER_BASE = 'https://api.voicenter.com/ForwardDialer/Dialer';
const CODE = process.env.VOICENTER_API_CODE!;
async function dialerRequest<T>(method: string, body: object): Promise<T> {
const res = await fetch(`${DIALER_BASE}/${method}`, {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ Code: CODE, ...body }),
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const data = await res.json();
if (data.ErrorCode !== 0) throw new Error(`Dialer ${method} error: ${data.Description}`);
return data;
}
// Full campaign workflow: get campaigns → upload leads → start
const { Data: campaigns } = await dialerRequest<any>('GetCampaignList', {});
const campaignCode = campaigns[0].Code;
const leads = [
{ Campaign: campaignCode, Target: '972501234567', CustomerName: 'John', Priority: 1, CustomData: { var_LeadID: '101' } },
{ Campaign: campaignCode, Target: '972501234568', CustomerName: 'Jane', Priority: 2, CustomData: { var_LeadID: '102' } },
];
await dialerRequest('AddCallsBulk', leads);
await dialerRequest('StartCampaign', { Campaign: campaignCode });
// Later — stop and clear
await dialerRequest('StopCampaign', { Campaign: campaignCode });
await dialerRequest('ClearCampaignCalls', { Campaign: campaignCode });
| ErrorCode | Description |
|---|---|
| 0 | OK |
| 1 | Invalid campaign code |
| 2 | Missing required field |
| -2 | Phone number format invalid |
GetCampaignList first — the Code in the response is the campaign identifier, not the name.OriginateTime + IsDateLocal: "true" lets you schedule future callbacks — great for "call me back at 3 PM" CRM features.CustomData values flow through to the Pop-Up Screen and CDR Notification — use them to carry CRM lead IDs and source attribution.type: "ProductiveCall Leg1/Leg2" — filter with cdrTypes: [14, 15] in the Call Log API.Member when adding agents to a campaigncdrTypes: [14, 15]