Support Console
Overview
Resolve telecom support tasks against a shared REST API. Every task includes a <TASK_ENV_BASE_URL> placeholder that points to the running support-console instance (typically http://task-env:9003/). All data must come from API responses, never from assumptions.
Essential Rules
- Replace
<TASK_ENV_BASE_URL> with the actual base URL provided in the task prompt.
- Call the API for every record the task references; do not guess values.
- Preserve payload ordering in output arrays unless the task explicitly says otherwise.
- Output only JSON that conforms to the provided answer template.
API Navigation
| Resource |
List endpoint |
Single-item endpoint |
| Tickets |
GET /api/tickets |
GET /api/tickets/{ticket_id} |
| Accounts |
GET /api/accounts (via catalog) |
GET /api/accounts/{account_id} |
| Outages |
GET /api/outages |
(list only) |
| Diagnostics |
|
GET /api/diagnostics/{ticket_id} |
| Troubleshooting |
|
GET /api/troubleshooting/{ticket_id} |
| Customers |
GET /api/customers |
GET /api/customers/{customer_id} |
| Lines |
GET /api/lines |
GET /api/lines/{line_id} |
| Devices |
|
GET /api/devices/{device_id} |
| Plans |
|
GET /api/plans/{plan_id} |
| Bills |
GET /api/bills |
GET /api/bills/{bill_id} |
| Cases |
via catalog |
GET /api/contact-center/cases/{case_id} |
| Enterprise accounts |
GET /api/enterprise/accounts |
GET /api/enterprise/accounts/{account_id} |
| Enterprise incidents |
GET /api/enterprise/incidents |
GET /api/enterprise/incidents/{incident_id} |
| Export runs |
GET /api/enterprise/export-runs |
(list only) |
| Messages |
GET /api/enterprise/messages |
(list only) |
| SLA |
|
GET /api/enterprise/sla/{account_id} |
| Catalog |
GET /api/catalog |
(system overview) |
For complete field-by-field schemas and record shapes, see references/api_schemas.md.
Task Workflows
Service Ticket Resolution
Applies when the task provides a batch of ticket IDs and asks for resolution status, diagnostic needs, outage matching, escalations, and routing.
For each ticket:
GET /api/tickets/{ticket_id} to get account_id, service_area, service_type.
GET /api/accounts/{account_id} to check account status and authentication.
GET /api/outages and match against the ticket's service_area and service_type.
GET /api/diagnostics/{ticket_id} to see root causes and metrics.
GET /api/troubleshooting/{ticket_id} to see applied fixes and post-fix metrics.
Decision rules:
- Account not found (404 or unknown account_id):
FAILED / INVALID_ACCOUNT
- Account status
Suspended: FAILED / INELIGIBLE_ACCOUNT
- Authentication failures (
last_login_status: "FAILURE", account_recovery_status: "FAILURE"): FAILED / AUTH_FAILED
- Active outage matching the ticket's
service_area and service_type: PENDING_ACTION / OUTAGE_WAIT. Set outage_id to the matching outage.
- Diagnostics + troubleshooting fixable: If diagnostics reveals a root cause that the troubleshooting steps successfully remediated (comparing pre/post metrics for improvement), mark
RESOLVED / AUTO_TROUBLESHOOTING. Set boolean flags based on diagnostic metrics.
- Structural/hardware root cause where troubleshooting was inadequate:
ESCALATED. Map root cause to escalation team:
FIBER_DROP_DAMAGE, SIGNAL_LOSS, PHYSICAL_LINE_FAULT → FIELD_OPS
BACKBONE_CAPACITY, NETWORK_CAPACITY → NETWORK_ENGINEERING
PROVISIONING_STALE, CONFIGURATION_DRIFT → TIER2_SUPPORT
- Overdue suspension:
FAILED / ACCOUNTS_PAYABLE (if the schema supports it), key blocker OVERDUE_SUSPENSION.
When a task asks for a batch_summary, count results and also count tickets requiring customer wait (those marked PENDING_ACTION).
Mobile Contact-Center Case Resolution
Applies when the task gives a case queue and asks for support actions.
For each case:
GET /api/contact-center/cases/{case_id} to get line_id, customer_id, device_id, issue_type.
GET /api/lines/{line_id} for status, roaming, suspension reason, plan.
GET /api/devices/{device_id} for signal, sim, VPN, data saver, messaging permissions, network mode, mobile data, roaming.
GET /api/bills (or per-customer bills) to check for overdue bills.
GET /api/plans/{plan_id} for plan limits and pricing.
Action selection by issue pattern:
| Symptom |
Likely cause |
Primary action |
Notes |
| No service after commute/travel |
SIM dislodged |
RESEAT_SIM |
Confirm with sim_status: "missing" |
| Line suspended, user willing to pay |
Overdue bill |
SEND_PAYMENT_REQUEST + RESUME_LINE_REBOOT |
Find overdue bill, set bill_id, charge_amount_usd |
| Traveling abroad, no data |
Roaming off on device or line |
TOGGLE_ROAMING (device-side) or ENABLE_LINE_ROAMING (line-side) |
Check both line.roaming_enabled and device.phone_roaming_enabled |
| Cannot send photos/MMS |
Missing storage permission |
GRANT_MESSAGING_PERMISSION |
Check device.messaging_permissions.storage, set permission field |
| Slow data with VPN running |
VPN throttling |
DISCONNECT_VPN |
Confirm device.vpn_connected: true |
| Slow data, data-saver icon |
Data saver active |
TOGGLE_DATA_SAVER |
Confirm device.data_saver_mode: true |
| Slow data, old network mode |
3G-only mode |
SET_NETWORK_MODE |
Confirm device.network_mode_preference set to legacy |
| No data, mobile data off |
Toggle needed |
TOGGLE_MOBILE_DATA |
Confirm device.mobile_data_enabled: false |
| Data limit reached |
Need refuel |
REFUEL_DATA |
Compare line.data_used_gb vs plan.data_limit_gb |
Set secondary_action to NO_ACTION unless a clear follow-up is identified.
Set final_route:
- Device-side fixes (toggle, reseat, VPN, data saver, network mode) →
SELF_SERVICE
- Billing/payment actions →
BILLING_RECOVERY
- Line-side roaming/carrier changes →
CARRIER_UPDATE
- Complex issues requiring a person →
HUMAN_TRANSFER
Enterprise Incident Investigation
Applies when a client has an export failure or similar enterprise incident and a formal response package must be assembled.
Workflow:
- Identify the incident ID from the complaint (may be approximate, search
/api/enterprise/incidents).
GET /api/enterprise/incidents/{incident_id} for severity, owners, account_id, product.
GET /api/enterprise/accounts/{account_id} for account_owner, name, tier.
GET /api/enterprise/export-runs and filter by enterprise_account_id and incident_id to find the failure window.
GET /api/enterprise/messages and filter by incident-related message IDs or channels/accounts to find root cause details and SLA information.
GET /api/enterprise/sla/{account_id} for the credit percentage.
Naming conventions (when requirements specify a style):
channel_name: lowercase-hyphenated version of the client organization name (e.g., "Example Corp" → example-corp)
evidence_folder: {Client Name} {Month Year} Investigation (e.g., "Example Corp May 2026 Investigation")
report_title: {Client Name} Export Failure - Resolution Report
Share permissions: Assign view or edit to listed users based on role; read permission designations from the task requirements.
Response status:
NEEDS_FINANCE_REVIEW when SLA credits are involved and the task involves billing/credit handling
NEEDS_ENGINEERING_REVIEW when root cause has an engineering owner
READY_TO_SEND when all information is confirmed
UNDER_INVESTIGATION when evidence is still being collected
Root cause: Derive from failure_code on failed export runs combined with message bodies. Map STALE_CREDENTIAL → "stale credential after rotation", STAGING_STORAGE_QUOTA → "storage quota exceeded".
Failure window: Find consecutive failed runs by date. start_date is the first failed run date, end_date is the last, failed_days is the count.
Backfill: Equal to failed_days unless evidence shows partial recovery.
Contributing alert issue: ARCHIVED_ALERT_ROUTE when messages mention an alert/export channel that appears in the archive; otherwise NONE or UNKNOWN.
Queue Quality Triage
Applies when classifying tickets before SLA handoff.
Follow the same data-gathering steps as Service Ticket Resolution, but classify with key_blocker instead of full resolution detail. The key_blocker enum values:
ACTIVE_OUTAGE — matching active outage on service_area + service_type
INVALID_ACCOUNT — account not found
AUTH_FAILED — authentication permanently failed
OVERDUE_SUSPENSION — account suspended due to overdue bill
FRAUD_SUSPENSION — account suspended for fraud
NETWORK_CAPACITY — backbone/capacity root cause
PROVISIONING_STALE — provisioning mismatch
PHYSICAL_LINE_FAULT — fiber drop or physical damage
NONE — no blocking issue found (ticket resolvable)
Map key_blocker to route_team:
ACTIVE_OUTAGE → NONE (awaiting resolution)
INVALID_ACCOUNT → NONE
AUTH_FAILED → NONE
OVERDUE_SUSPENSION → ACCOUNTS_PAYABLE
NETWORK_CAPACITY → NETWORK_ENGINEERING
PROVISIONING_STALE → TIER2_SUPPORT
PHYSICAL_LINE_FAULT → FIELD_OPS
Set diagnostic_required: true when diagnostics are needed for further investigation (voice profile issues, backbone capacity, provisioning mismatches). Set false for outages, invalid accounts, auth failures, and overdue suspensions where diagnostics add no value.
final_resolution_status:
PENDING_ACTION for active outages (waiting for outage resolution)
RESOLVED for tickets where diagnostics + troubleshooting show improvement and no structural blocker remains
ESCALATED for tickets needing specialist teams
FAILED for invalid accounts, auth failures, overdue suspensions
Mobile Data Recovery
Applies when a worklist of mobile data cases needs resolution with data refuel calculations.
For each case:
GET /api/contact-center/cases/{case_id} for line_id, device_id, issue_type, customer_location.
GET /api/lines/{line_id} for data_used_gb, status, roaming_enabled.
GET /api/devices/{device_id} for the full device state.
GET /api/plans/{plan_id} for data_limit_gb and data_refueling_price_per_gb.
Action selection mirrors Mobile Contact-Center cases with these additions:
- Data refuel: When
line.data_used_gb > plan.data_limit_gb, use REFUEL_DATA. Check task payload for accepted refuel GB. Calculate charge: accepted_gb × plan.data_refueling_price_per_gb. Set data_refuel_gb and charge_amount_usd.
- Line roaming missing: When customer is abroad and
line.roaming_enabled: false, use ENABLE_LINE_ROAMING, carrier_update_required: true.
- Device-setting fixes:
TOGGLE_DATA_SAVER, SET_NETWORK_MODE, TOGGLE_MOBILE_DATA, DISCONNECT_VPN — these are DEVICE_SETTING_FIX routes.
final_route values:
DATA_RECOVERY for refuel operations
CARRIER_UPDATE for line-side roaming changes
DEVICE_SETTING_FIX for device toggles
HUMAN_TRANSFER for cases requiring a person
Reference
For detailed API schemas with every field and data type, see references/api_schemas.md.
1---2name: support-console-43description: Resolve telecom support tasks using a shared support-console REST API. Use when the task involves service-ticket classification, mobile contact-center case resolution, enterprise incident investigation, queue-quality triage, mobile-data recovery, or any support-console record lookups. The skill covers accounts, tickets, diagnostics, troubleshooting, outages, customers, lines, devices, plans, bills, contact-center cases, enterprise accounts, incidents, export runs, messages, and SLA contracts.4metadata:5 source: https://skillmd.com/skills/prism-shadow/support-console-46---78# Support Console910## Overview1112Resolve telecom support tasks against a shared REST API. Every task includes a `<TASK_ENV_BASE_URL>` placeholder that points to the running support-console instance (typically `http://task-env:9003/`). All data must come from API responses, never from assumptions.1314## Essential Rules15161. Replace `<TASK_ENV_BASE_URL>` with the actual base URL provided in the task prompt.172. Call the API for every record the task references; do not guess values.183. Preserve payload ordering in output arrays unless the task explicitly says otherwise.194. Output only JSON that conforms to the provided answer template.2021## API Navigation2223| Resource | List endpoint | Single-item endpoint |24|---|---|---|25| Tickets | `GET /api/tickets` | `GET /api/tickets/{ticket_id}` |26| Accounts | `GET /api/accounts` (via catalog) | `GET /api/accounts/{account_id}` |27| Outages | `GET /api/outages` | (list only) |28| Diagnostics | | `GET /api/diagnostics/{ticket_id}` |29| Troubleshooting | | `GET /api/troubleshooting/{ticket_id}` |30| Customers | `GET /api/customers` | `GET /api/customers/{customer_id}` |31| Lines | `GET /api/lines` | `GET /api/lines/{line_id}` |32| Devices | | `GET /api/devices/{device_id}` |33| Plans | | `GET /api/plans/{plan_id}` |34| Bills | `GET /api/bills` | `GET /api/bills/{bill_id}` |35| Cases | via catalog | `GET /api/contact-center/cases/{case_id}` |36| Enterprise accounts | `GET /api/enterprise/accounts` | `GET /api/enterprise/accounts/{account_id}` |37| Enterprise incidents | `GET /api/enterprise/incidents` | `GET /api/enterprise/incidents/{incident_id}` |38| Export runs | `GET /api/enterprise/export-runs` | (list only) |39| Messages | `GET /api/enterprise/messages` | (list only) |40| SLA | | `GET /api/enterprise/sla/{account_id}` |41| Catalog | `GET /api/catalog` | (system overview) |4243For complete field-by-field schemas and record shapes, see [references/api_schemas.md](references/api_schemas.md).4445## Task Workflows4647### Service Ticket Resolution4849Applies when the task provides a batch of ticket IDs and asks for resolution status, diagnostic needs, outage matching, escalations, and routing.5051**For each ticket:**52531. `GET /api/tickets/{ticket_id}` to get `account_id`, `service_area`, `service_type`.542. `GET /api/accounts/{account_id}` to check account status and authentication.553. `GET /api/outages` and match against the ticket's `service_area` and `service_type`.564. `GET /api/diagnostics/{ticket_id}` to see root causes and metrics.575. `GET /api/troubleshooting/{ticket_id}` to see applied fixes and post-fix metrics.5859**Decision rules:**6061- **Account not found** (404 or unknown account_id): `FAILED` / `INVALID_ACCOUNT`62- **Account status `Suspended`**: `FAILED` / `INELIGIBLE_ACCOUNT`63- **Authentication failures** (`last_login_status: "FAILURE"`, `account_recovery_status: "FAILURE"`): `FAILED` / `AUTH_FAILED`64- **Active outage** matching the ticket's `service_area` and `service_type`: `PENDING_ACTION` / `OUTAGE_WAIT`. Set `outage_id` to the matching outage.65- **Diagnostics + troubleshooting fixable**: If diagnostics reveals a root cause that the troubleshooting steps successfully remediated (comparing pre/post metrics for improvement), mark `RESOLVED` / `AUTO_TROUBLESHOOTING`. Set boolean flags based on diagnostic metrics.66- **Structural/hardware root cause** where troubleshooting was inadequate: `ESCALATED`. Map root cause to escalation team:67 - `FIBER_DROP_DAMAGE`, `SIGNAL_LOSS`, `PHYSICAL_LINE_FAULT` → `FIELD_OPS`68 - `BACKBONE_CAPACITY`, `NETWORK_CAPACITY` → `NETWORK_ENGINEERING`69 - `PROVISIONING_STALE`, `CONFIGURATION_DRIFT` → `TIER2_SUPPORT`70- **Overdue suspension**: `FAILED` / `ACCOUNTS_PAYABLE` (if the schema supports it), key blocker `OVERDUE_SUSPENSION`.7172When a task asks for a `batch_summary`, count results and also count tickets requiring customer wait (those marked `PENDING_ACTION`).7374### Mobile Contact-Center Case Resolution7576Applies when the task gives a case queue and asks for support actions.7778**For each case:**79801. `GET /api/contact-center/cases/{case_id}` to get `line_id`, `customer_id`, `device_id`, `issue_type`.812. `GET /api/lines/{line_id}` for status, roaming, suspension reason, plan.823. `GET /api/devices/{device_id}` for signal, sim, VPN, data saver, messaging permissions, network mode, mobile data, roaming.834. `GET /api/bills` (or per-customer bills) to check for overdue bills.845. `GET /api/plans/{plan_id}` for plan limits and pricing.8586**Action selection by issue pattern:**8788| Symptom | Likely cause | Primary action | Notes |89|---|---|---|---|90| No service after commute/travel | SIM dislodged | `RESEAT_SIM` | Confirm with `sim_status: "missing"` |91| Line suspended, user willing to pay | Overdue bill | `SEND_PAYMENT_REQUEST` + `RESUME_LINE_REBOOT` | Find overdue bill, set `bill_id`, `charge_amount_usd` |92| Traveling abroad, no data | Roaming off on device or line | `TOGGLE_ROAMING` (device-side) or `ENABLE_LINE_ROAMING` (line-side) | Check both `line.roaming_enabled` and `device.phone_roaming_enabled` |93| Cannot send photos/MMS | Missing storage permission | `GRANT_MESSAGING_PERMISSION` | Check `device.messaging_permissions.storage`, set `permission` field |94| Slow data with VPN running | VPN throttling | `DISCONNECT_VPN` | Confirm `device.vpn_connected: true` |95| Slow data, data-saver icon | Data saver active | `TOGGLE_DATA_SAVER` | Confirm `device.data_saver_mode: true` |96| Slow data, old network mode | 3G-only mode | `SET_NETWORK_MODE` | Confirm `device.network_mode_preference` set to legacy |97| No data, mobile data off | Toggle needed | `TOGGLE_MOBILE_DATA` | Confirm `device.mobile_data_enabled: false` |98| Data limit reached | Need refuel | `REFUEL_DATA` | Compare `line.data_used_gb` vs `plan.data_limit_gb` |99100Set `secondary_action` to `NO_ACTION` unless a clear follow-up is identified.101102Set `final_route`:103- Device-side fixes (toggle, reseat, VPN, data saver, network mode) → `SELF_SERVICE`104- Billing/payment actions → `BILLING_RECOVERY`105- Line-side roaming/carrier changes → `CARRIER_UPDATE`106- Complex issues requiring a person → `HUMAN_TRANSFER`107108### Enterprise Incident Investigation109110Applies when a client has an export failure or similar enterprise incident and a formal response package must be assembled.111112**Workflow:**1131141. Identify the incident ID from the complaint (may be approximate, search `/api/enterprise/incidents`).1152. `GET /api/enterprise/incidents/{incident_id}` for severity, owners, account_id, product.1163. `GET /api/enterprise/accounts/{account_id}` for account_owner, name, tier.1174. `GET /api/enterprise/export-runs` and filter by `enterprise_account_id` and `incident_id` to find the failure window.1185. `GET /api/enterprise/messages` and filter by incident-related message IDs or channels/accounts to find root cause details and SLA information.1196. `GET /api/enterprise/sla/{account_id}` for the credit percentage.120121**Naming conventions (when requirements specify a style):**122123- `channel_name`: lowercase-hyphenated version of the client organization name (e.g., "Example Corp" → `example-corp`)124- `evidence_folder`: `{Client Name} {Month Year} Investigation` (e.g., "Example Corp May 2026 Investigation")125- `report_title`: `{Client Name} Export Failure - Resolution Report`126127**Share permissions:** Assign `view` or `edit` to listed users based on role; read permission designations from the task requirements.128129**Response status:**130- `NEEDS_FINANCE_REVIEW` when SLA credits are involved and the task involves billing/credit handling131- `NEEDS_ENGINEERING_REVIEW` when root cause has an engineering owner132- `READY_TO_SEND` when all information is confirmed133- `UNDER_INVESTIGATION` when evidence is still being collected134135**Root cause:** Derive from `failure_code` on failed export runs combined with message bodies. Map `STALE_CREDENTIAL` → "stale credential after rotation", `STAGING_STORAGE_QUOTA` → "storage quota exceeded".136137**Failure window:** Find consecutive failed runs by date. `start_date` is the first failed run date, `end_date` is the last, `failed_days` is the count.138139**Backfill:** Equal to `failed_days` unless evidence shows partial recovery.140141**Contributing alert issue:** `ARCHIVED_ALERT_ROUTE` when messages mention an alert/export channel that appears in the archive; otherwise `NONE` or `UNKNOWN`.142143### Queue Quality Triage144145Applies when classifying tickets before SLA handoff.146147Follow the same data-gathering steps as Service Ticket Resolution, but classify with `key_blocker` instead of full resolution detail. The `key_blocker` enum values:148149- `ACTIVE_OUTAGE` — matching active outage on service_area + service_type150- `INVALID_ACCOUNT` — account not found151- `AUTH_FAILED` — authentication permanently failed152- `OVERDUE_SUSPENSION` — account suspended due to overdue bill153- `FRAUD_SUSPENSION` — account suspended for fraud154- `NETWORK_CAPACITY` — backbone/capacity root cause155- `PROVISIONING_STALE` — provisioning mismatch156- `PHYSICAL_LINE_FAULT` — fiber drop or physical damage157- `NONE` — no blocking issue found (ticket resolvable)158159Map `key_blocker` to `route_team`:160- `ACTIVE_OUTAGE` → `NONE` (awaiting resolution)161- `INVALID_ACCOUNT` → `NONE`162- `AUTH_FAILED` → `NONE`163- `OVERDUE_SUSPENSION` → `ACCOUNTS_PAYABLE`164- `NETWORK_CAPACITY` → `NETWORK_ENGINEERING`165- `PROVISIONING_STALE` → `TIER2_SUPPORT`166- `PHYSICAL_LINE_FAULT` → `FIELD_OPS`167168Set `diagnostic_required: true` when diagnostics are needed for further investigation (voice profile issues, backbone capacity, provisioning mismatches). Set `false` for outages, invalid accounts, auth failures, and overdue suspensions where diagnostics add no value.169170`final_resolution_status`:171- `PENDING_ACTION` for active outages (waiting for outage resolution)172- `RESOLVED` for tickets where diagnostics + troubleshooting show improvement and no structural blocker remains173- `ESCALATED` for tickets needing specialist teams174- `FAILED` for invalid accounts, auth failures, overdue suspensions175176### Mobile Data Recovery177178Applies when a worklist of mobile data cases needs resolution with data refuel calculations.179180**For each case:**1811821. `GET /api/contact-center/cases/{case_id}` for line_id, device_id, issue_type, customer_location.1832. `GET /api/lines/{line_id}` for data_used_gb, status, roaming_enabled.1843. `GET /api/devices/{device_id}` for the full device state.1854. `GET /api/plans/{plan_id}` for data_limit_gb and data_refueling_price_per_gb.186187**Action selection mirrors Mobile Contact-Center cases with these additions:**188189- **Data refuel**: When `line.data_used_gb > plan.data_limit_gb`, use `REFUEL_DATA`. Check task payload for accepted refuel GB. Calculate charge: `accepted_gb × plan.data_refueling_price_per_gb`. Set `data_refuel_gb` and `charge_amount_usd`.190- **Line roaming missing**: When customer is abroad and `line.roaming_enabled: false`, use `ENABLE_LINE_ROAMING`, `carrier_update_required: true`.191- **Device-setting fixes**: `TOGGLE_DATA_SAVER`, `SET_NETWORK_MODE`, `TOGGLE_MOBILE_DATA`, `DISCONNECT_VPN` — these are `DEVICE_SETTING_FIX` routes.192193**final_route values:**194- `DATA_RECOVERY` for refuel operations195- `CARRIER_UPDATE` for line-side roaming changes196- `DEVICE_SETTING_FIX` for device toggles197- `HUMAN_TRANSFER` for cases requiring a person198199## Reference200201For detailed API schemas with every field and data type, see [references/api_schemas.md](references/api_schemas.md).