---
name: voicenter-Dashboard
description: "Knowledge base of Voicenter's public support center (מרכז התמיכה, voicenter.co.il), covering the Dashboard/Monitor interface, all monitoring report templates (דוחות ותרשימים, template numbers/names), Cpanel management, call history (פירוט שיחות), Softphone, Auto-Dialer, Chrome extension, networks, call recording storage, data security, account setup, SSO, CRM integration, mobile access, VoiceBot, and AI call analysis — as documented for end users (not the developer API). Trigger on: דוחות ניטור, דשבורד, דוח דשבורד, מוניטור, תבנית דוח, report template, מרכז תמיכה, support center, Voicenter dashboard, how does X report work, מה זה הדוח, Cpanel, פירוט שיחות, סופטפון, חייגן אוטומטי, תוסף כרום, SSO, ניתוח שיחות AI. Use for user-facing 'how does this feature/report work' questions about the Voicenter platform, as opposed to voicenter-api which covers developer API integration."
---

# Voicenter Dashboard & Support Center Knowledge Base

This skill is a local, searchable snapshot of Voicenter's public support center (`https://www.voicenter.co.il/מרכז-תמיכה`). It exists because that content lives inside the company's Umbraco-driven site as a client-rendered Nuxt app — there is no public content API — so it was crawled once and converted into local markdown reference files.

Use this skill to answer **end-user / "how does this feature work"** questions (what a report shows, how the Dashboard is structured, how Cpanel/SSO/CRM/Softphone work from a user's perspective). For **developer API integration** questions (endpoints, auth, request/response formats), use the `voicenter-api` skill instead.

## Category Index

| Category (Hebrew slug) | Topic | Items | Reference file |
|---|---|---|---|
| דאשבורד | Dashboard / Monitor — **all monitoring report & chart templates**, template numbers/names, real-time vs. standard reports, editing/exporting/emailing reports | 193 | `references/דאשבורד.md` |
| סיפאנל | Cpanel management interface | 102 | `references/סיפאנל.md` |
| תוסף-כרום | Chrome extension | 21 | `references/תוסף-כרום.md` |
| רשתות | Networks | 20 | `references/רשתות.md` |
| פירוט-שיחות | Call history (פירוט שיחות) | 17 | `references/פירוט-שיחות.md` |
| חייגן-אוטומטי | Auto-dialer | 17 | `references/חייגן-אוטומטי.md` |
| crm | CRM integration | 15 | `references/crm.md` |
| ניתוח-שיחות-AI | AI call analysis | 5 | `references/ניתוח-שיחות-AI.md` |
| אחסון-הקלטות-שיחה | Call recording storage | 10 | `references/אחסון-הקלטות-שיחה.md` |
| אבטחת-מידע | Data security | 9 | `references/אבטחת-מידע.md` |
| סופטפון | Softphone | 13 | `references/סופטפון.md` |
| Voicebot | VoiceBot | 7 | `references/Voicebot.md` |
| תהליך-הקמה | Account setup | 5 | `references/תהליך-הקמה.md` |
| SSO | Single sign-on | 3 | `references/SSO.md` |
| mobile | Mobile access | 2 | `references/mobile.md` |

`references/_toc.json` has the same table as structured data.

## How to Use This Skill

1. Identify the relevant category/categories from the table above based on the user's question. Most "which reports exist" / "what does report X show" questions belong in `references/דאשבורד.md`.
2. **Grep first, read second**: these reference files can be large (the Dashboard one is ~150KB / 193 items). Use grep/search for the report's template name, template number, or keyword before reading the whole file, then read just the matching section.
3. Each item in a reference file follows this shape:
   ```
   ### <title>
   **קטגוריה:** <sub-category, e.g. "ביצועי נציגים">
   <full description — for report items this includes "תבנית מספר" (template #), "שם תבנית" (template name), and "תיאור הדוח" (what the report shows)>
   ---
   ```
4. Answer in the language the user asked in (these docs are in Hebrew; translate/summarize as needed).
5. If asked "what reports exist for X" (e.g. agent performance, incoming calls, queues, dialer), scan the matching sub-categories inside `references/דאשבורד.md` (e.g. "ביצועי נציגים", "שיחות נכנסות", "שיחות יוצאות", "מעגלי המתנה", "חייגנים") and list the template names/numbers found.
6. **Always include the template number (מספר תבנית) for every report/chart you mention — for ANY report-related question, not just specific ones.** This is the identifier used to find/add the report in the actual Dashboard UI. If a listed report has no template number in the source data, say so explicitly instead of omitting the column silently.
7. If the answer isn't in these files, say so plainly rather than guessing — the support center may have added content since the last crawl (see Refreshing below).

## Refreshing the Data

The content is a snapshot, not a live connection. To refresh it when the site changes, run these from this skill's own directory (the folder containing this SKILL.md):

```
node scripts/crawl.js              # re-fetches all 15 category pages from voicenter.co.il into a local data/*.json cache
node scripts/build-references.js   # regenerates references/*.md from data/*.json
```

`scripts/crawl.js` works by fetching each support-center category page and decoding the `__NUXT_DATA__` JSON payload embedded in the server-rendered HTML (see `scripts/decode-nuxt.js`) — this is how the full article content is recovered even though the site is a client-rendered SPA with no public API. If Voicenter adds a new category, add its Hebrew URL slug to the `CATEGORY_SLUGS` array in `scripts/crawl.js`. The `data/` cache is not committed to this repo — only the generated `references/*.md` are — so re-run `crawl.js` before `build-references.js` after cloning.