Invocation and discovery checklist

Invocation Name
Avoid words that have multiple pronunciations

This is needed so that both users and the Google Assistant know how to pronounce your invocation name. For instance, it may not be a good idea to include the word "Envelope" in your invocation name, as users and the 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 invocation name
  • Test your invocation name in the Actions console's simulator with the microphone input. Check to see if the text output matches what is listed for your app name. Speech input is currently only available in the Chrome browser.
  • 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 invocation name will be recognized no matter who says it.
Choose easy but unique names

You want users to be able to effortlessly invoke your Action. 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 Action.

Adhere to our naming policies

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

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

Invocation Phrases
Design for your Action's use cases

DO design your invocation phrases around your Action's specific tasks and real world use cases.

DON'T use phrases that are too general or don't describe your app's purpose specifically.

Specify clear verb-object pairs

The most useful invocation phrases typically consist of a verb-object pair. These phrases are easy to remember and align well with most user queries.

Use entities with relevant synonyms

Entities are useful tools for invocation phrases since they can match multiple user inputs to a single phrase. Make sure all entities you add to invocation phrases only include synonyms that are relevant to the phrase(s) and your Action's use case.

Provide a broad set of quality invocation phrases

You should ensure your Actions can be invoked regardless of your user's choice of words. Try and provide at least 10 different invocation phrases for each Action under Build > Actions in the Actions console.

Review examples of good and bad invocation phrases

Invocation phrases are critical for your Action being discovered naturally via implicit invocation, so you should take the time to ensure they are designed well. Review our recommendations for writing useful invocation phrases to make sure you get this right.

Assistant Directory
Use Action links

Promote your Action by creating Action links and distributing them to users. Users who click your link on compatible devices will be taken directly to a conversation with your Action.

Use the Actions directory weblink

Promote your Action using the directory weblink. You can provide this link on your website and other marketing materials to drive users to your Action's directory page.

Write good descriptions

Make sure your Directory descriptions promote your Action’s utility, benefits, and best features with text and images.

If the Assistant recommends your Action to a user and they ask for more details, the Assistant will read your Action's description to the user. Make sure your description sounds good in this context to give a good first impression.