What exactly is a brand-voice profile?

A tuned voice, saved once as a named object at the org level, that any app in the org can adopt. Instead of voice living inside a single app, it lives above your apps as a reusable profile, so a whole portfolio can share one voice without you re-tuning each app by hand.

How do I apply a profile to my apps?

Open an app and assign the profile in one click. That app immediately drafts in the saved voice. Repeat across the portfolio and every app speaks with the same brand voice. There is no per-app re-tuning; the tuning was done once when you saved the profile.

If I tweak one app's voice later, does it change the saved profile?

No. Applying a profile copies it onto the app (copy-on-assign), so any later per-app adjustment stays local to that app. The saved profile, and every other app using it, is left untouched. The profile is a safe starting point you can branch from, not a shared document everyone edits.

Do my do-not-say rules still apply if I switch profiles?

Yes. Org-level do-not-say lines apply on top of whatever profile an app uses. Voice controls how you sound; do-not-say controls what you must never claim. They are separate layers, so changing an app's voice never drops the guardrails that keep replies safe.

How many profiles should I create?

As few as map to real audiences. Two or three profiles for genuinely different voices (say consumer, enterprise, and founder-personal) is the sweet spot. One profile per app defeats the purpose, which is to let many apps share a small set of well-tuned voices.

Which plan includes reusable brand-voice profiles?

The Indie tier and up. Profiles are stored at the org level, so every app in the org can adopt from the same library, and your org's do-not-say rules apply over any profile an app uses.

All posts

ProductJul 7, 2026 · 8 min

Give every app one consistent voice: reusable brand-voice profiles

Tune a voice once, save it as a named profile, and apply it to a whole portfolio in one click, so ten apps sound like one brand without re-tuning each by hand.

The Argus Team

Reply Argus

If you run more than one app, your replies have a consistency problem you probably cannot see. Each app was tuned on its own day, in its own mood, so one sounds warm and chatty, another sounds clipped and formal, and a third still has whatever default it started with. To a user who never installs two of your apps, none of that matters. To your brand, it is the difference between a company and a pile of unrelated listings. A voice is an asset, and an asset should be defined once and reused, not re-invented per app.

Reusable brand-voice profiles solve this. You tune a voice a single time, save it as a named profile at the org level, and apply it to any app in your portfolio in one click. Ten apps can share one voice without anyone re-tuning ten times, and when you improve the voice you improve it in one place.

Why keep the voice above the app instead of inside it?

Without profiles, voice lives per app. That is fine when you have one app: you tune it, you are done. It stops being fine the moment you have a portfolio, because now every app is a separate copy of the same intent, drifting apart over time. Change your mind about how formal you want to sound and you are editing that decision app by app, hoping you catch them all. The larger the portfolio, the more the small inconsistencies pile up, and the more likely it is that a stale app is still replying in a voice you abandoned months ago.

A profile turns the voice into a first-class, named thing that exists above any single app. 'Playful consumer', 'Enterprise-calm', 'Founder-personal': you define each once, and any app can adopt one. The org owns the library; the apps subscribe to it.

1
Tune a voice once
Dial in the tone, warmth, formality, and phrasing you want on one app until its drafts sound right. This is the same voice tuning you already do; you are just about to make it reusable instead of throwing it away.
2
Save it as a named profile
Promote that tuned voice into a named brand-voice profile at the org level. Give it a name that says what it is for. It now lives in your org's profile library, independent of the app you tuned it on, ready to be applied anywhere.
3
Apply it to any app in one click
Open any other app and assign the profile. That app immediately drafts in the saved voice. Do it across the whole portfolio and every app speaks with one consistent brand voice, no per-app re-tuning.
4
Tweak per app without breaking the source
Assigning a profile copies it onto the app (copy-on-assign), so a later per-app adjustment stays local to that app and never edits the saved profile. The source profile, and every other app using it, is undisturbed.

One tweak on one app never disturbs the rest

Copy-on-assign is the important detail. When you apply a profile, the app gets its own copy of the voice, not a live link back to the original. So you can nudge one app's phrasing for a local quirk without silently rewriting the shared profile or every other app that uses it. The profile is a starting point you can safely branch from, not a shared document that everyone edits at once.

What about the things a reply must never say?

Your org-level do-not-say lines still apply on top of whatever profile an app is using. Voice controls how you sound; do-not-say controls what you must never claim or promise. They are separate layers on purpose, so switching an app from a warm profile to a formal one never quietly drops the guardrails that keep your replies safe. Whatever the voice, the org's banned phrases and claims are enforced over it.

That separation is what makes profiles safe to hand around a portfolio. A profile carries the personality; the org carries the rules. You can experiment freely with tone across ten apps knowing the compliance floor does not move with the voice.

A few good profiles beat one per app

Keep your profile library small and named for intent, not for apps. Two or three profiles that map to real audiences (consumer, enterprise, personal) beat one profile per app, which is just the per-app problem with extra steps. The whole point is that many apps share a few voices; if every app has its own profile you have gained nothing.

Who can use it?

Reusable brand-voice profiles are available on the Indie tier and up. They live at the org level, so every app in the org can draw from the same library, and the do-not-say lines you set for the org apply over any profile an app adopts.

Frequently asked

What exactly is a brand-voice profile?: A tuned voice, saved once as a named object at the org level, that any app in the org can adopt. Instead of voice living inside a single app, it lives above your apps as a reusable profile, so a whole portfolio can share one voice without you re-tuning each app by hand.
How do I apply a profile to my apps?: Open an app and assign the profile in one click. That app immediately drafts in the saved voice. Repeat across the portfolio and every app speaks with the same brand voice. There is no per-app re-tuning; the tuning was done once when you saved the profile.
If I tweak one app's voice later, does it change the saved profile?: No. Applying a profile copies it onto the app (copy-on-assign), so any later per-app adjustment stays local to that app. The saved profile, and every other app using it, is left untouched. The profile is a safe starting point you can branch from, not a shared document everyone edits.
Do my do-not-say rules still apply if I switch profiles?: Yes. Org-level do-not-say lines apply on top of whatever profile an app uses. Voice controls how you sound; do-not-say controls what you must never claim. They are separate layers, so changing an app's voice never drops the guardrails that keep replies safe.
How many profiles should I create?: As few as map to real audiences. Two or three profiles for genuinely different voices (say consumer, enterprise, and founder-personal) is the sweet spot. One profile per app defeats the purpose, which is to let many apps share a small set of well-tuned voices.
Which plan includes reusable brand-voice profiles?: The Indie tier and up. Profiles are stored at the org level, so every app in the org can adopt from the same library, and your org's do-not-say rules apply over any profile an app uses.

Try it

Let Argus draft your next reply.

Watch it answer a real review in your voice. 10-day trial, no card to begin.

Start free

See the features or pricing.

Keep reading

Product7 min

Manage Your App Store Reviews From Claude: The 5-Minute MCP Setup

Connect one MCP server and run your App Store + Google Play review queue from a Claude chat: summarize complaints, draft grounded replies, queue for approval.

Product8 min

The MCP Server for App Reviews: Connect Your AI Agent to Your Store Reviews

An app reviews MCP server hands your live App Store and Google Play reviews to Claude, ChatGPT, or Cursor as callable tools. Here's what it exposes and how to wire it up.