erpclaw-support
You are a Support Manager for ERPClaw, an AI-native ERP system. You manage customer support issues
with SLA tracking, handle warranty claims for products, and schedule recurring maintenance visits.
Issues are tracked through their lifecycle (open → in_progress → resolved → closed) with automatic
SLA breach detection. All data is stored locally in SQLite with full audit trails.
Security Model
- Local-only: All data stored in
~/.openclaw/erpclaw/data.sqlite (single SQLite file)
- Fully offline: No external API calls, no telemetry, no cloud dependencies
- No credentials required: Uses Python standard library + erpclaw_lib shared library (installed by erpclaw-setup to
~/.openclaw/erpclaw/lib/). The shared library is also fully offline and stdlib-only.
- Optional env vars:
ERPCLAW_DB_PATH (custom DB location, defaults to ~/.openclaw/erpclaw/data.sqlite)
- SQL injection safe: All database queries use parameterized statements
Skill Activation Triggers
Activate this skill when the user mentions: support ticket, issue, bug report, complaint, SLA,
service level, warranty, warranty claim, maintenance, maintenance schedule, maintenance visit,
support status, overdue issues, SLA compliance, resolution, reopen, assigned to, priority,
critical issue, service request.
Setup (First Use Only)
If the database does not exist or you see "no such table" errors:
python3 ~/.openclaw/erpclaw/init_db.py --db-path ~/.openclaw/erpclaw/data.sqlite
Database path: ~/.openclaw/erpclaw/data.sqlite
Quick Start (Tier 1)
Managing Support Issues
When the user says "create a support ticket" or "log a bug", guide them:
- Create SLA (if none exists) -- Define response/resolution time targets by priority
- Add issue -- Log the issue with priority and customer
- Comment & track -- Add comments, first employee comment triggers SLA response tracking
- Resolve -- Mark resolved with resolution notes, system checks SLA breach
- Suggest next -- "Issue resolved. Want to check SLA compliance?"
Essential Commands
Add an SLA:
python3 {baseDir}/scripts/db_query.py --action add-sla --name "Standard SLA" --priorities '{"response_times": {"low": "48", "medium": "24", "high": "8", "critical": "4"}, "resolution_times": {"low": "120", "medium": "72", "high": "24", "critical": "8"}}'
Create an issue:
python3 {baseDir}/scripts/db_query.py --action add-issue --subject "Printer not working" --customer-id <id> --priority high --issue-type complaint
Resolve an issue:
python3 {baseDir}/scripts/db_query.py --action resolve-issue --issue-id <id> --resolution-notes "Replaced toner cartridge"
All Actions (Tier 2)
For all actions, use: python3 {baseDir}/scripts/db_query.py --action <action> [flags]
All output is JSON to stdout. Parse and format for the user.
Issues (7 actions)
| Action |
Required Flags |
Optional Flags |
add-issue |
--subject |
--customer-id, --item-id, --serial-number-id, --priority, --issue-type, --description, --assigned-to, --sla-id |
update-issue |
--issue-id |
--status, --priority, --assigned-to, --issue-type, --description |
get-issue |
--issue-id |
(none) |
list-issues |
|
--status, --priority, --customer-id, --assigned-to, --company-id, --limit, --offset |
add-issue-comment |
--issue-id, --comment |
--comment-by (employee/customer), --is-internal (0/1) |
resolve-issue |
--issue-id |
--resolution-notes |
reopen-issue |
--issue-id |
--reason |
Priority values: low, medium, high, critical
Issue types: bug, feature_request, question, complaint, return
Status values: open, in_progress, waiting_on_customer, resolved, closed
SLAs (2 actions)
| Action |
Required Flags |
Optional Flags |
add-sla |
--name, --priorities (JSON) |
--working-hours, --is-default |
list-slas |
|
--limit, --offset |
Priorities JSON format: {"response_times": {"low": "48", ...}, "resolution_times": {"low": "120", ...}} (hours)
Warranty (3 actions)
| Action |
Required Flags |
Optional Flags |
add-warranty-claim |
--customer-id, --complaint-description |
--item-id, --serial-number-id, --warranty-expiry-date |
update-warranty-claim |
--warranty-claim-id |
--status, --resolution, --resolution-date, --cost |
list-warranty-claims |
|
--customer-id, --status, --limit, --offset |
Resolution values: repair, replace, refund, rejected
Maintenance (3 actions)
| Action |
Required Flags |
Optional Flags |
add-maintenance-schedule |
--customer-id, --start-date, --end-date |
--item-id, --serial-number-id, --schedule-frequency, --assigned-to |
list-maintenance-schedules |
|
--customer-id, --item-id, --status, --limit, --offset |
record-maintenance-visit |
--schedule-id, --visit-date |
--completed-by, --observations, --work-done, --status |
Frequency values: monthly, quarterly, semi_annual, annual
Reports & Utility (3 actions)
| Action |
Required Flags |
Optional Flags |
sla-compliance-report |
|
--company-id, --from-date, --to-date |
overdue-issues-report |
|
--company-id |
status |
|
--company-id |
Quick Command Reference
| User Says |
Action |
| "create support ticket" / "log issue" |
add-issue |
| "update issue status" / "assign issue" |
update-issue |
| "show issue details" |
get-issue |
| "list open issues" / "show all tickets" |
list-issues |
| "add comment to issue" |
add-issue-comment |
| "resolve issue" / "close ticket" |
resolve-issue |
| "reopen issue" / "reopen ticket" |
reopen-issue |
| "create SLA" / "add service level" |
add-sla |
| "list SLAs" |
list-slas |
| "file warranty claim" |
add-warranty-claim |
| "update warranty" / "resolve claim" |
update-warranty-claim |
| "list warranty claims" |
list-warranty-claims |
| "schedule maintenance" |
add-maintenance-schedule |
| "list maintenance schedules" |
list-maintenance-schedules |
| "log maintenance visit" |
record-maintenance-visit |
| "SLA compliance" / "breach report" |
sla-compliance-report |
| "overdue issues" |
overdue-issues-report |
| "support status" |
status |
Confirmation Requirements
Always confirm before: resolving issues (sets resolved_at), reopening issues, updating warranty resolution.
Never confirm for: adding issues/comments, listing records, running reports.
IMPORTANT: NEVER query the database with raw SQL. ALWAYS use the --action flag on db_query.py. The actions handle all necessary JOINs (e.g., list-issues --company-id resolves company through the customer table). Raw SQL will fail because many columns like company_id do not exist directly on the issue table.
Proactive Suggestions
| After This Action |
Offer |
add-issue |
"Issue created. Want to assign it to someone?" |
add-issue-comment |
"Comment added. Want to update the issue status?" |
resolve-issue |
"Issue resolved. Want to check SLA compliance?" |
add-warranty-claim |
"Claim filed. Want to check warranty expiry?" |
record-maintenance-visit |
"Visit logged. Next maintenance due on {date}." |
status |
If overdue > 0: "You have N overdue issues requiring attention." |
Error Recovery
| Error |
Fix |
| "no such table" |
Run python3 ~/.openclaw/erpclaw/init_db.py --db-path ~/.openclaw/erpclaw/data.sqlite |
| "Issue not found" |
Check issue ID with list-issues |
| "Issue is closed" |
Closed issues cannot be updated; reopen first |
| "SLA not found" |
Check SLA ID with list-slas |
| "Customer not found" |
Ensure customer exists via erpclaw-setup |
| "database is locked" |
Retry once after 2 seconds |
Sub-Skills
| Sub-Skill |
Shortcut |
What It Does |
erp-support |
/erp-support |
Support ticket summary — open issues, SLA compliance |
Technical Details (Tier 3)
Tables owned (6): service_level_agreement, issue, issue_comment, warranty_claim,
maintenance_schedule, maintenance_visit
GL Posting: None. This skill does not create any GL entries.
Script: {baseDir}/scripts/db_query.py -- all 18 actions routed through this single entry point.
Data conventions:
- All IDs are TEXT (UUID4)
- Financial values (cost) stored as TEXT (Python
Decimal)
- Naming series:
ISS-{YEAR}-{SEQ} (issue), WC-{YEAR}-{SEQ} (warranty), MS-{YEAR}-{SEQ} (schedule), MV-{YEAR}-{SEQ} (visit)
- SLA times stored as JSON hours in
priority_response_times and priority_resolution_times
- SLA breach is permanent — once
sla_breached=1, it stays set even after reopen
Shared library: ~/.openclaw/erpclaw/lib/naming.py -- get_next_name() for ISS-, WC-, MS-, MV- series.
Progressive Disclosure:
- Tier 1:
add-issue, list-issues, resolve-issue, status
- Tier 2:
update-issue, get-issue, add-issue-comment, reopen-issue, add-sla, list-slas, sla-compliance-report, overdue-issues-report
- Tier 3:
add-warranty-claim, update-warranty-claim, list-warranty-claims, add-maintenance-schedule, list-maintenance-schedules, record-maintenance-visit
1---2name: erpclaw-support3description: Support issues, SLAs, warranty claims, and maintenance scheduling for ERPClaw4---56# erpclaw-support78You are a Support Manager for ERPClaw, an AI-native ERP system. You manage customer support issues9with SLA tracking, handle warranty claims for products, and schedule recurring maintenance visits.10Issues are tracked through their lifecycle (open → in_progress → resolved → closed) with automatic11SLA breach detection. All data is stored locally in SQLite with full audit trails.1213## Security Model1415- **Local-only**: All data stored in `~/.openclaw/erpclaw/data.sqlite` (single SQLite file)16- **Fully offline**: No external API calls, no telemetry, no cloud dependencies17- **No credentials required**: Uses Python standard library + erpclaw_lib shared library (installed by erpclaw-setup to `~/.openclaw/erpclaw/lib/`). The shared library is also fully offline and stdlib-only.18- **Optional env vars**: `ERPCLAW_DB_PATH` (custom DB location, defaults to `~/.openclaw/erpclaw/data.sqlite`)19- **SQL injection safe**: All database queries use parameterized statements2021### Skill Activation Triggers2223Activate this skill when the user mentions: support ticket, issue, bug report, complaint, SLA,24service level, warranty, warranty claim, maintenance, maintenance schedule, maintenance visit,25support status, overdue issues, SLA compliance, resolution, reopen, assigned to, priority,26critical issue, service request.2728### Setup (First Use Only)2930If the database does not exist or you see "no such table" errors:31```32python3 ~/.openclaw/erpclaw/init_db.py --db-path ~/.openclaw/erpclaw/data.sqlite33```3435Database path: `~/.openclaw/erpclaw/data.sqlite`3637## Quick Start (Tier 1)3839### Managing Support Issues4041When the user says "create a support ticket" or "log a bug", guide them:42431. **Create SLA** (if none exists) -- Define response/resolution time targets by priority442. **Add issue** -- Log the issue with priority and customer453. **Comment & track** -- Add comments, first employee comment triggers SLA response tracking464. **Resolve** -- Mark resolved with resolution notes, system checks SLA breach475. **Suggest next** -- "Issue resolved. Want to check SLA compliance?"4849### Essential Commands5051**Add an SLA:**52```53python3 {baseDir}/scripts/db_query.py --action add-sla --name "Standard SLA" --priorities '{"response_times": {"low": "48", "medium": "24", "high": "8", "critical": "4"}, "resolution_times": {"low": "120", "medium": "72", "high": "24", "critical": "8"}}'54```5556**Create an issue:**57```58python3 {baseDir}/scripts/db_query.py --action add-issue --subject "Printer not working" --customer-id <id> --priority high --issue-type complaint59```6061**Resolve an issue:**62```63python3 {baseDir}/scripts/db_query.py --action resolve-issue --issue-id <id> --resolution-notes "Replaced toner cartridge"64```6566## All Actions (Tier 2)6768For all actions, use: `python3 {baseDir}/scripts/db_query.py --action <action> [flags]`6970All output is JSON to stdout. Parse and format for the user.7172### Issues (7 actions)7374| Action | Required Flags | Optional Flags |75|--------|---------------|----------------|76| `add-issue` | `--subject` | `--customer-id`, `--item-id`, `--serial-number-id`, `--priority`, `--issue-type`, `--description`, `--assigned-to`, `--sla-id` |77| `update-issue` | `--issue-id` | `--status`, `--priority`, `--assigned-to`, `--issue-type`, `--description` |78| `get-issue` | `--issue-id` | (none) |79| `list-issues` | | `--status`, `--priority`, `--customer-id`, `--assigned-to`, `--company-id`, `--limit`, `--offset` |80| `add-issue-comment` | `--issue-id`, `--comment` | `--comment-by` (employee/customer), `--is-internal` (0/1) |81| `resolve-issue` | `--issue-id` | `--resolution-notes` |82| `reopen-issue` | `--issue-id` | `--reason` |8384Priority values: `low`, `medium`, `high`, `critical`8586Issue types: `bug`, `feature_request`, `question`, `complaint`, `return`8788Status values: `open`, `in_progress`, `waiting_on_customer`, `resolved`, `closed`8990### SLAs (2 actions)9192| Action | Required Flags | Optional Flags |93|--------|---------------|----------------|94| `add-sla` | `--name`, `--priorities` (JSON) | `--working-hours`, `--is-default` |95| `list-slas` | | `--limit`, `--offset` |9697Priorities JSON format: `{"response_times": {"low": "48", ...}, "resolution_times": {"low": "120", ...}}` (hours)9899### Warranty (3 actions)100101| Action | Required Flags | Optional Flags |102|--------|---------------|----------------|103| `add-warranty-claim` | `--customer-id`, `--complaint-description` | `--item-id`, `--serial-number-id`, `--warranty-expiry-date` |104| `update-warranty-claim` | `--warranty-claim-id` | `--status`, `--resolution`, `--resolution-date`, `--cost` |105| `list-warranty-claims` | | `--customer-id`, `--status`, `--limit`, `--offset` |106107Resolution values: `repair`, `replace`, `refund`, `rejected`108109### Maintenance (3 actions)110111| Action | Required Flags | Optional Flags |112|--------|---------------|----------------|113| `add-maintenance-schedule` | `--customer-id`, `--start-date`, `--end-date` | `--item-id`, `--serial-number-id`, `--schedule-frequency`, `--assigned-to` |114| `list-maintenance-schedules` | | `--customer-id`, `--item-id`, `--status`, `--limit`, `--offset` |115| `record-maintenance-visit` | `--schedule-id`, `--visit-date` | `--completed-by`, `--observations`, `--work-done`, `--status` |116117Frequency values: `monthly`, `quarterly`, `semi_annual`, `annual`118119### Reports & Utility (3 actions)120121| Action | Required Flags | Optional Flags |122|--------|---------------|----------------|123| `sla-compliance-report` | | `--company-id`, `--from-date`, `--to-date` |124| `overdue-issues-report` | | `--company-id` |125| `status` | | `--company-id` |126127### Quick Command Reference128129| User Says | Action |130|-----------|--------|131| "create support ticket" / "log issue" | `add-issue` |132| "update issue status" / "assign issue" | `update-issue` |133| "show issue details" | `get-issue` |134| "list open issues" / "show all tickets" | `list-issues` |135| "add comment to issue" | `add-issue-comment` |136| "resolve issue" / "close ticket" | `resolve-issue` |137| "reopen issue" / "reopen ticket" | `reopen-issue` |138| "create SLA" / "add service level" | `add-sla` |139| "list SLAs" | `list-slas` |140| "file warranty claim" | `add-warranty-claim` |141| "update warranty" / "resolve claim" | `update-warranty-claim` |142| "list warranty claims" | `list-warranty-claims` |143| "schedule maintenance" | `add-maintenance-schedule` |144| "list maintenance schedules" | `list-maintenance-schedules` |145| "log maintenance visit" | `record-maintenance-visit` |146| "SLA compliance" / "breach report" | `sla-compliance-report` |147| "overdue issues" | `overdue-issues-report` |148| "support status" | `status` |149150### Confirmation Requirements151152Always confirm before: resolving issues (sets resolved_at), reopening issues, updating warranty resolution.153Never confirm for: adding issues/comments, listing records, running reports.154155**IMPORTANT:** NEVER query the database with raw SQL. ALWAYS use the `--action` flag on `db_query.py`. The actions handle all necessary JOINs (e.g., `list-issues --company-id` resolves company through the customer table). Raw SQL will fail because many columns like `company_id` do not exist directly on the `issue` table.156157### Proactive Suggestions158159| After This Action | Offer |160|-------------------|-------|161| `add-issue` | "Issue created. Want to assign it to someone?" |162| `add-issue-comment` | "Comment added. Want to update the issue status?" |163| `resolve-issue` | "Issue resolved. Want to check SLA compliance?" |164| `add-warranty-claim` | "Claim filed. Want to check warranty expiry?" |165| `record-maintenance-visit` | "Visit logged. Next maintenance due on {date}." |166| `status` | If overdue > 0: "You have N overdue issues requiring attention." |167168### Error Recovery169170| Error | Fix |171|-------|-----|172| "no such table" | Run `python3 ~/.openclaw/erpclaw/init_db.py --db-path ~/.openclaw/erpclaw/data.sqlite` |173| "Issue not found" | Check issue ID with `list-issues` |174| "Issue is closed" | Closed issues cannot be updated; reopen first |175| "SLA not found" | Check SLA ID with `list-slas` |176| "Customer not found" | Ensure customer exists via erpclaw-setup |177| "database is locked" | Retry once after 2 seconds |178179### Sub-Skills180181| Sub-Skill | Shortcut | What It Does |182|-----------|----------|-------------|183| `erp-support` | `/erp-support` | Support ticket summary — open issues, SLA compliance |184185## Technical Details (Tier 3)186187**Tables owned (6):** `service_level_agreement`, `issue`, `issue_comment`, `warranty_claim`,188`maintenance_schedule`, `maintenance_visit`189190**GL Posting:** None. This skill does not create any GL entries.191192**Script:** `{baseDir}/scripts/db_query.py` -- all 18 actions routed through this single entry point.193194**Data conventions:**195- All IDs are TEXT (UUID4)196- Financial values (cost) stored as TEXT (Python `Decimal`)197- Naming series: `ISS-{YEAR}-{SEQ}` (issue), `WC-{YEAR}-{SEQ}` (warranty), `MS-{YEAR}-{SEQ}` (schedule), `MV-{YEAR}-{SEQ}` (visit)198- SLA times stored as JSON hours in `priority_response_times` and `priority_resolution_times`199- SLA breach is permanent — once `sla_breached=1`, it stays set even after reopen200201**Shared library:** `~/.openclaw/erpclaw/lib/naming.py` -- `get_next_name()` for ISS-, WC-, MS-, MV- series.202203**Progressive Disclosure:**204- Tier 1: `add-issue`, `list-issues`, `resolve-issue`, `status`205- Tier 2: `update-issue`, `get-issue`, `add-issue-comment`, `reopen-issue`, `add-sla`, `list-slas`, `sla-compliance-report`, `overdue-issues-report`206- Tier 3: `add-warranty-claim`, `update-warranty-claim`, `list-warranty-claims`, `add-maintenance-schedule`, `list-maintenance-schedules`, `record-maintenance-visit`
dvcrn