How to Contact the Apple App Review Team (All Your Options)

Apple's App Review team is notoriously hard to reach through traditional customer service channels — there's no phone number, no support email, and no live chat. But there are multiple official pathways to communicate with them, and knowing which channel to use for which situation can make the difference between a quick resolution and weeks of delay.

Channel 1: The Resolution Center (Your Primary Tool)

The Resolution Center is built into App Store Connect and is the standard channel for any active review communication. Every rejection, whether for a new app or an update, can be responded to through the Resolution Center.

When to use it:

• Responding to a specific rejection notice
• Providing additional information the reviewer requested
• Clarifying how a feature works when a reviewer misunderstood it
• Asking for clarification on vague rejection reasons

How to access it:

1. Log into App Store Connect
2. Select your app, then go to the version in question
3. Find the rejection notice under App Review
4. Click Reply to Apple — this opens the Resolution Center for that specific submission

What makes a good Resolution Center message:

• Reference the specific guideline number cited in the rejection
• Keep the tone professional and factual — never accusatory
• Attach screenshots, screen recordings, or demo account credentials when relevant
• Be concise: two to four paragraphs is usually enough
• End with a specific question or request ("Could you clarify what specific element triggered this concern?")

What to avoid:

• Writing a wall of text that buries the key point
• Mentioning other apps or competitors' practices
• Threatening legal action (this routes your case to Apple's legal team and freezes review progress)
• Sending multiple follow-up messages in quick succession — wait at least 3 business days before following up

Channel 2: The App Review Board (Formal Escalation)

When you've been through the Resolution Center and still disagree with the outcome, the App Review Board is Apple's formal appeals process. This is a separate team that independently re-evaluates the rejection.

When to use it:

• You believe the reviewer made a factual error about your app's functionality
• Your Resolution Center appeal was denied without sufficient explanation
• The rejection seems inconsistent with similar apps already on the store
• You've received the same rejection after multiple rounds of Resolution Center communication

How to submit:

1. Visit developer.apple.com/contact/app-store/
2. Select Appeal a Rejection
3. Provide your app's Apple ID, the guideline cited, and a detailed written explanation

The App Review Board is not a rubber-stamp process — they conduct a genuine independent review. However, "I disagree with this guideline" is not a basis for appeal. The Board is looking for cases where the guideline was misapplied, not cases where a developer finds the guideline unreasonable.

For a full breakdown of the appeal process, see our guide on how to appeal an App Store rejection.

Channel 3: Pre-Submission Consultation

This channel is underutilized and can prevent rejections before they happen. If you're building an app with any of the following:

• Novel payment mechanisms or monetization models
• Sensitive APIs (location, health, camera in unusual ways)
• Content in borderline categories (medical, financial, children's apps)
• Features that might be confused with something violating the guidelines

...you can contact App Review proactively before submitting.

How to do it:

1. Go to developer.apple.com/contact/app-store/
2. Select Contact Us About App Store Publishing
3. Describe your app's functionality and ask for guidance

Apple doesn't guarantee a response on pre-submission inquiries, and the answer you receive isn't a binding approval. But it creates a paper trail and often results in useful guidance that prevents rejection.

Channel 4: Developer Technical Support (DTS)

Apple Developer Program membership includes two complimentary Developer Technical Support (DTS) incidents per year. These are intended for code-level questions, not review decisions — but they can be useful in specific scenarios:

• Your app was rejected for using an API in a way you believe is valid
• You need Apple's documentation on the expected behavior of a framework
• You want clarification on whether a specific technical implementation violates guidelines from a code perspective

DTS contacts are reached through developer.apple.com/support/technical/. They're engineers, not reviewers, and they can't override a review decision — but they can provide authoritative technical clarification that you can then cite in a Resolution Center response.

Channel 5: Apple Developer Forums

The Apple Developer Forums are a moderated peer community. Apple staff and Apple Developer Relations (DevRel) employees participate, though not on every thread.

When forums help:

• Understanding how other developers have handled similar guideline questions
• Getting community perspective on a rejection reason before writing your appeal
• Finding precedents ("here's how I resolved a 4.3 rejection") from other developers

When forums don't help:

• You need an official answer quickly
• You're dealing with an active rejection with a countdown
• Your situation involves confidential app details you can't share publicly

Apple DevRel staff will sometimes engage on forum threads about guideline interpretations, but they won't intervene directly in an active review case.

What to Say: Templates for Common Situations

Requesting clarification on a vague rejection:

"Thank you for reviewing [App Name]. The rejection references Guideline [X.X], but we're not clear on which specific element triggered this concern. Could you clarify what aspect of the app needs to be addressed? We want to make sure our fix targets the right issue."

Providing missing demo credentials:

"We apologize for the oversight. Below are test account credentials that allow full access to the app's features. [Username / Password]. The [feature name] requires [specific condition] — here are the steps to reproduce it: [steps]."

Contesting a factual error:

"We believe there may be a misunderstanding about how [feature] works. [Feature] does [actual behavior] — it does not [what the reviewer described]. We've attached a screen recording demonstrating this at [timestamp]. We believe this demonstrates compliance with Guideline [X.X] because [reason]."

Response Time Expectations

Channel	Typical Response Time
Resolution Center	1–3 business days
App Review Board	3–7 business days
Pre-submission inquiry	1–5 business days (not guaranteed)
Developer Technical Support	1–3 business days
Developer Forums	Varies (community-driven)

During high-volume periods — the six weeks before Christmas, major iOS release windows — all channels run slower. If your app has a time-sensitive launch, account for this in your timeline. For urgent cases, you can also request an expedited review.

Monitor Your App Store Reviews Automatically

Staying on top of every review is crucial for maintaining your rating and catching issues early. AppStoreReview monitors your app across 175+ countries, sends instant alerts for negative reviews, and lets you set keyword filters — so you never miss a critical review again.

Start monitoring for free →