# **Weekly Support Report: 2026-02-25 to 2026-03-03** --- ### **1. Weekly Summary** Support operations this week were dominated by systemic service delivery failures, with refund requests and unresolved domain provisioning issues accounting for nearly half of all tickets. A surge in automated monitoring alerts and persistent infrastructure instability—particularly on DAS servers—further strained team capacity. Customer frustration is escalating due to unmet expectations around service activation, billing accuracy, and timely resolutions, signaling urgent needs for process automation, infrastructure stabilization, and clearer customer communication. --- ### **2. Top Issue Categories (Week)** | **Category** | **Est. % of All Tickets** | **Representative Ticket Subjects** | **Pattern Description** | |-------------|----------------------------|------------------------------------|--------------------------| | **Refund Requests** | **~35%** | "Refund for domain and hosting not activated", "Double charge for VPS – request reversal", "No service provided after payment – request full refund" | The dominant issue across all days. Driven by failed service provisioning (hosting, domains), duplicate charges, and customer dissatisfaction. Often linked to upstream technical failures or unclear billing communication. | | **Domain Registration/Transfer Problems** | **~15%** | "Domain transfer stuck in pending status", "Failed domain registration due to registrar error", "EPP code retrieval failure" | Persistent issues with domain provisioning via ConnectReseller: registrar locks, domains <60 days old, IPS tag mismatches, and fraud flags. Frequently leads to refund demands and customer churn. | | **Automated Monitoring Alerts (UptimeRobot)** | **~12%** | "Server X is down – uptime monitor alert", "HTTP 500 error on das112", "Service fluctuating – timeout alerts" | High-volume automated alerts from UptimeRobot indicating brief outages or timeouts. Most are transient and auto-resolved, but flood the queue with non-actionable noise. | | **Email/Delivery & Configuration Issues** | **~9%** | "SMTP relay access denied", "Incoming emails not arriving", "Emails blocked by Gmail spam filters" | Recurring problems with outbound/inbound mail delivery due to missing DKIM/SPF, IP reputation, or relay restrictions. Often requires abuse or infrastructure team intervention. | | **Affiliate Payout & Withdrawal Issues** | **~7%** | "Withdraw $240 commission via PayPal", "Affiliate balance not showing", "Payout method not visible" | Users unable to withdraw commissions due to UI bugs, missing payout methods, or backend processing delays. High financial sensitivity and risk of partner dissatisfaction. | | **Billing Disputes / Unauthorized Charges** | **~6%** | "Charged for SSL I never ordered", "Invoice does not belong to my account", "Unauthorized KES 4,959 charge" | Customers disputing unrecognized or duplicate charges. Often tied to missing opt-in confirmations, invoice mismatches, or failed payment reconciliation. | | **VPS/Server Performance & Security** | **~5%** | "VPS extremely slow with frequent downtime", "VPS compromised by cryptominer", "Cannot access CWP panel" | Performance degradation, SSH access failures, and cryptomining compromises. Indicates infrastructure vulnerabilities and lack of proactive monitoring. | | **ETR/eTIMS Tax Receipt Requests** | **~4%** | "Need ETIM-compliant certificate for KRA filing", "Missing eTIMS receipt for last month’s payment" | Compliance-driven requests from Kenyan customers requiring tax-compliant documentation. Manual handling creates avoidable workload. | | **Hosting Provisioning & Access Failures** | **~4%** | "Payment confirmed but hosting account not created", "Locked out of cPanel despite active payment" | Paid services not activated or suspended without notice. Points to gaps in fulfillment automation and communication. | | **SSL Certificate Issues** | **~3%** | "SSL not received after 48 hours", "Verification email missing", "Installation failure due to SSH access" | Delays in issuance, missing verification emails, or installation blocked by access issues. Often cascades into refund requests. | --- ### **3. Day-over-Day Trends** - **Refund requests spiked sharply from 22% (Wed) to 60% (Tue)**, peaking on **Tuesday, 2026-03-03**, indicating a compounding effect of unresolved provisioning issues and billing errors. - **UptimeRobot alerts surged on Saturday (25%)**, coinciding with widespread HTTP 500 errors and timeouts across DAS servers (das103–das116), suggesting a potential infrastructure-wide event. - **Domain transfer issues declined from 32% (Wed) to 7% (Tue)**, but were replaced by **service activation failures (2.6%) and domain status issues (2.6%)**, indicating a shift from transfer problems to post-payment fulfillment gaps. - **ETR receipt requests emerged as a consistent 3–4% daily category**, particularly on **Sunday and Tuesday**, highlighting growing regulatory demand. - **Phishing reports appeared for the first time on Monday**, with multiple tickets reporting spoofed emails from `info@truehost.cloud`, indicating a new security threat vector. --- ### **4. Team Bottlenecks** **Biggest Bottleneck: Lack of Automated Fulfillment & Refund Triage** The single largest drag on support throughput was the **manual handling of refund requests and service activation failures**, both stemming from broken or opaque fulfillment pipelines. Over **35% of tickets were refund-related**, many tied to services that were paid for but never provisioned—yet no automated system exists to detect, validate, or process these claims. Support agents are forced to escalate repeatedly to billing and engineering teams, often with no resolution timeline. This creates **multi-touch ticket cycles**, with average resolution times exceeding 72 hours. Additionally, **UptimeRobot alerts (12% of tickets)** are routed as individual support tickets despite being automated and often self-resolving. This **unnecessary ticket noise** consumes ~200+ tickets weekly that could be filtered or aggregated. **Impact:** Estimated **40–50% of support capacity** was spent on **repetitive refund processing, escalations, and non-actionable alerts**, severely limiting bandwidth for complex technical issues. --- ### **5. Customer Friction Points** 1. **"Paid but Not Delivered" Experience (High Frequency)** Customers paid for domains, hosting, or VPS but received no access or confirmation. Many reported being locked out or seeing "pending" statuses for days. Required multiple follow-ups, often ending in refund requests. *Customer perspective:* “I paid, but nothing works. No one tells me why or when it will be fixed.” 2. **Refund Delays & Lack of Communication (Very High Frequency)** Refund requests took days to process, with no status updates. Customers escalated with legal threats or public complaints. *Customer perspective:* “I asked for a refund a week ago. No response. I feel ignored and scammed.” 3. **Affiliate Payout Delays & UI Confusion (Moderate-High Frequency)** Affiliates submitted withdrawal requests but saw no movement. Some reported balances not updating or payout options disappearing. *Customer perspective:* “I earned $600, but the button doesn’t work. No one explains why.” 4. **Silent Suspensions & Access Loss (Moderate Frequency)** Accounts were suspended without warning, taking websites and emails offline. Restoration required manual support intervention. *Customer perspective:* “My site went down with no notice. I lost business and trust.” 5. **Phishing Scams Using Brand Identity (Emerging)** Customers received spoofed emails and feared account compromise. Support had no protocol to warn others or investigate. *Customer perspective:* “I got an urgent email from 'TrueHost' asking for login. Is this real?” --- ### **6. Urgent / Escalation Items** - **Recurring VPS Cryptomining Compromises**: Multiple confirmed cases of unauthorized cryptominers on VPS instances. **Requires immediate security audit, patch management review, and enhanced monitoring.** - **DAS Server Instability**: Persistent HTTP 500 errors and timeouts across das103–das116. **Infrastructure team must investigate resource bottlenecks or configuration drift.** - **Phishing Campaign Using `info@truehost.cloud`**: Active spoofing of support identity. **Urgent need for DMARC enforcement and brand abuse monitoring.** - **Broken Domain Provisioning Pipeline**: High fraud flags, EPP code failures, and registration delays. **Registrar (ConnectReseller) integration requires urgent review.** - **Affiliate Payout System Failure**: Payouts not processing despite threshold met. **Risk of partner churn and reputational damage.** --- ### **7. Recommendations** 1. **Implement Automated Refund & Fulfillment Triage** Build rules to auto-detect and process refunds for common scenarios (e.g., failed domain registration, unprovisioned hosting). Integrate with billing and provisioning systems to reduce manual escalations. 2. **Filter & Aggregate UptimeRobot Alerts** Route automated monitoring alerts to a dedicated internal dashboard or summary ticket—**not individual support tickets**. Only escalate if outages persist beyond 15 minutes. 3. **Launch Self-Service Portals for High-Friction Areas** - **Affiliate Payout Portal**: Secure, branded interface for withdrawal requests. - **ETR/eTIMS Receipt Generator**: Auto-issue tax-compliant receipts post-payment. - **Domain Status Tracker**: Real-time visibility into transfer/registration progress. 4. **Initiate Infrastructure Stabilization Task Force** Convene engineering, security, and support leads to: - Audit DAS server performance - Patch VPS security gaps - Enforce DMARC/SPF to combat phishing 5. **Proactive Customer Communication Protocol** Automate notifications for: - Domain transfer delays - Service suspensions (with reason and resolution ETA) - Refund processing status Reduce inbound follow-ups and build trust. --- **Prepared by:** Senior Support Analytics Assistant **Date:** 2026-03-04