# ASO Agency — Lesson 47: App ratings strategy: plan in-app review requests

Outcome: Coordinate review requests with product value and current platform rules.

App / store / market / locale:
Prepared by / date:
Product or listing version:

## Your ASO assignment

1. Draft a request-flow brief tied to a genuine value moment.

Your response:

2. List prohibited or misleading practices your process avoids.

Your response:

3. Define how critical themes reach product and support owners.

Your response:

## Scenario challenge

Redesign a flow that says “Enjoying the app? Yes: rate five stars. No: contact support.” Explain how your alternative invites honest feedback and offers support without filtering sentiment.

Your reasoning:

## Handover

### Trigger design

Describe the meaningful experience, timing and interruption considerations.

Your evidence and decision:

### Flow map

Show every branch, including support access and review-request behavior.

Your evidence and decision:

### Policy references

Link current platform guidance and record review of incentives and selective routing.

Your evidence and decision:

### Implementation record

Assign engineering ownership and verify supported API behavior without guaranteed display assumptions.

Your evidence and decision:

### Monitoring

Track user friction and rating context without overclaiming causation.

Your evidence and decision:

## Submission check

- [ ] The request follows a meaningful experience rather than coerces praise.
- [ ] Platform behavior and rules are verified with the implementation owner.
- [ ] Support access is not conditional on a positive rating.

## Next action
Owner:
Required evidence:
Due date:
Review decision:

www.asoagency.com