App Store / Google Play · 清单验收 · 不承诺过审Telegram @hagee66

上架通

GOEE LISTING LEDGER

№ ENgoee.cc
账号归你 · 邀请协作


2026-02-13

Listing agency handoff: scope, access, acceptance, comms

Before hiring listing help, spell out platform scope, who owns materials, console access, no approval guarantee, acceptance checklist, and Telegram workflow. Telegram @hagee66.

This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66

Before hiring a listing agency or consultant, a single “please ship on Apple” message almost always leads to fights: who makes screenshots, who fixes rejections, whether passwords are shared, who guarantees approval, who tests IAP. A handoff checklist puts scope, ownership, access limits, acceptance criteria, and channels on one page—signed or email-confirmed—before anyone touches App Store Connect or Play Console.

Goee (goee.cc) starts external work from this checklist, with first-time listing roadmap and precheck scorecard. No approval guarantee; outcomes are decided by the platforms. Quotes and progress: Telegram @hagee66.

What this guide solves

  • Client assumes “agency = guaranteed pass,” demands refund or fake appeals after rejection.
  • Consultant holds Admin password; client loses control of certs and payouts.
  • Scope silent on Google; mid-project upsell.
  • Test accounts and privacy URLs found last-minute; review cycles idle.
  • Rejection in client inbox, agency blind—or agency changes builds without client knowing.
  • Appeals, metadata, compliance decisions with no named approver.

Who should read

Party Use
App owner (client) Self-check materials and access before hiring
Goee or any advisor Shared acceptance language
In-house listing lead Align with outsourcing
Legal Access and data terms

Core practice

1. Scope first

List explicitly:

  • Platforms: iOS / Android / both.
  • Version: first ship / update / metadata-only / rejection fix only.
  • Excludes: review farming, competitor keyword stuffing, hidden features, entity lending, guaranteed approval (do not put in contract).
  • Languages and countries: launch distribution—see localization ASO.

Scope changes need written addendum—avoid verbal “while you’re at it, fix paywall.”

2. Materials responsibility matrix

Material Default owner Guide
Icon, screenshots, description Client drafts; agency may advise Screenshot specs, Apple materials
Privacy policy URL Client legal Privacy policy
Nutrition label / Data Safety Client + agency together Privacy labels
Test account and notes Client data; agency formats Login notes
Binary Client engineering Crash precheck
IAP setup Client product + finance IAP notes

3. Least privilege

  • Apple: prefer App Manager—no Apple ID password.
  • Google: Play Console user invite, role tiers.
  • Signing: certificate handoff—agency does not hold private keys.
  • Client keeps Account Holder / owner revoke rights.

4. Comms and archive

  • One project thread; rejection full text within 48 hours.
  • Major decisions (remove features, change business model) need client written OK.
  • Folder naming per rejection fix.

5. Acceptance

Joint precheck scorecard before submit. Acceptance ≠ approval—it means materials per agreement are complete and paths self-tested.

After go-live, agency delivers: store links, version numbers, submit-time screenshots, note copies, known limitations.

6. Fees and timing

  • Split service fee from Apple/Google annual fees and rush labor.
  • Queue per review timeline—no promised days.
  • Round two after rejection: contract states N fixes included or per-incident billing.

7. Red lines (Goee will not do)

No help with hidden features, deceiving review, sensitive permissions by default (SMS/call log), clone/spam batches (clone policy). Client insists → engagement ends.

8. Response levels (contract attachment)

Event Suggested response Primary owner
Rejection arrives Archive within 48h Client forwards + agency ACK
Login path fails Client eng fixes account/build first Client; agency can retest
Metadata Client design/ops updates art Client; agency checks consistency
Declarations Joint privacy/forms Both
Client wants appeal Appeal decision table first Client sign-off

No “24-hour approval” KPIs. Queue is not controllable—see review timeline.

9. Knowledge transfer and exit

At end: final links, version, note copies, role screenshots, open items. Client removes agency users or downgrades—ASC roles, Play users. Avoid agencies editing metadata after project end.

Before first submit, joint read of precheck scorecard; sub-perfect rows name who fixes by when. Open items go on handoff as “known risk,” not “agency should have known.”

Copy-paste templates

[Listing handoff v1]
Project:
Client entity:
Agency:
Platform + version scope:
Rejection fixes included: 0 / N / billed separately
Exclusions (list):
Client POC / agency POC:
Channel: Telegram @… / email …
Apple Connect role (planned): no password / role name
Play Console role (planned):
Privacy policy URL (client confirms live):
Test account delivery (no plaintext passwords in public groups):
IAP involved: Y / N
Target submit date (not approval date):
Precheck meeting:
Acceptance: scorecard / materials matrix / note paths
Fees and invoice:
Client sign / date:
Agency sign / date:

Rejection sync message

[Rejection sync]
Platform:
Build:
Full letter (attachment)
Agency can log into Console: Y / N
Client decision deadline:

Common mistakes

  1. Password custody for a discount.
  2. Verbal “guaranteed pass.”
  3. Agency cannot change builds but takes payment-metadata rejections.
  4. Dual-platform handoff covers one side only.
  5. Appeal filed without client OK.
  6. Test account on CEO’s phone—cannot re-login after review.
  7. Ignore China team outbound gaps—all-Chinese materials.

FAQ

Can agency click Submit?
With App Manager (or equivalent) in scope—yes; client should still know build number.

Can agency receive IAP revenue?
No—payouts stay under client agreement.

Metadata-only engagement?
Yes—client still owns data accuracy.

Who pays for rejection fixes?
Per contract; product-debt rejections usually client engineering.

Ongoing Goee partnership?
Renew handoff per version—no need to renegotiate verbally.

Next steps

  • Both sides fill handoff v1; run precheck meeting.
  • Milestones per first-time listing roadmap.
  • Configure ASC / Play roles—no passwords.
  • Quote and schedule: Telegram @hagee66.

Related reading

Back to guide library · Telegram @hagee66