There is no public phone number for the Apple App Store review team; you reach them through defined channels instead. Use the Resolution Center in App Store Connect to reply about a specific rejection or reviewer message, use Apple's Contact the App Review Team page for general questions or a review taking longer than expected, submit an appeal to the App Review Board when you believe a rejection was wrong, and use the expedited review request for a genuine, time-sensitive launch. Pick the channel that matches your situation.
Short answer
Apple does not offer a phone number for App Review; the channels are web-based. For a specific rejection, reply in the Resolution Center, where Apple generally responds within 24 hours. For general questions, a review taking longer than expected, an appeal, or an expedited request, use the Contact the App Review Team page linked from Apple's App Review page. Choose Resolution Center for an in-flight submission, the App Review Board to appeal a rejection you believe is wrong, and expedited review only for a real, time-sensitive event. Always include your app name, the build, and a specific question.
There is no phone number for App Review
The first thing to know is that calling is not an option; there is no App Review phone line, and searching for one leads nowhere useful. Apple handles App Review communication through App Store Connect and its developer contact pages, which is deliberate, because a written channel keeps a record of the exact submission, message, and guideline in question.
This is not a brush-off. The written channels are monitored, and the Resolution Center in particular tends to get a response within a day. What it means for you is that the fastest path is not to hunt for a number, but to use the right written channel with the right information, which is what actually moves your case.
The channels, and when to use each
There are a handful of channels, and using the right one for your situation is what gets a useful answer. The table below maps each channel to what it is for.
| Channel | Use it for | Where |
|---|---|---|
| Resolution Center | Replying to a reviewer about a specific rejection | App Store Connect |
| Contact the App Review Team | General questions, a review taking longer than expected | Apple developer contact page |
| App Review Board | Appealing a rejection you believe is wrong | Contact page, appeal option |
| Request Expedited Review | A genuine, time-sensitive event or fix | Contact page, expedite form |
| Apple Developer Support | Account, membership, and enrollment issues | Apple developer support page |
The single most common mistake is using a general contact form for something that belongs in the Resolution Center, or the reverse. If your question is about a specific submission that was rejected, the Resolution Center is the place; if it is a broader question, an appeal, or an expedite request, the Contact the App Review Team page is the place.
Resolution Center: replying about a specific submission
The Resolution Center, inside App Store Connect, is where you talk to the reviewer about a specific submission. When your app is Rejected or Metadata Rejected, the reviewer's message appears there, and you reply in the same thread. Apple says it generally responds to Resolution Center messages within 24 hours, which makes it the fastest channel for an in-flight review.
Use it to ask what specifically needs to change, to explain a feature the reviewer may have misunderstood, or to confirm you have made a requested change. Keep replies specific and tied to the guideline cited. This is a conversation about one submission, so stay on that submission rather than raising unrelated questions, which belong in the general contact channel.
Contact Us: general questions and a review taking too long
For anything that is not a reply on a specific rejection, use the Contact the App Review Team page, reachable from Apple's App Review page. This is where you ask general questions, request the status of a submission that is taking longer than expected, or raise a guideline question before you submit. It is the catch-all channel for App Review that is not tied to an open rejection thread.
The most common use is a review that has sat far longer than typical. Apple states that most apps are reviewed within 24 hours, so a submission stuck for several days is a reasonable reason to reach out through this page. Select the option that matches your situation, and describe it concretely so the team can locate your app and respond.
Appealing a rejection: the App Review Board
When your app is rejected and you genuinely believe the decision was wrong, you can appeal to the App Review Board. You do this through the Contact the App Review Team page by selecting the option to appeal an app rejection or removal, and Apple asks you to provide specific reasons why your app complies with the App Store Review Guidelines.
An effective appeal is specific and calm. Point to the exact guideline, explain why your app meets it, and address the reviewer's stated concern directly rather than arguing in general terms. Appeal when you have a real case that a decision was mistaken; if you actually need to change the app, it is usually faster to fix it and resubmit through the normal flow than to appeal.
Requesting an expedited review
If a genuine deadline is approaching, you can request an expedited review, which asks Apple to move your submission ahead in the queue. You request it through the Contact the App Review Team page, and Apple wants the specifics: the event, its date, and how your app is associated with it. It is intended for real, time-sensitive situations, such as an app tied to a scheduled event or a critical fix for a live issue.
Use it sparingly and honestly. Expedited review is a limited courtesy, and over-requesting it, or using it for routine launches, undermines it for the cases that genuinely need it. If your reason is strong and clearly explained, it is a legitimate tool; if it is just impatience, the normal queue is the right path.
What to include so you get a useful reply
Whichever channel you use, the quality of the reply depends on the information you provide. A vague message gets a slow or generic answer, while a specific one gets a specific response. The checklist below covers what to include.
| Item | Why it matters |
|---|---|
| App name and Apple ID | Lets the team find your app |
| The submission or build and date | Identifies the exact review |
| The guideline or message referenced | Ties to the reviewer's note |
| A clear, specific question | Gets a specific answer |
| Screenshots or supporting evidence | Backs up your case |
| A calm, factual tone | Speeds resolution |
The theme is specificity. Give Apple enough to find your exact app and submission, tie your question to the exact guideline or message, and ask something answerable. A calm, factual message with the right identifiers does more than a long or frustrated one.
What Apple will not do
Set expectations about the limits. Apple will not give you a phone call, will not guarantee a review time, and will not reverse a correct rejection because a deadline is tight. Support and App Review can clarify, re-examine, and expedite in genuine cases, but they cannot bend the guidelines or move every app to the front of the line.
Knowing this keeps you from spending energy on the wrong ask. If your app genuinely violates a guideline, the productive path is to fix it, not to appeal or escalate. If it does not, a specific Resolution Center reply or a well-argued appeal is the right move. Matching your request to what the channel can actually do is what gets results.
Reduce the need to contact review at all
The best contact with App Review is the one you never need. Many messages and appeals trace back to avoidable rejections, and a good share of those are security and privacy issues: an app requesting permissions it cannot justify, cleartext traffic where encryption is expected, or an embedded secret. Catching these before you submit removes the reason to contact review in the first place.
A scanner like PTKD.com analyzes your .ipa and returns findings ordered by severity and mapped to OWASP MASVS, so you can fix security and privacy issues before submission. To be clear about the boundary: PTKD cannot contact Apple for you, speed up a review, or file an appeal. It reduces the preventable rejections that create the need to reach out, which is the part of the process you control.
What to take away
- There is no phone number for App Review; use the written channels instead.
- Reply in the Resolution Center for a specific rejection, where Apple generally responds within 24 hours.
- Use the Contact the App Review Team page for general questions, a review taking too long, appeals, and expedite requests.
- Appeal to the App Review Board with specific reasons, and request expedited review only for a genuine, time-sensitive event.
- Scan each build with PTKD.com before submitting, so a preventable security issue does not create the need to contact review.
