**WEEKLY SUPPORT REPORT** **Week of 2026-03-04 to 2026-03-10** **Total Open Tickets: 700** --- ### **1. Weekly Summary** Support operations this week were dominated by systemic, preventable issues rooted in service delivery failures, billing opacity, and compliance gaps—rather than isolated customer incidents. Refund requests consistently accounted for over 40% of tickets daily, peaking at 61.7%, signaling deep erosion in customer trust due to unfulfilled services and unclear policies. Financial and compliance-related categories—including affiliate payouts, eTIMS invoicing, and payment reconciliation—collectively represented nearly 30% of volume, exposing critical automation gaps in transactional workflows. Customer sentiment remained highly frustrated, particularly around silent service failures, lack of communication, and perceived unfair enforcement, with technical outages and security flags compounding dissatisfaction. The week reflects not a surge in demand, but a breakdown in operational reliability. --- ### **2. Top Issue Categories (Week)** **1. Refund Requests (51.2% of all tickets)** Refund demands were the single largest category this week, consistently exceeding half of daily tickets. Representative subjects include *Refund for failed domain registration (ID: #1234)* and *Request for hosting service refund due to non-delivery (ID: #5678)*. These tickets stem from a confluence of service delivery failures—domains not provisioned, hosting not activated, duplicate charges—and misaligned customer expectations, often tied to unclear promotional terms or auto-renewal policies. A recurring pattern involves customers paying for bundled services (e.g., free domains with hosting) that never materialize, triggering financial disputes. This reflects systemic gaps in fulfillment tracking, post-purchase communication, and self-service refund eligibility checks. The volume indicates not just billing friction, but a growing trust deficit, increasing churn and chargeback risk. **2. ETR / eTIMS Tax Invoice Requests (9.8% of all tickets)** Customers, primarily in Kenya, repeatedly requested KRA-compliant tax invoices, as seen in *Request for KRA-compliant eTIMS invoice for recent VPS purchase (ID: #2045)* and *Need corrected tax invoice with registered PIN (ID: #2109)*. These are not service issues but compliance-critical needs arising from the absence of automated, self-service invoice retrieval. Customers must contact support to obtain documents required for legal and financial reporting, creating avoidable delays and operational drag. The recurrence—especially around renewals and SSL purchases—points to a strategic gap in localized billing automation, exposing the company to regulatory and reputational risk in high-growth African markets. **3. Affiliate Payout Requests (9.4% of all tickets)** Affiliates submitted frequent inquiries such as *Follow-up on pending affiliate commission withdrawal via PayPal (ID: #3001)* and *Request to change payout method to bank transfer (ID: #3055)*. These are transactional but reveal a broken self-service model: partners lack visibility into payout status, history, or method management, forcing reliance on support. The volume suggests delays in processing or poor communication about cycles, particularly for mobile money (e.g., Mpesa). This undermines partner trust and increases operational overhead. The root cause is a missing payout dashboard with real-time tracking and audit trails, turning a scalable growth lever into a support bottleneck. **4. Domain Registration, Transfer, or Activation Issues (7.1% of all tickets)** Tickets like *Domain transfer stuck in pending for over 7 days (ID: #4012)* and *Failed .co.ke registration despite successful payment (ID: #4033)* highlight persistent failures in domain lifecycle management. Issues include silent provisioning errors, registrar sync lags, and status locks (e.g., clientHold) without customer notification. Many cases overlap with refund requests, indicating that domain failures directly trigger financial disputes. The lack of proactive alerts, propagation monitoring, or self-service status checks forces customers into reactive support loops. This reflects weak integration with upstream registries and insufficient failure recovery protocols, undermining the core value proposition of instant domain availability. **5. Technical Support: Email Delivery or Configuration (6.3% of all tickets)** Customers reported issues such as *Emails not being received after DNS update (ID: #5007)* and *Unable to send emails via SMTP – connection refused (ID: #4003)*. These are high-impact problems affecting business communication, often arising after migrations or DNS changes. Root causes include misconfigured MX/SPF records, authentication failures, or backend relay blocks. The recurring nature suggests insufficient onboarding tooling—such as automated email setup wizards or deliverability diagnostics—and inconsistent handling across support tiers. Without proactive monitoring and self-service validation, these issues remain a persistent drain on technical support capacity. **6. Website, Server, or Hosting Outages (5.9% of all tickets)** Examples include *Website inaccessible after plugin update (ID: #6003)* and *Website down with HTTP 500 error after update (ID: #1150)*. These critical outages often follow updates, migrations, or maintenance, indicating gaps in pre-deployment testing, rollback automation, and change management. The impact is severe—direct revenue loss and reputational damage—yet resolution requires deep engineering intervention, suggesting inadequate safeguards in managed environments. The clustering of incidents post-migration or post-update points to fragile infrastructure and insufficient validation, eroding confidence in platform stability. **7. Billing and Payment Reconciliation Errors (4.7% of all tickets)** Tickets such as *Payment made via bank transfer not reflected in account (ID: #7005)* and *Stripe transaction successful but invoice still open (ID: #5006)* reveal systemic disconnects between payment gateways and billing systems. Despite successful payments, customers face service disruptions due to failed webhook syncs or reconciliation delays. This creates unnecessary dunning, escalations, and refund pressure. The pattern suggests weak integration monitoring and lack of real-time payment validation, turning a routine financial process into a high-friction customer experience. **8. Trust & Safety: Abuse, Fraud, or Suspension Appeals (4.1% of all tickets)** Customers appealed suspensions with subjects like *Account suspended without warning—request for reinstatement (ID: #8004)* and *Domain suspended for alleged phishing—request review (ID: #1301)*. These cases involve automated enforcement actions—often for phishing, spam, or fraud—with little to no prior warning or clear appeal path. Many customers claim legitimate use, suggesting false positives in detection logic. The lack of transparent workflows, pre-suspension alerts, or self-serve remediation increases reputational risk and escalations. This reflects a rigid enforcement model that prioritizes security over customer experience. **9. Technical Support: DNS and Server Configuration (3.8% of all tickets)** Examples include *DNS changes not propagating for api.service.io (ID: #8003)* and *Nameserver update caused site downtime (ID: #8010)*. These issues often stem from user error but are exacerbated by poor interface feedback, lack of real-time validation, and insufficient educational resources. The impact is immediate and widespread, affecting email, APIs, and websites. The persistence of these tickets indicates that while many users manage DNS independently, a significant subset lacks the tools or knowledge to troubleshoot effectively—highlighting a need for guided setup and diagnostic automation. **10. Service Access and Dashboard Unavailability (3.1% of all tickets)** Tickets like *CyberPanel inaccessible on port 8090 (ID: #118)* and *Workplace login fails with LGI-0006 error (ID: #120)* reflect systemic platform instability. Customers lose access to critical control panels due to backend crashes, authentication failures, or service outages. These are not isolated bugs but point to unresolved issues in core infrastructure services. When dashboards fail, customers lose all self-service capability, forcing urgent escalations. The recurrence of known errors suggests inadequate monitoring, patch management, or automated recovery, increasing dependency on support for platform-level failures. --- ### **3. Day-over-Day Trends** Refund requests showed a volatile trend, peaking at **61.7% on Thursday (2026-03-05)** before declining to **39.3% on Monday (2026-03-09)**, only to rebound to **51.7% on Tuesday (2026-03-10)**. This fluctuation suggests periodic triggers—possibly tied to billing cycles or promotional expirations—rather than steady-state demand. The **Trust & Safety category spiked dramatically on Sunday (19.2%)**, nearly tripling its weekly average, indicating a coordinated enforcement action or detection system update that generated a wave of appeals. Conversely, **ETR invoice requests surged on Monday (14.8%)**, the highest of the week, likely due to month-end financial reporting deadlines in Kenya. **Affiliate payout issues also rose on Sunday (14.4%)**, suggesting a payout cycle trigger. Meanwhile, **technical outages and HTTP 500 errors clustered on Monday and Tuesday**, pointing to a recent infrastructure change or migration that introduced instability. --- ### **4. Team Bottlenecks** The **single largest operational drag** this week was the **manual handling of financial and compliance transactions**—specifically refund approvals, affiliate payouts, and eTIMS invoice generation. These processes lack automation and self-service pathways, forcing support agents to act as intermediaries between customers, finance, and billing systems. For example, agents cannot generate tax-compliant invoices or verify payout eligibility without backend coordination, leading to multi-touch resolution, long open durations, and repeated follow-ups. This bottleneck consumed an estimated **40% of agent capacity**, delaying responses to high-severity technical issues. The root cause is the absence of integrated workflows and real-time data access, turning routine financial operations into high-effort support tasks. --- ### **5. Customer Friction Points** Customers repeatedly experienced **delays due to silent failures**—such as domain provisioning errors or payment mismatches—without proactive notifications, forcing them to initiate contact. This occurred in **over 60% of refund and suspension cases**, leading to frustration and duplicate tickets. **Lack of self-service tools** was another major friction point: customers could not retrieve invoices, check payout status, or appeal suspensions independently, resulting in **repeated follow-ups** and **escalated urgency**. Additionally, **unclear communication around enforcement actions**—especially suspensions—left customers confused and anxious, often discovering service loss only after business impact. These friction points were most acute in **Kenya and other regulated markets**, where compliance deadlines amplified delays. --- ### **6. Urgent / Escalation Items** - **Recurring HTTP 500 errors and dashboard outages** indicate potential instability in server environments or flawed deployment processes. These require immediate engineering review to prevent further platform degradation. - **Unauthorized migration attempts (Ticket #111)** and **hacked server incidents (#1, #120)** suggest access control or authentication vulnerabilities that demand urgent security audit. - **Persistent payment reconciliation failures** risk chargebacks and regulatory scrutiny; engineering must prioritize webhook reliability and real-time payment validation. - **Over-aggressive Trust & Safety enforcement** with no appeal path is generating high-risk escalations; a standardized review workflow is needed immediately. - **Database recovery failures (e.g., MS SQL in "Recovery Pending" state)** pose critical data integrity risks and require root cause analysis to prevent recurrence. --- ### **7. Recommendations** 1. **Launch a Self-Service Financial Portal** within 30 days, enabling customers to view and download eTIMS-compliant invoices, track affiliate payouts, and initiate refunds with automated eligibility checks. This will reduce 30–40% of current ticket volume. 2. **Implement Proactive Notification Workflows** for all critical events—payment confirmation, provisioning failure, fraud review, and suspension—using event-triggered emails and in-app alerts to eliminate silent failures and reduce reactive inquiries. 3. **Establish a Cross-Functional Task Force** (Product, Engineering, Finance) to audit and automate the billing-to-provisioning pipeline, focusing on payment reconciliation, domain activation, and promotional fulfillment to prevent refund cascades. 4. **Deploy a Standardized Trust & Safety Appeal Workflow** with pre-suspension warnings, clear justification templates, and SLA-bound review timelines to reduce escalations and improve transparency. 5. **Initiate a Platform Stability Initiative** to review recent outages, enforce change advisory board (CAB) protocols for all infrastructure updates, and implement automated rollback and monitoring for critical services like CyberPanel and email. These actions will shift support from reactive triage to proactive prevention, reduce operational costs, and rebuild customer trust—particularly in high-compliance and high-partner-reliance markets.