Explain an existing referral program without hiding the rules

Explain who may refer, who may be invited, the action that qualifies, what each person receives, when the benefit appears, relevant limits or exclusions, and where the reader can see the full terms. Show the current invite flow rather than implying that a share alone creates a reward.

Keep referral rewards separate from store ratings and reviews. Apple and Google Play prohibit attempts to manipulate ratings, reviews, or store placement, including incentivized reviews. A referral program can reward an eligible product action under its own rules; do not turn that reward into payment for a positive review or rating.

Have the program owner approve these fields before anyone drafts creative.

If a field varies by market or account, create separate approved variants. Do not compress incompatible terms into a footnote. Record the source and approval date so old scheduled posts can be found when the program changes.

1. 1

   Entry point

   Show where an eligible user opens the referral experience. Crop out private account data and retain enough interface context to make the path recognizable.

2. 2

   Offer summary

   Show the current benefit and qualification in the product's wording. If the screen omits an important limit, state it in the slide and link the terms.

3. 3

   Invite preview

   Show what the invited person receives before asking a user to share. Let the referrer understand the message and destination.

4. 4

   Invitee destination

   Show the signup, store, or landing-page state the invitee reaches. Do not substitute a generic app-store screenshot for a different destination.

5. 5

   Qualification and reward state

   Explain pending, qualified, delivered, expired, or reversed states using the actual program logic. AttentionClaw does not administer these states.

Fictional program: eligible existing users invite a new teammate; both receive one month of the Team add-on after the teammate starts a paid Team plan. Full terms and limits live at the fictional destination.

Replace every fictional term with the approved program fields. Do not borrow the reward, timing, or qualification from this example.

1. 1

   Announcement carousel

   1: “Planning work with a teammate?” 2: “Eligible existing users can send a Team invite from Settings.” 3: “Your teammate sees the plan and price before starting.” 4: “After the invited teammate starts an eligible paid Team plan, both accounts receive one month of the Team add-on.” 5: “Eligibility, limits, timing, and exclusions apply.” 6: “Open Referral in Settings or read the full terms.”

2. 2

   Workflow reminder

   1: “A natural time to invite: when the next project needs an owner.” 2: show the project member screen. 3: show the Referral entry point. 4: explain the qualifying paid-plan action. 5: link the current terms. The reminder begins with the collaboration use case rather than manufactured urgency.

3. 3

   Verified proof variant

   1: “What the invited teammate sees.” 2–4: current, privacy-safe screenshots of message, landing page, and plan choice. 5: “No reward is created until the qualifying action in the terms occurs.” 6: program destination. This proves the flow, not a performance outcome.

4. 4

   FAQ carousel

   1: “Before you invite a teammate...” 2: who may refer. 3: who qualifies as a new teammate. 4: the qualifying action. 5: reward timing. 6: limits and exclusions. 7: support path. 8: full terms. Every answer is copied from or reviewed against the source-of-truth sheet.

A user sharing an incentivized recommendation may create a material connection that needs disclosure under applicable rules. The FTC advises clear disclosure when an incentive could affect the weight or credibility of an endorsement. Give users plain disclosure guidance for the channels you ask them to use, and have the appropriate policy or legal owner review the program.

Do not describe rewards as cash when they are credits, say “free” without material conditions, claim unlimited availability when limits exist, or present a pending reward as earned. Do not use a testimonial unless the person approved the wording and the claim is accurate.

The referral platform or product backend should remain the source of truth for who referred whom, whether the invitee qualified, and whether a reward was delivered. Use social and web analytics only for the layer they observe. Google Analytics documents campaign parameters for identifying traffic from tagged URLs; app deep-link and referral attribution require the systems your team has implemented.

Create distinct creative identifiers for announcement, reminder, proof, and FAQ variants where your destination and analytics support them. Never infer delivered rewards from link clicks. Keep unattributed invitations and private shares in a separate bucket rather than assigning them to the nearest post.

After the program owner approves the terms sheet, screenshots, and destination, AttentionClaw can draft carousel copy and images, apply the app's brand style, and give the team variants to review and edit before publishing. It does not implement the referral system, determine eligibility, issue rewards, prevent fraud, or track campaign results.

Before publication, compare every generated statement with the source-of-truth sheet and live flow. Test the link on the intended device and account state. Archive the creative version with the terms version so the team can identify what must be corrected when the program changes.