51 lines
1.7 KiB
Markdown
51 lines
1.7 KiB
Markdown
---
|
|
description: Get billing increment updates and changes for telecom destinations
|
|
---
|
|
|
|
# Billing Updates Command
|
|
|
|
You are helping the user track billing increment changes in the telecommunications industry. Follow these steps:
|
|
|
|
1. **Parse the user's query** to identify:
|
|
- Year filter (e.g., 2024, 2025)
|
|
- Country filter (e.g., "CAMBODIA")
|
|
- Change type filter (increase, decrease, improved, mixed)
|
|
- Timeframe (recent days)
|
|
|
|
2. **Determine the appropriate endpoint:**
|
|
- `/updates/` - for filtered historical updates (year, country, change_type)
|
|
- `/updates/recent` - for updates in last N days (1-365 days)
|
|
- `/updates/summary` - for aggregated statistics
|
|
|
|
3. **Construct the API request** to `https://destinations-api.telecomsxchange.com` with parameters:
|
|
- `year` - filter by year
|
|
- `country` - filter by country name
|
|
- `change_type` - filter by change type
|
|
- `days` - for recent endpoint (default 30)
|
|
- `limit` - default to 100, max 500 for updates
|
|
|
|
4. **Use the WebFetch tool** to query the API
|
|
|
|
5. **Present the results** showing:
|
|
- Date of change
|
|
- Country
|
|
- Prefix/Network
|
|
- Old billing increment
|
|
- New billing increment
|
|
- Change type (improvement/deterioration)
|
|
|
|
6. **Analyze the impact:**
|
|
- Highlight favorable changes (better billing increments)
|
|
- Note unfavorable changes (worse billing increments)
|
|
- Summarize trends if multiple updates shown
|
|
|
|
7. **Provide context** about what billing changes mean:
|
|
- Improved: Better for cost control (e.g., 60/60 → 60/1)
|
|
- Deteriorated: Worse for cost control (e.g., 60/1 → 60/60)
|
|
|
|
**Example queries to handle:**
|
|
- "Show billing updates for 2025"
|
|
- "What changed in the last 30 days?"
|
|
- "Show billing improvements for Cambodia"
|
|
- "Get update summary"
|