Does the tester need an account to answer?

No. The email links back to the install page, where they answer once per reply.

Is the reply email marketing?

No. It is one transactional email with your reply and the link, tracking off, nothing else.

Can my AI coding assistant reply?

Yes, with the MCP tool reply_to_feedback, after a confirmation, by a Developer or above.

Who sees the star ratings?

Your team, on the build page. Testers see only their own rating.

AppForShare Create a free account

Feedback that turns into a conversation

Replies on Team. Star ratings on Pro and Team

A feedback report often needs one more answer: which screen, which account, does it still happen on the new build. Until now that meant copying the tester's email address and writing to them from your own mail, outside the report.

Now you reply from the report itself. The tester gets one email with your reply and a link back to the install page, where they can answer. The whole thread stays on the report.

Start free See plans

Example

Bug: checkout button does nothing

Tester, iPhone 15Tapping Pay does nothing
YouDoes it happen with Apple Pay too?
TesterOnly with a saved card
Build 2.4.0 (88) rating4.2 stars from 9 testers

Up to 20 messages per report, one email per reply.

Made for

Teams running a beta with outside testers or clients
QA leads who need a detail before they can reproduce a bug
Product owners who want a quick sense of how a build lands

What it ends

Follow up questions sent from personal mail, lost from the report
Testers who never hear whether their bug was fixed
No quick signal of how testers feel about a build

How it works

Step 1
Reply from the report
Press Reply to tester in the feedback inbox or on the build page card, or use appforshare feedback reply <id> --text "...", the CI API or the MCP tool reply_to_feedback.
Step 2
The tester gets one email
In the language of the install page they reported from (13 languages), with your reply and a link back to the install page. No account needed.
Step 3
They answer once
The tester can answer once per reply on the install page. You get an email without their words, plus a push notification, and an answer reopens a resolved report.

Replies, on Team

Replies work on reports where the tester left an email address; invited Team testers always have one. TestFlight reports and reports on deleted builds cannot be answered. Each report holds up to 20 messages, the report included, with up to 5 replies per report a day and 200 per workspace a day.

Every reply sends one transactional email, with tracking off and nothing else in it. Threads are deleted with the report, the build's feedback or the account.

Star ratings, on Pro and Team

The install page feedback card lets testers rate the build from 1 to 5 stars, under the same rules as the feedback form: the page must be unlocked and the link live, and private projects allow invited testers only. Each person rates a build once and can change their rating. The build page shows the average and how many testers rated; testers do not see the average.

Good to know

Replies are on Team only. Pro gets star ratings, not replies.
Only testers who left an email address can get a reply.
One answer per reply from the tester; it is not a chat.
No replies to TestFlight feedback: those testers are answered in TestFlight.

Questions

Does the tester need an account to answer?: No. The email links back to the install page, where they answer once per reply.
Is the reply email marketing?: No. It is one transactional email with your reply and the link, tracking off, nothing else.
Can my AI coding assistant reply?: Yes, with the MCP tool reply_to_feedback, after a confirmation, by a Developer or above.
Who sees the star ratings?: Your team, on the build page. Testers see only their own rating.