TinyTap customer service — professional operations guide

Overview and purpose

TinyTap is a digital learning platform used by parents, teachers, and school districts. This guide explains how to design and run a customer service operation that reduces churn, improves learning outcomes, and supports educators’ workflows. It focuses on measurable processes, timing, and real-world scripts you can deploy immediately — not generic platitudes.

Use this as a playbook if you manage TinyTap support in-house, operate a reseller helpdesk, or are a consultant aligning support SLAs to product and business goals. The recommendations below are deliberately concrete: response time targets, escalation thresholds, sample messages, and tracking metrics that experienced support managers can implement in the next 7–30 days.

Channels and routing

Offer at least three supported channels: in-app chat for fast triage, email for asynchronous issues and attachments, and a public help center with searchable articles and short videos. In-app chat should be enabled in the mobile/desktop app and routed via an omnichannel platform (e.g., Zendesk, Intercom, Freshdesk) so agents see user context (account type, last activity, subscription status).

Route inbound contacts with automated priority rules. Example routing logic: priority 1 (billing failures, classroom outages) → routed to a senior agent within 15 minutes; priority 2 (content creation bugs, teacher onboarding) → routed within 2 hours; priority 3 (general how-to, feature requests) → routed within 24 hours. These rules keep urgent educational disruptions from escalating during class time.

Operational SLAs and KPIs

Define clear SLAs and measure them daily and weekly. Public-facing SLAs improve trust with paying customers and school IT administrators. Internally, publish a living dashboard with the metrics below and use them in weekly ops reviews.

• Initial response time target: ≤1 hour for Priority 1 during business hours; ≤4 hours for Priority 2; ≤24 hours for Priority 3.
• Average resolution time: target ≤24 hours for standard issues, ≤72 hours for complex cases requiring engineering input.
• First Contact Resolution (FCR): aim for 70–85% on basic issues (password resets, billing queries) and track separately for teacher vs. parent segments.
• Customer Satisfaction (CSAT): target ≥4.5/5 collected after case closure; Net Promoter Score (NPS) quarterly target ≥30 for paid segments.
• Ticket backlog: keep aging tickets (>7 days) <5% of open queue; critical incidents must have dedicated incident owners until closed.

Escalation matrix and engineering collaboration

Design an escalation matrix with named roles, response time windows, and actions. Example matrix: level 1 agent → level 2 specialist (within 2 hours) → product owner (within 8 hours) → engineering incident lead (within 24 hours). Capture owner, phone/email, and required status updates (every 2 hours for Priority 1 incidents during remediation).

Use a single source of truth for incident status (status page + internal Slack channel). Publish incident post-mortems within 48 hours of resolution with root cause, mitigation, corrective actions, and timeline. Track recurring bugs and link them to engineering sprints so support inputs feed product decisions.

Knowledge base, self-service, and content strategy

High-quality self-service reduces support volume by 30–50% if executed correctly. Build a help center with short articles (300–500 words), annotated screenshots, 2–3 minute tutorial videos, and printable classroom handouts. Tag content by persona (teacher, parent, IT admin) and by intent (billing, classroom setup, content creation).

Maintain a versioned FAQ for each app release. For every support ticket, require the agent to add one new knowledge base entry or improve an existing one once a week — this operational rule creates continuous content improvement and reduces repeat contacts over time.

Billing, refunds, and account management

Standardize billing workflows and templated responses. Recommended refund policy (example template for teams): full refund if requested within 14 days of purchase for annual subscriptions; prorated refunds for mid-year cancellations for district accounts with administrative approval. Always log financial exceptions and require manager-level approval for non-standard refunds above $200.

Provide an account reconciliation checklist for billing inquiries: verify transaction ID, user email, subscription SKU, purchase date, and payment processor (Stripe, PayPal). Typical turnaround for verified billing adjustments should be ≤72 hours; urgent reversals for duplicate charges should be handled within 24 hours.

Handling educators and schools — practical steps

Teacher and district support differs from consumer support. For teacher onboarding, create a 30-minute guided implementation workflow: account setup, class roster import (CSV), device provisioning, and a sandbox lesson. Offer a “train-the-trainer” 60–90 minute webinar for district IT and lead teachers; track attendance and follow-up within 48 hours with tailored materials.

For school IT teams, maintain a technical checklist with required ports, minimum device specs (Chrome/Edge latest, iOS 13+, Android 9+), and recommended MDM settings. Provide a designated enterprise support channel or SLA for district contracts — typical contract SLA: 4-hour initial response and weekly status reports until complete.

Sample operational contacts and resources

Centralized contacts to publish internally: [email protected] for general cases, [email protected] for escalations, and [email protected] for reseller and district account inquiries. Public resources should live at https://www.tinytap.com/help with a status page (e.g., https://status.tinytap.com) linked from the app.

Track outcomes: run monthly cohort reports showing support volume by channel, average handle time, churn correlated to unresolved tickets, and classroom uptime. These reports inform staffing (e.g., 1 support full-time employee per 2,500 monthly active users is a useful baseline) and budgeting decisions.