The Three Tiers of Technical Support in Web Hosting
In web hosting and managed services, technical support is organised into three tiers — Level 1, Level 2, and Level 3 — each with a distinct scope of responsibility, required expertise, and escalation path. Understanding these tiers is essential for building an efficient support operation, and critical for designing AI automation that stays within appropriate boundaries.
What Is Level 1 (L1) Technical Support?
Level 1 support is the first point of contact for hosting customers and the monitoring system. L1 engineers handle the most common, well-documented issues — the ones that appear most frequently and have clear, repeatable solutions.
Typical Level 1 support tasks in web hosting:
- Checking whether a website is up or down
- Reviewing error logs for obvious causes
- Answering questions about DNS propagation
- Confirming server resource consumption (CPU, RAM, disk)
- Verifying SSL certificate status
- Restarting services that have clearly crashed
- Checking Exim mail queue size
- Confirming backup job completion
What Is Level 2 (L2) Technical Support?
Level 2 technical support handles incidents that require deeper investigation, more impactful remediation, or coordination across systems. L2 engineers typically have 2-5 years of hosting experience, strong Linux administration skills, and familiarity with the specific control panels and billing systems in use.
Typical Level 2 technical support tasks:
- Diagnosing MySQL performance issues (slow queries, replication lag, InnoDB buffer pool)
- Investigating recurring Apache crashes (worker pool saturation, PHP-FPM misconfiguration)
- Tracing email delivery failures through Exim logs
- Investigating persistent disk space issues
- Diagnosing SSL certificate renewal failures
- Investigating DDoS patterns and configuring mitigation
- Coordinating with hardware vendors on physical server issues
- Reviewing and modifying PHP-FPM pool configurations
In AIOP's governance model, Level 2 actions are those that are reversible and routinely safe — service restarts, log rotation, cache clearing, SSL renewal. These execute automatically without human approval but are logged permanently.
What Is Level 3 (L3) Technical Support?
Level 3 technical support handles the most complex, critical, and potentially irreversible operations. L3 engineers are senior infrastructure specialists — often with 5+ years of hosting experience — who handle escalations from L2 and own architectural decisions.
Typical Level 3 technical support tasks:
- Account suspension or termination decisions
- Production database schema modifications
- Kernel-level investigation and patching
- Major infrastructure migrations
- Security breach investigation and response
- VM deletion or large-scale data operations
- Major configuration changes affecting multiple customers
In AIOP, ALL Level 3 actions require explicit human approval via Slack before execution. The AI proposes the action, provides its reasoning, and waits for an engineer to click Approve. The approval is logged with the engineer's identity, timestamp, and reason. This is enforced in Python code — not in a prompt instruction that could theoretically be bypassed.
How AIOP Implements the Three-Tier Model
The AIOP governance model maps directly to the L1/L2/L3 framework with a critical addition: every action is tracked at the code level, not just in policy documents.
The APPROVED_TOOLS registry in the Tool Executor service (Episode 14) specifies the action level for every command AIOP can execute. Claude can only request tools by name — it cannot specify the actual shell command that runs, and it cannot override the level enforcement:
- Level 1 tools:
check_services,tail_error_log,check_disk_usage,verify_ssl,query_metrics - Level 2 tools:
restart_apache,restart_mysql,restart_php_fpm,force_logrotate,renew_ssl,block_ip - Level 3 tools:
suspend_account,delete_vm,modify_production_config,mass_account_operation
This architecture means AIOP's Level 1 automation is genuinely safe — read-only operations that cannot cause service disruption. Level 2 automation is carefully bounded to reversible, routinely-safe operations. Level 3 operations are guaranteed to require human sign-off regardless of what the AI reasons or is instructed.
The Business Case for Automating L1 and L2 Support
For a hosting company managing 200 servers, a conservative estimate of L1 and L2 support costs might be 2-3 engineers ($6,000-9,000/month in Kenya/East Africa). AIOP automates 80% of L1 tickets and a significant portion of L2 incidents, with a monthly infrastructure cost of approximately $300-500 for the AIOP platform itself.
The ROI is compelling from month one — and grows as server count increases, since the AIOP infrastructure cost scales far more slowly than the support labor it replaces.