Reviews
Reply footer: support email and signature
Append a support address and a signature to every reply, with a different address per app
Most replies to unhappy reviewers end the same way: point them somewhere a human can actually help. The reply footer automates that, so the model does not have to remember and cannot get the address wrong.
What the footer adds
| Element | Description |
|---|---|
| Support email line | A sentence pointing the reviewer at your support address, using wording you control. |
| Signature | A sign-off such as the team or product name. |
Both are switched on independently in Settings → Replies, and a live preview shows exactly how a reply will end.
Customising the wording
The support line is a short template, up to 300 characters, containing a token that is replaced with the app’s support address:
Need a hand? Email us at {{email}} and
we'll sort it out.Per-app support addresses
Each connected app has its own support email and signature, set in the same panel and grouped by account. An agency replying for several clients gives each app the client’s own address, and every reply for that app points at the right inbox.
The panel shows an "n of m set up" count per account, so it is obvious which apps still have no address configured.
How it interacts with character limits
The footer is appended after the reply is generated, and the room it needs is reserved before the model writes. On Google Play, where the whole reply must fit in 350 characters, that means the AI writes a shorter body rather than the footer being cut off.
Adding or removing it on a draft
The composer has an Attach support email checkbox that overrides the default for one reply. Toggling it on text you have already drafted does not regenerate the reply from scratch — ReviewDesk rewrites just enough to add or remove the support sentence, leaving the rest of your wording intact.