Eve library

User Feedback Channels

Tracker

Revision 1

On this page

Historical task source. The Eve task board holds current task state.

This document outlines the various channels for collecting, managing, and responding to user feedback for Tara.


Table of Contents#

  1. Feedback Channel Overview
  2. In-App Feedback
  3. App Store Reviews
  4. Support Email
  5. Social Media
  6. Community Channels
  7. Feedback Triage Process
  8. Reporting and Analytics

Feedback Channel Overview#

Channel Summary#

Channel Type Response SLA Team Responsible
In-App Feedback Feature request 5 business days Product
In-App Bug Report Bug report 48 hours Engineering
iOS App Store Review 24-48 hours Support
Google Play Store Review 24-48 hours Support
Support Email Support ticket 24 hours Support
Twitter/X Social 4 hours Social/Support
Instagram Social 24 hours Social
Facebook Social 24 hours Social
Discord Community Community Community-driven Community

Feedback Categories#

Category Examples Routing
Bug Report Crash, error, broken feature Engineering
Feature Request New feature, enhancement Product
Content Request New meditation type, teacher Content
Account Issue Login, subscription, billing Support
General Feedback Compliment, suggestion, question Support → Product
Complaint Service issue, dissatisfaction Support → Manager

In-App Feedback#

Implementation#

The in-app feedback system captures context automatically.

Feedback Button Location#

  • Settings > Help & Support > Send Feedback
  • Shake gesture (optional, for beta users)
  • Post-meditation prompt (selective)

Feedback Form Fields#

typescript
interface FeedbackSubmission {
  // User provided
  type: 'bug' | 'feature' | 'content' | 'general';
  subject: string;
  description: string;
  screenshot?: File;

  // Auto-captured
  userId: string;
  email: string;
  appVersion: string;
  platform: 'ios' | 'android' | 'web';
  deviceModel: string;
  osVersion: string;
  locale: string;
  timestamp: Date;
  currentScreen: string;
  sessionId: string;
  subscriptionStatus: string;
}

Post-Submission Flow#

text
User submits feedback
         │
         ▼
┌─────────────────────────────────┐
│ Auto-categorize with AI         │
│ (bug vs feature vs general)     │
└─────────────────────────────────┘
         │
         ▼
┌─────────────────────────────────┐
│ Create ticket in helpdesk       │
│ (Zendesk/Intercom/etc)          │
└─────────────────────────────────┘
         │
         ▼
┌─────────────────────────────────┐
│ Send confirmation email         │
│ "We received your feedback"     │
└─────────────────────────────────┘
         │
         ▼
   Route to appropriate team

Bug Report Enrichment#

For bug reports, additional data is captured:

typescript
interface BugReportData extends FeedbackSubmission {
  // Diagnostic data
  logs: string[]; // Last 100 log entries
  crashReport?: string; // If crash occurred
  networkStatus: string; // Online/offline
  memoryUsage: number;
  diskSpace: number;
  batteryLevel: number;

  // Reproduction steps (user provided)
  stepsToReproduce?: string;
  expectedBehavior?: string;
  actualBehavior?: string;
}

In-App Survey Triggers#

yaml
surveys:
  nps_survey:
    trigger: session_count >= 10
    frequency: every_90_days
    question: 'How likely are you to recommend Tara?'
    type: nps (0-10)

  satisfaction_survey:
    trigger: meditation_completed
    frequency: every_7_days
    sample_rate: 10%
    question: 'How was this meditation?'
    type: rating (1-5)

  feature_survey:
    trigger: feature_first_use
    frequency: once_per_feature
    question: 'How useful was this feature?'
    type: rating (1-5)

  exit_survey:
    trigger: subscription_cancelled
    frequency: once
    question: 'Why are you leaving?'
    type: multiple_choice

App Store Reviews#

Review Monitoring#

iOS App Store#

Tool: AppFollow / App Annie / RevenueCat

Monitoring:

  • New review alerts (all ratings)
  • Rating change notifications
  • Keyword alerts (crash, bug, broken)
  • Competitor review monitoring

Response Process:

  1. Review appears in monitoring tool
  2. Auto-categorized by sentiment and topic
  3. Alert sent to #app-reviews Slack channel
  4. Support team responds within 24-48 hours

Google Play Store#

Tool: AppFollow / Google Play Console

Features:

  • Direct reply from Play Console
  • Review translation
  • Rating trend analysis
  • Beta feedback management

Review Response Guidelines#

Response Timing#

Rating Response Priority Target Response
1-2 ⭐ High Within 24 hours
3 ⭐ Medium Within 48 hours
4-5 ⭐ Low Within 72 hours

Response Templates#

Positive Review (4-5 stars):

text
Hi [Name],

Thank you so much for your kind words! We're thrilled that Tara is helping
you with your meditation practice. Your support means the world to us.

Happy meditating! 🙏

- The Tara Team

Constructive Feedback (3-4 stars):

text
Hi [Name],

Thank you for taking the time to share your feedback. We really appreciate
it!

We're always working to improve Tara, and suggestions like yours help us
prioritize. [Specific response to their feedback]

If you have more thoughts, we'd love to hear from you at feedback@tara.app.

- The Tara Team

Negative Review - Bug Report (1-2 stars):

text
Hi [Name],

We're really sorry to hear you're experiencing issues. That's definitely
not the experience we want you to have.

Could you email us at support@tara.app with details about your device and
the specific issue? We'd like to help resolve this for you.

Thank you for your patience.

- The Tara Team

Negative Review - Feature Request (1-2 stars):

text
Hi [Name],

Thank you for sharing your feedback. We understand your frustration and
appreciate you taking the time to let us know.

We're always working on improvements, and we've noted your suggestion for
our product team. We hope to make Tara better for you in future updates.

- The Tara Team

Negative Review - Subscription Issue (1-2 stars):

text
Hi [Name],

We're sorry to hear about your subscription issue. We'd like to help
resolve this right away.

Please reach out to support@tara.app with your account email, and our
team will assist you personally.

- The Tara Team

Review Request Strategy#

When to Ask for Reviews#

Optimal Moments:

  • After completing 5th meditation
  • After reaching a streak milestone (7, 30, 100 days)
  • After completing a course
  • After a positive NPS score (9-10)

Never Ask:

  • During meditation playback
  • Immediately after opening app
  • After an error or crash
  • More than once per 90 days
  • If user has already reviewed

Implementation#

typescript
async function shouldPromptReview(userId: string): Promise<boolean> {
  const user = await getUser(userId);

  // Eligibility checks
  const conditions = [
    user.meditationCount >= 5,
    user.lastReviewPrompt < Date.now() - 90 * DAY,
    !user.hasReviewed,
    !user.recentlyCrashed,
    user.lastNpsScore >= 9 || !user.lastNpsScore,
  ];

  return conditions.every((c) => c === true);
}

Support Email#

Email Configuration#

Primary: support@tara.app

Routing:

Keyword/Topic Route To
billing, charge, refund Billing queue
cancel, subscription Subscription queue
bug, crash, error Technical queue
feature, suggestion Product feedback
content, meditation Content feedback
Default General support

Ticket System Setup#

Tool: Zendesk / Intercom / Helpscout

Configuration:

yaml
queues:
  billing:
    sla: 24h
    priority: high
    team: billing_specialists

  technical:
    sla: 48h
    priority: medium
    team: technical_support
    escalation: engineering

  general:
    sla: 48h
    priority: normal
    team: support_generalists

automations:
  auto_response:
    trigger: new_ticket
    action: send_acknowledgment_email

  urgent_escalation:
    trigger: contains("urgent", "asap", "immediately")
    action: flag_for_review

  vip_routing:
    trigger: customer.subscription == "annual"
    action: prioritize

Email Templates#

Auto-Response:

text
Subject: We received your message [#{{ticket_id}}]

Hi {{customer_name}},

Thank you for reaching out to Tara support. We've received your message
and a team member will respond within 24-48 hours.

In the meantime, you might find these resources helpful:
- Help Center: help.tara.app
- FAQ: tara.app/faq

Your ticket number: #{{ticket_id}}

Namaste,
The Tara Support Team

Resolution:

text
Subject: Re: Your Tara Support Request [#{{ticket_id}}]

Hi {{customer_name}},

{{agent_response}}

If this resolves your issue, no further action is needed. If you have
additional questions, simply reply to this email.

Was this response helpful? Let us know:
👍 Yes, this helped: [Link]
👎 No, I need more help: [Link]

Thank you for being part of the Tara community.

Best,
{{agent_name}}
Tara Support

Social Media#

Platform Presence#

Platform Handle Purpose
Twitter/X @tara_app Updates, support, news
Instagram @tara.meditation Content, community
Facebook @tarameditation Community, support
TikTok @tara.meditation Content, awareness
LinkedIn Tara Meditation B2B, careers

Social Listening#

Tools: Sprout Social / Hootsuite / Brand24

Keywords to Monitor:

  • Brand: "tara app", "tara meditation", "@tara_app"
  • Product: "meditation app", "sleep app", "mindfulness app"
  • Competitors: "headspace", "calm", "insight timer"
  • Issues: "broken", "crash", "won't work", "cancel"

Response Guidelines#

Response SLAs#

Platform Direct Message Public Mention Comment
Twitter/X 2 hours 4 hours 4 hours
Instagram 4 hours 24 hours 24 hours
Facebook 4 hours 24 hours 24 hours

Public vs Private Response#

Respond Publicly When:

  • Positive feedback or testimonial
  • General question (answer helps others)
  • Simple fix or tip

Move to Private When:

  • Account-specific issue
  • Billing or subscription question
  • Complex technical problem
  • Complaint requiring investigation

Template for Moving Private:

text
Thanks for reaching out! We'd like to help you with this.
Please DM us your account email and we'll get this sorted out. 🙏

Crisis Response#

If negative sentiment spikes:

  1. Identify - Is this a real issue or isolated complaint?
  2. Acknowledge - Public acknowledgment within 2 hours
  3. Coordinate - Align messaging with support/engineering
  4. Respond - Consistent, empathetic responses
  5. Update - Provide resolution updates publicly

Community Channels#

Discord Server#

Purpose: Community support, feature discussion, beta testing

Channels:

Channel Purpose Moderation
#welcome Introduction, rules Strict
#general General discussion Moderate
#meditation-talk Meditation practice sharing Light
#feature-requests Feature suggestions Moderate
#bug-reports Bug reporting Moderate
#beta-testers Beta feedback (restricted) Light
#announcements Official updates (read-only) None

Moderation:

  • Community moderators (volunteers)
  • Tara staff presence (not 24/7)
  • Auto-moderation for spam/harassment

Beta Testing Program#

Platform: TestFlight (iOS) / Firebase App Distribution (Android)

Program Structure:

yaml
beta_program:
  tiers:
    alpha:
      size: 50
      access: earliest builds
      feedback: required
      nda: yes

    beta:
      size: 500
      access: feature complete builds
      feedback: encouraged
      nda: no

    public_beta:
      size: 5000
      access: stable beta builds
      feedback: optional
      nda: no

  requirements:
    - Account in good standing
    - At least 30 days as user
    - Agreed to beta terms

  communication:
    channel: discord #beta-testers
    survey: after each release

Feedback Triage Process#

Daily Triage#

Schedule: Every business day, 9 AM

Participants: Support lead, Product representative

Process:

text
1. Review overnight feedback
   - Support tickets
   - App store reviews
   - In-app feedback
   - Social mentions

2. Categorize and tag
   - Bug / Feature / Content / Other
   - Priority level
   - Product area

3. Route to teams
   - Bugs → Engineering backlog
   - Features → Product backlog
   - Content → Content team
   - Urgent → Immediate action

4. Update tracking
   - Log in feedback database
   - Update weekly report

Feedback Categorization#

yaml
categories:
  bugs:
    tags:
      - crash
      - playback-issue
      - login-issue
      - sync-issue
      - performance
      - ui-bug
    routing: engineering

  features:
    tags:
      - new-feature
      - enhancement
      - ui-improvement
      - integration
    routing: product

  content:
    tags:
      - new-meditation
      - teacher-request
      - topic-request
      - translation
    routing: content

  account:
    tags:
      - subscription
      - billing
      - deletion
      - password
    routing: support

priority:
  critical:
    criteria: 'affecting >10% users or security issue'
    action: immediate escalation

  high:
    criteria: 'blocking core functionality'
    action: next sprint

  medium:
    criteria: 'degraded experience'
    action: backlog prioritization

  low:
    criteria: 'nice to have'
    action: backlog for consideration

Feature Request Voting#

Track and prioritize feature requests:

typescript
interface FeatureRequest {
  id: string;
  title: string;
  description: string;
  category: string;
  requestCount: number;
  firstRequested: Date;
  lastRequested: Date;
  sources: string[]; // app, review, social, email
  status:
    | 'new'
    | 'under_review'
    | 'planned'
    | 'in_progress'
    | 'shipped'
    | 'declined';
  productNotes?: string;
}

Reporting and Analytics#

Weekly Feedback Report#

Audience: Product, Engineering, Leadership

Contents:

markdown
# Weekly Feedback Report: [Date Range]

## Summary

- Total feedback received: [X]
- By channel: App [X], Email [X], Reviews [X], Social [X]
- Sentiment: Positive [X%], Neutral [X%], Negative [X%]

## Ratings

- iOS App Store: [X.X] ⭐ ([+/-X.X] from last week)
- Google Play: [X.X] ⭐ ([+/-X.X] from last week)

## Top Issues

1. [Issue] - [X] reports
2. [Issue] - [X] reports
3. [Issue] - [X] reports

## Top Feature Requests

1. [Feature] - [X] requests
2. [Feature] - [X] requests
3. [Feature] - [X] requests

## Notable Feedback

- "[Quote]" - [Source]
- "[Quote]" - [Source]

## Action Items

- [ ] [Item] - Owner: [Name]
- [ ] [Item] - Owner: [Name]

Metrics Dashboard#

Metric Target Current
Average Review Rating > 4.5 [X.X]
Review Response Rate > 90% [X%]
Support Ticket Resolution < 24h [Xh]
NPS Score > 50 [X]
Feedback Volume (weekly) Baseline [X]
Feature Request Completion > 20%/Q [X%]

Feedback Database#

Store all feedback for analysis:

sql
CREATE TABLE feedback (
  id UUID PRIMARY KEY,
  source VARCHAR(50),  -- app, email, review, social
  channel VARCHAR(50), -- ios_review, android_review, etc.
  category VARCHAR(50),
  sentiment VARCHAR(20), -- positive, neutral, negative
  priority VARCHAR(20),
  user_id UUID REFERENCES users(id),
  content TEXT,
  tags TEXT[],
  created_at TIMESTAMP,
  resolved_at TIMESTAMP,
  resolution TEXT,
  metadata JSONB
);

-- Index for analytics
CREATE INDEX idx_feedback_source_date ON feedback(source, created_at);
CREATE INDEX idx_feedback_category ON feedback(category);
CREATE INDEX idx_feedback_sentiment ON feedback(sentiment);

Quarterly Feedback Review#

Process:

  1. Aggregate all feedback data
  2. Identify trends and patterns
  3. Compare to previous quarter
  4. Present findings to leadership
  5. Prioritize roadmap based on feedback
  6. Communicate back to users (changelog, announcements)

Quick Reference#

Contact Points#

Channel Address/Link
Support Email support@tara.app
Feedback Email feedback@tara.app
Security Email security@tara.app
Press Email press@tara.app
Twitter twitter.com/tara_app
Instagram instagram.com/tara.meditation
Discord discord.gg/tara-meditation

Response Templates Location#

All response templates are maintained in: /docs/templates/support/

Escalation Path#

text
User Feedback
     │
     ├── Support Issue → Support Team → Support Lead
     │
     ├── Bug Report → Engineering → Engineering Lead
     │
     ├── Feature Request → Product → Product Lead
     │
     └── Complaint → Support Manager → Director

Last Updated: January 2026

For questions about feedback channels, contact support@tara.app