Support email is part of the product. It is the only place some users will tell you the first job failed. If the address in App Store Connect goes to a black hole, you shipped a listing without a human. At Croncode we treat the inbox as a surface with an owner, a tone, and a rule for when a message becomes a build. This is not a call-center playbook.

Support email is a product surface when one inbox is owned, replies name the job, and repeats become tickets. A noreply address is a closed door.

What belongs in the App Store support field?

A mailbox the company owns, not a personal Gmail that will die with a contractor. A page that states hours and languages if you cannot be 24/7. A privacy path that is not the same thread as “how do I restore.” Deletion requests are a legal surface: data deletion in small apps.

Who owns the Apple org should own or appoint the mailbox. Account paper: who owns the App Store account. Istanbul hiring checks: what to check. Identity: Croncode LLC in Albuquerque, not croncodetech.com. Identity article.

How should a reply be written?

1. Restate the job they were trying to finish.
2. Say what you can do in this message: steps, restore, refund path, or a bug ID.
3. Say what you cannot do: change Apple billing, unlock a chapter that is not in the binary.
4. Give one next action, not five links.

Founder-led weeks use the same shape with a name. See founder-led support. Paywall confusion is common. Keep the sheet honest so mail is not your only disclosure: honest paywalls.

When does a message become engineering work?

Crash diligence: crash-free questions. Reviews are a second inbox. Read them on a cadence: reviews as a team.

Which products teach this the hard way?

A stylist app gets photo and combination questions. A decision app gets “did you store my story.” A narrative app gets spoiler and save questions. A transfer app gets time-window questions. Those jobs are YourStyle, Numira, Spylie, and Luviport. We do not invent ticket volumes.

Team who will see early mail: Goktug Unver, Yusufhan Sokur, Ozgur Ismet Ozkan. Catalog: what Croncode builds.

What mistakes make the inbox useless?

• A chatbot that cannot name the object: users escalate angrier.
• English-only replies to Turkish store users: localize the inbox, not only strings. onboarding localization.
• No overlap hour with Istanbul engineering: shipping: how we ship.
• Analytics that exist only to retarget complainers: analytics without surveillance.

Put the mailbox and the owner in the quote packet: what to send. Hire: hire the studio. Custom: custom software. Contact: contact us. Journal: /en/journel/.

How do you staff support in a lean studio?

One named human in the first cohort, a saved reply for restore and deletion, and a weekly tag review. Do not hire a vendor to hide the product. Do not let the designer be the only person who sees “the button is gone.” Resource split: small team, multiple products. Week-two product work still matters more than a prettier autoresponder: week two.

If you hand a codebase in, include mailbox credentials in the company vault, not in a chat screenshot. Handover: handover a codebase. Security questions before you sign: security questions.

Frequently asked questions

Is a contact form enough instead of email?

Apple still wants a support URL or email that works. A form is fine if a human reads it on a named schedule.

How fast should we reply?

Write a target you can keep, such as two business days in the overlap hour. A fake one-hour promise is worse than a honest two-day one.

Should we answer billing in the app?

Explain the product. Apple manages the subscription sheet. Tell users where to cancel in Settings. Do not pretend you can void a store charge from Slack.

Can the studio be the support desk forever?

Only if the contract says so. Default: the company that owns the listing owns the user. We can operate the inbox if invited.

What address should Croncode clients publish?

A domain they own. We will not put a personal engineer address on a client listing.