Support Console Operations Skill
Use this skill when a task asks for support-console evidence from <TASK_ENV_BASE_URL> and requires JSON conforming to a provided payloads/answer_template.json.
Ground Rules
- Read the prompt, every payload file, and the answer template first.
- Return only valid JSON matching the template shape, field names, enum spelling, ordering requirements, and numeric precision.
- Use the support-console API as the source of truth. Do not infer from customer wording alone when API records exist.
- Use only read-only business endpoints. Do not call any judge/evaluator endpoint.
- Preserve payload order for ticket lists. Sort case decisions by ascending
case_id when the template says so.
- Leave string IDs empty only when the template says an empty string means "not applicable".
- Compute all summary counts from the emitted decisions, not separately.
API Workflow
Start with GET /api/catalog when available to confirm endpoint names. Use GET /api/search?q=<id or client> as a cross-reference when direct endpoints are absent or when you need linked records.
For service tickets, gather:
- Ticket:
/api/tickets/{ticket_id}
- Diagnostics:
/api/diagnostics/{ticket_id}
- Troubleshooting:
/api/troubleshooting/{ticket_id}
- Outages:
/api/outages, filtered to active outages matching both service_area and service_type
- Account state: search by
account_id if a direct account endpoint is unavailable
For mobile/contact-center cases, gather:
- Case record via the case endpoint advertised by the catalog, or
search by case_id
- Customer:
/api/customers/{customer_id}
- Line:
/api/lines/{line_id}
- Device:
/api/devices/{device_id}
- Plan:
/api/plans/{plan_id}
- Bills: search by
customer_id or use /api/bills, then filter to that customer
For enterprise export incidents, gather:
- Incident:
/api/enterprise/incidents/{incident_id} or search by client/product/reference
- Enterprise account:
/api/enterprise/accounts/{enterprise_account_id}
- Export runs:
/api/enterprise/export-runs or search by incident/account
- Messages:
/api/enterprise/messages or search by client, incident, product, or failure terms
- SLA:
/api/enterprise/sla/{enterprise_account_id}
Service Ticket Decisions
Apply blockers before diagnostics:
- If no matching account record exists for the ticket account, classify as failed with the invalid-account route/blocker and no diagnostic.
- If account authentication shows failed login/recovery and the ticket is an authentication problem, classify as failed with the auth-failed route/blocker and no diagnostic.
- If account or line state is suspended/held:
- Use overdue-suspension and accounts-payable routing when the template has those fields and evidence mentions overdue billing.
- Otherwise use the template's ineligible-account route/blocker with no escalation team.
- If an active outage matches both service area and service type, classify as pending action/outage wait, include the outage ID when requested, set diagnostic-required/needed false, and count it as a customer-wait case.
If no blocker applies, use diagnostics and troubleshooting:
- Set
diagnostic_needed/diagnostic_required true when diagnostics drive the decision.
latency_issue: true for clearly high latency, typically around 100 ms or higher, or when root causes/text indicate latency or packet loss.
stability_issue: true for high jitter, packet loss, signal loss, intermittent service, or similar stability evidence.
bandwidth_issue: true when measured bandwidth is materially below subscribed speed, usually below about 80 percent, or when speed/throughput evidence says poor.
- If troubleshooting resolves metrics to acceptable levels and the root cause is a refreshable profile/configuration issue, mark resolved with the auto-troubleshooting/no-team route.
- Physical signal, fiber drop, damaged line, or line-work evidence escalates to field operations and physical-line-fault when that blocker enum exists.
- Backbone, capacity, congestion, or network-wide engineering evidence escalates to network engineering and network-capacity.
- Stale provisioning, profile mismatch after a move, or failed provisioning adjustment escalates to tier 2 support and provisioning-stale.
- If serious diagnostics remain bad after troubleshooting and no more specific route exists, escalate to tier 2 support.
For queue-quality templates:
key_blocker is NONE for resolved/self-service outcomes.
route_team is NONE unless an escalation or accounts-payable recovery is needed.
- Count each route-team enum from emitted decisions, including zeroes for teams present in the template.
Mobile Case Decisions
Use the case issue type and customer wording to choose the relevant record fields, but let line/device/bill/plan state decide the action. Prefer the first matching item in this priority order.
- Suspended line with overdue bill:
primary_action: SEND_PAYMENT_REQUEST
secondary_action: RESUME_LINE_REBOOT
bill_id: overdue bill for the customer
charge_amount_usd: overdue amount
- route: billing recovery
- Fraud, unsupported suspension, missing customer/line/device evidence, or ambiguous states that cannot be fixed from the allowed actions:
- transfer human when available; otherwise no action only if the template has no transfer route.
- No service:
airplane_mode: true -> TOGGLE_AIRPLANE_MODE
- SIM missing/inactive/not ready ->
RESEAT_SIM
- mobile data disabled for a data complaint ->
TOGGLE_MOBILE_DATA
- APN/MMSC carrier settings missing ->
RESET_APN_REBOOT
- Roaming while abroad:
- Phone roaming disabled while line roaming is enabled ->
TOGGLE_ROAMING, no carrier update.
- Line/carrier roaming disabled ->
ENABLE_LINE_ROAMING, carrier update required.
- If both are disabled and the template allows a secondary action, enable line roaming first and toggle device roaming second.
- Data limit exhausted:
- Compare line
data_used_gb with plan data_limit_gb.
- If payload preferences include accepted refuel GB, use
REFUEL_DATA.
data_refuel_gb is the accepted amount; charge is accepted GB times data_refueling_price_per_gb.
- Use a data-recovery route when the template provides one; otherwise use self-service unless human approval is required.
- Slow data:
data_saver_mode: true -> TOGGLE_DATA_SAVER
- old or restrictive network mode such as 3G-only ->
SET_NETWORK_MODE
vpn_connected: true -> DISCONNECT_VPN
- MMS/photo messaging:
- Missing
sms and/or storage permissions -> GRANT_MESSAGING_PERMISSION; set permission to sms, storage, or sms_and_storage.
- Permissions present but MMS/APN config missing ->
RESET_APN_REBOOT.
- Voice/Wi-Fi calling issues:
- If Wi-Fi calling is off and the complaint is about voice coverage or Wi-Fi calling, use
TOGGLE_WIFI_CALLING.
Set secondary_action to NO_ACTION unless a required follow-up is shown by the rule. Set permission to NONE except for messaging-permission fixes. Set bill and charge fields to empty/zero unless billing recovery or refuel applies.
Route mapping:
- Billing recovery:
BILLING_RECOVERY
- Carrier-side line change:
CARRIER_UPDATE and carrier_update_required: true
- Refuel/data-limit recovery:
DATA_RECOVERY when present
- Local device settings:
DEVICE_SETTING_FIX when present, otherwise SELF_SERVICE
- Human transfer:
HUMAN_TRANSFER
Enterprise Export Response Packages
Extract the client, product, requested incident reference, required users, and naming requirements from the payloads. Then build the response from API evidence:
- Identify the incident from the reference first. If the reference is approximate, search by client and product and choose the incident whose account and product match the complaint.
- Use the incident for
incident_id, enterprise_account_id, severity, engineering_owner, and account_owner unless stronger account evidence overrides owner fields.
- Filter export runs to the chosen incident/account/product. Failed runs determine:
failure_window.start_date: earliest failed run date
failure_window.end_date: latest failed run date
failure_window.failed_days: count of failed run dates
backfill_days: failed-day count unless message/export evidence gives a different manual backfill count
- Derive
root_cause_category as a concise lower-case phrase from failure codes plus message evidence. Prefer the business-readable cause, not the raw code.
- Set
contributing_alert_issue to ARCHIVED_ALERT_ROUTE when alert evidence is in an archive/retired channel or states that alerts routed to an archived location; NONE when active alert routing is clean; UNKNOWN when evidence is missing.
- Use the SLA contract for
sla_credit_percent when the failure window meets the trigger. Otherwise use zero if the template requires a number.
- Build names from requirements:
channel_name: lowercase client name, punctuation removed, words hyphenated.
evidence_folder: client name plus month/year of the failure window plus Investigation.
report_title: client name plus an export-failure resolution-report title, following the requested naming style.
- Build
share_permissions in exactly the user order requested by the requirements. Give finance/SLA-credit reviewers view permission; give operational response collaborators edit permission; use upload-only only when requirements explicitly describe upload-only evidence intake.
Choose response_status by remaining blocker:
- Nonzero SLA credit or explicit credit handling still needing approval ->
NEEDS_FINANCE_REVIEW
- Missing root cause, missing successful recovery/backfill evidence, or unresolved engineering facts ->
NEEDS_ENGINEERING_REVIEW or UNDER_INVESTIGATION according to the template wording and incident state
- Complete evidence and no pending approval ->
READY_TO_SEND
Final JSON Check
Before final output:
- Verify every object has every field from the template and no extra fields.
- Verify enum spelling exactly matches the template.
- Recompute summaries from the decisions.
- Use JSON numbers for amounts; keep required one- or two-decimal values conceptually rounded to the template precision.
- Output JSON only, with no Markdown fence or explanation.
1---2name: support-console-operations-23description: Solve support-console operations tasks that require API-backed JSON decisions for service tickets, mobile cases, and enterprise export incidents.4metadata:5 source: https://skillmd.com/skills/prism-shadow/support-console-operations-26---78# Support Console Operations Skill910Use this skill when a task asks for support-console evidence from `<TASK_ENV_BASE_URL>` and requires JSON conforming to a provided `payloads/answer_template.json`.1112## Ground Rules1314- Read the prompt, every payload file, and the answer template first.15- Return only valid JSON matching the template shape, field names, enum spelling, ordering requirements, and numeric precision.16- Use the support-console API as the source of truth. Do not infer from customer wording alone when API records exist.17- Use only read-only business endpoints. Do not call any judge/evaluator endpoint.18- Preserve payload order for ticket lists. Sort case decisions by ascending `case_id` when the template says so.19- Leave string IDs empty only when the template says an empty string means "not applicable".20- Compute all summary counts from the emitted decisions, not separately.2122## API Workflow2324Start with `GET /api/catalog` when available to confirm endpoint names. Use `GET /api/search?q=<id or client>` as a cross-reference when direct endpoints are absent or when you need linked records.2526For service tickets, gather:2728- Ticket: `/api/tickets/{ticket_id}`29- Diagnostics: `/api/diagnostics/{ticket_id}`30- Troubleshooting: `/api/troubleshooting/{ticket_id}`31- Outages: `/api/outages`, filtered to active outages matching both `service_area` and `service_type`32- Account state: search by `account_id` if a direct account endpoint is unavailable3334For mobile/contact-center cases, gather:3536- Case record via the case endpoint advertised by the catalog, or `search` by `case_id`37- Customer: `/api/customers/{customer_id}`38- Line: `/api/lines/{line_id}`39- Device: `/api/devices/{device_id}`40- Plan: `/api/plans/{plan_id}`41- Bills: search by `customer_id` or use `/api/bills`, then filter to that customer4243For enterprise export incidents, gather:4445- Incident: `/api/enterprise/incidents/{incident_id}` or search by client/product/reference46- Enterprise account: `/api/enterprise/accounts/{enterprise_account_id}`47- Export runs: `/api/enterprise/export-runs` or search by incident/account48- Messages: `/api/enterprise/messages` or search by client, incident, product, or failure terms49- SLA: `/api/enterprise/sla/{enterprise_account_id}`5051## Service Ticket Decisions5253Apply blockers before diagnostics:54551. If no matching account record exists for the ticket account, classify as failed with the invalid-account route/blocker and no diagnostic.562. If account authentication shows failed login/recovery and the ticket is an authentication problem, classify as failed with the auth-failed route/blocker and no diagnostic.573. If account or line state is suspended/held:58 - Use overdue-suspension and accounts-payable routing when the template has those fields and evidence mentions overdue billing.59 - Otherwise use the template's ineligible-account route/blocker with no escalation team.604. If an active outage matches both service area and service type, classify as pending action/outage wait, include the outage ID when requested, set diagnostic-required/needed false, and count it as a customer-wait case.6162If no blocker applies, use diagnostics and troubleshooting:6364- Set `diagnostic_needed`/`diagnostic_required` true when diagnostics drive the decision.65- `latency_issue`: true for clearly high latency, typically around 100 ms or higher, or when root causes/text indicate latency or packet loss.66- `stability_issue`: true for high jitter, packet loss, signal loss, intermittent service, or similar stability evidence.67- `bandwidth_issue`: true when measured bandwidth is materially below subscribed speed, usually below about 80 percent, or when speed/throughput evidence says poor.68- If troubleshooting resolves metrics to acceptable levels and the root cause is a refreshable profile/configuration issue, mark resolved with the auto-troubleshooting/no-team route.69- Physical signal, fiber drop, damaged line, or line-work evidence escalates to field operations and physical-line-fault when that blocker enum exists.70- Backbone, capacity, congestion, or network-wide engineering evidence escalates to network engineering and network-capacity.71- Stale provisioning, profile mismatch after a move, or failed provisioning adjustment escalates to tier 2 support and provisioning-stale.72- If serious diagnostics remain bad after troubleshooting and no more specific route exists, escalate to tier 2 support.7374For queue-quality templates:7576- `key_blocker` is `NONE` for resolved/self-service outcomes.77- `route_team` is `NONE` unless an escalation or accounts-payable recovery is needed.78- Count each route-team enum from emitted decisions, including zeroes for teams present in the template.7980## Mobile Case Decisions8182Use the case issue type and customer wording to choose the relevant record fields, but let line/device/bill/plan state decide the action. Prefer the first matching item in this priority order.83841. Suspended line with overdue bill:85 - `primary_action`: `SEND_PAYMENT_REQUEST`86 - `secondary_action`: `RESUME_LINE_REBOOT`87 - `bill_id`: overdue bill for the customer88 - `charge_amount_usd`: overdue amount89 - route: billing recovery902. Fraud, unsupported suspension, missing customer/line/device evidence, or ambiguous states that cannot be fixed from the allowed actions:91 - transfer human when available; otherwise no action only if the template has no transfer route.923. No service:93 - `airplane_mode: true` -> `TOGGLE_AIRPLANE_MODE`94 - SIM missing/inactive/not ready -> `RESEAT_SIM`95 - mobile data disabled for a data complaint -> `TOGGLE_MOBILE_DATA`96 - APN/MMSC carrier settings missing -> `RESET_APN_REBOOT`974. Roaming while abroad:98 - Phone roaming disabled while line roaming is enabled -> `TOGGLE_ROAMING`, no carrier update.99 - Line/carrier roaming disabled -> `ENABLE_LINE_ROAMING`, carrier update required.100 - If both are disabled and the template allows a secondary action, enable line roaming first and toggle device roaming second.1015. Data limit exhausted:102 - Compare line `data_used_gb` with plan `data_limit_gb`.103 - If payload preferences include accepted refuel GB, use `REFUEL_DATA`.104 - `data_refuel_gb` is the accepted amount; charge is accepted GB times `data_refueling_price_per_gb`.105 - Use a data-recovery route when the template provides one; otherwise use self-service unless human approval is required.1066. Slow data:107 - `data_saver_mode: true` -> `TOGGLE_DATA_SAVER`108 - old or restrictive network mode such as 3G-only -> `SET_NETWORK_MODE`109 - `vpn_connected: true` -> `DISCONNECT_VPN`1107. MMS/photo messaging:111 - Missing `sms` and/or `storage` permissions -> `GRANT_MESSAGING_PERMISSION`; set `permission` to `sms`, `storage`, or `sms_and_storage`.112 - Permissions present but MMS/APN config missing -> `RESET_APN_REBOOT`.1138. Voice/Wi-Fi calling issues:114 - If Wi-Fi calling is off and the complaint is about voice coverage or Wi-Fi calling, use `TOGGLE_WIFI_CALLING`.115116Set `secondary_action` to `NO_ACTION` unless a required follow-up is shown by the rule. Set permission to `NONE` except for messaging-permission fixes. Set bill and charge fields to empty/zero unless billing recovery or refuel applies.117118Route mapping:119120- Billing recovery: `BILLING_RECOVERY`121- Carrier-side line change: `CARRIER_UPDATE` and `carrier_update_required: true`122- Refuel/data-limit recovery: `DATA_RECOVERY` when present123- Local device settings: `DEVICE_SETTING_FIX` when present, otherwise `SELF_SERVICE`124- Human transfer: `HUMAN_TRANSFER`125126## Enterprise Export Response Packages127128Extract the client, product, requested incident reference, required users, and naming requirements from the payloads. Then build the response from API evidence:129130- Identify the incident from the reference first. If the reference is approximate, search by client and product and choose the incident whose account and product match the complaint.131- Use the incident for `incident_id`, `enterprise_account_id`, `severity`, `engineering_owner`, and `account_owner` unless stronger account evidence overrides owner fields.132- Filter export runs to the chosen incident/account/product. Failed runs determine:133 - `failure_window.start_date`: earliest failed run date134 - `failure_window.end_date`: latest failed run date135 - `failure_window.failed_days`: count of failed run dates136 - `backfill_days`: failed-day count unless message/export evidence gives a different manual backfill count137- Derive `root_cause_category` as a concise lower-case phrase from failure codes plus message evidence. Prefer the business-readable cause, not the raw code.138- Set `contributing_alert_issue` to `ARCHIVED_ALERT_ROUTE` when alert evidence is in an archive/retired channel or states that alerts routed to an archived location; `NONE` when active alert routing is clean; `UNKNOWN` when evidence is missing.139- Use the SLA contract for `sla_credit_percent` when the failure window meets the trigger. Otherwise use zero if the template requires a number.140- Build names from requirements:141 - `channel_name`: lowercase client name, punctuation removed, words hyphenated.142 - `evidence_folder`: client name plus month/year of the failure window plus `Investigation`.143 - `report_title`: client name plus an export-failure resolution-report title, following the requested naming style.144- Build `share_permissions` in exactly the user order requested by the requirements. Give finance/SLA-credit reviewers view permission; give operational response collaborators edit permission; use upload-only only when requirements explicitly describe upload-only evidence intake.145146Choose `response_status` by remaining blocker:147148- Nonzero SLA credit or explicit credit handling still needing approval -> `NEEDS_FINANCE_REVIEW`149- Missing root cause, missing successful recovery/backfill evidence, or unresolved engineering facts -> `NEEDS_ENGINEERING_REVIEW` or `UNDER_INVESTIGATION` according to the template wording and incident state150- Complete evidence and no pending approval -> `READY_TO_SEND`151152## Final JSON Check153154Before final output:155156- Verify every object has every field from the template and no extra fields.157- Verify enum spelling exactly matches the template.158- Recompute summaries from the decisions.159- Use JSON numbers for amounts; keep required one- or two-decimal values conceptually rounded to the template precision.160- Output JSON only, with no Markdown fence or explanation.