Invocation and discovery checklist

App Name
Avoid words that have multiple pronunciations

This is needed so that both users and Google Assistant know how to pronounce your app name. For instance, it may not be a good idea to include the word "Envelope" in your app name, as users and Google Assistant will not know whether to say "en-vel-ope" or "ahn-vel-ope". Other examples include "tear", "bow", and "bass".

Make sure Google recognizes your app name
  • Use the microphone input in the developer console to speak your app name, rather than type it. Using our speech recognizer increases the chances that your app name will be correctly recognized. You should also try saying it several times to make sure it's consistently recognized accurately. Speech input is currently only available in the Chrome browser
  • Test your app name in the Actions Simulator with the microphone input. Check to see if the text output matches what is listed for your app name.
  • Test your action on voice-activated speakers. Preview your action and try to invoke it on a voice-activated speaker
  • Try testing with people of different genders and accents. You want to make sure that your app name will be recognized no matter who says it.
Choose easy but unique names

You want users to be able to effortlessly use your actions. If they have to struggle to say the name or if they can’t easily remember the name, then they are far less likely to keep using your actions.

Adhere to our app name policies

See the app naming policies for more information on guidelines and restrictions for app names.

If you need an app name for your business that violates one of our policies or if it's not recognized well by Google, contact support to receive an exception that we evaluate on a case-by-case basis.

Action Phrases
Specify action phrases specific to your app's capabilities

Action phrases can help the Assistant invoke your app more often and in more appropriate situations. Define action phrases that are specific to your app's capabilities. Action phrases that are too vague or general decrease the likelihood of the Assistant matching your app to user requests.

Design for the right use cases

DO Design your actions around specific tasks and real world use cases.

DON'T use general phrases that will prevent Assistant from triggering your app.

Provide a broad set of action phrases

Provide at least 10 or more variations for each action that helps guide users to your action.

Specify a clear verb and object

Your action phrases should be easy to remember and obvious verb and object pairs.

Assistant Directory
Use the Assistant Directory weblink

Promote your app using the Assistant Directory weblink. You can provide this link on your webiste and other marketing materials to drive users to your actions.

Describe your app's capabilities in your app description

Describe ways that your app can help users and promote your app’s utility, benefits, and best features with text and images.