Choose the Invocation Name for a Custom Skill

If the invocation name is "توقعات الابراج اليومية", users can say:

Users say a skill's invocation name to begin an interaction with a particular custom skill. For example, if the invocation name is "Dagelijkse Horoscoop", users can say:

You can change your invocation name at any time while developing a skill. You cannot change the invocation name after a skill is certified and published.

Note that the invocation name is only needed for custom skills. If you are using a pre-built model, users do not need to use an invocation name for the skill. For more about the different types of skills you can create, see About Voice Interaction Models.

If the invocation name is "signe astrologique", users can say:

If the invocation name is "Tageshoroskop", users can say:

If the invocation name is "दैनिक राशिफल", users can say:

Use Latin script for English words and Devanagari script for Hindi words in your invocation name. For example:

If the invocation name is "Oroscopo del Giorno", users can say:

If the invocation name is "十二星座占い", users can say:

If the invocation name is "Horóspoco Diário", users can say:

If the invocation name is "Horóscopo Diario", users can say:

There are two ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):

   • "اليكسا، ابحثي في توقعات الابراج اليومية عن برج الجوزاء"
   • "اليكسا، من فضلك أبغى أسأل توقعات الابراج اليومية عن برج الثور"

2. Invoking the skill without a particular request, using a defined phrase such as "open" or "start". For example (this is not a complete list):

   • "اليكسا، افتحي توقعات الابراج اليومية"
   • "اليكسا، روحي إلى توقعات الابراج اليومية"
   • "اليكسا، وديني حق توقعات الابراج اليومية"

For a complete list of all launch phrases, see Understand How Users Invoke Custom Skills.

There are three ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all three of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):
   • "Alexa, vraag Dagelijkse Horoscoop om Tweelingen"
   • "Alexa, Talk to Dagelijkse Horoscoop en geef me de horoscoop voor Stier"
   • "Alexa, geef me de Stieren Horoscoop van Dagelijkse Horoscoop"
2. Invoking the skill without a particular request, using a defined phrase such as "open" or "start". For example (this is not a complete list):
   • "Alexa, open Dagelijkse Horoscoop"
   • "Alexa, start Dagelijkse Horoscoop"
   • "Alexa, vraag Dagelijkse Horoscoop"
3. Invoking the skill using just the invocation name and nothing else: "Alexa, Dagelijkse Horoscoop".

For a complete list of all launch phrases, see Understand How Users Invoke Custom Skills.

There are three ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all three of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):
   • "Alexa, ouvre signe astrologique pour verseaux"
   • "Alexa, lance signe astrologique et donne-moi l'horoscope des verseaux"
   • "Alexa, demande à signe astrologique quel est l'horoscope des verseaux"
   • "Alexa, dis à signe astrologique de me donner l'horoscope verseaux"
   • "Alexa, demandez à signe astrologique si je peux avoir l'horoscope verseaux"
2. Invoking the skill without a particular request, using a defined phrase such as "ouvre" or "commence". For example (this is not a complete list):
   • "Alexa, ouvre signe astrologique"
   • "Alexa, lance signe astrologique"
   • "Alexa, démarre signe astrologique"
3. Invoking the skill using just the invocation name and nothing else: "Alexa, signe astrologique".

For a complete list of all launch phrases, see Understand How Users Invoke Custom Skills.

There are three ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all three of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):

   • "Alexa, frage Tageshoroskop nach Fische"
   • "Alexa, sprich mit Tageshoroskop und öffne mein Horoskop für Fische"
   • "Alexa, gib mir das Fischhoroskop vom Tageshoroskop"
2. Invoking the skill without a particular request, using a defined phrase such as "open" or "start". For example (this is not a complete list):
   • "Alexa, öffne Tageshoroskop"
   • "Alexa, starte Tageshoroskop"
   • "Alexa, frage Tageshoroskop"
3. Invoking the skill using just the invocation name and nothing else: "Alexa, Tageshoroskop".

For a complete list of all launch phrases, see Understand How Users Invoke Custom Skills.

There are two ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all three of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):
   • "Alexa, दैनिक राशिफल से पूछो के Gemini राशि का दिन कैसा रहेगा"
   • "Alexa, दैनिक राशिफल शुरू करो और मुझे मिथुन राशि का राशिफल बताओ"
   • "Alexa, दैनिक राशिफल इस्तेमाल करो और मुझे वृषभ राशि का horoscope दें"
2. Invoking the skill without a particular request, using a defined phrase such as "open" or "start". For example (this is not a complete list):
   • "Alexa, मज़ेदार jokes खोलो"

   • "Alexa, मज़ेदार jokes open करो"

   • "Alexa, मज़ेदार jokes शुरू करो"

For a complete list of all launch phrases, see Understand How Users Invoke Custom Skills.

There are three ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all three of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):
   • "Alexa, domanda a Oroscopo del Giorno l'oroscopo dei Gemelli"
   • "Alexa, lancia Oroscopo del Giorno e dimmi l'oroscopo del Toro"
   • "Alexa, avvia Oroscopo del Giorno e dimmi l'oroscopo dei Pesci"
2. Invoking the skill without a particular request, using a defined phrase such as "open" or "start". For example (this is not a complete list):
   • "Alexa, apri Oroscopo del Giorno"
   • "Alexa, lancia Oroscopo del Giorno"
   • "Alexa, avvia Oroscopo del Giorno"
3. Invoking the skill using just the invocation name and nothing else: "Alexa, Oroscopo del Giorno"

For a complete list of all launch phrases, see Understand How Users Invoke Custom Skills.

There are three ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all three of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):
   • "アレクサ、十二星座占いに双子座の運勢を聞いて"
   • "アレクサ、十二星座占いを開いて牡牛座の運勢をチェックして"
   • "アレクサ、十二星座占いを使って牡牛座の運勢を教えて"
2. Invoking the skill without a particular request, using a defined phrase such as "を開いて" or "をスタートして". For example (this is not a complete list):
   • "アレクサ、十二星座占いを開いて"
   • "アレクサ、十二星座占いをスタートして"
   • "アレクサ、十二星座占いを実行して"
3. Invoking the skill using just the invocation name and nothing else: "アレクサ、十二星座占い".

For a complete list of all launch phrases, see Understand How Users Invoke Custom Skills.

There are three ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all three of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):
   • “Alexa, peça ao Horóscopo Diário pelo horóscopo de gêmeos”
   • "Alexa, inicia Horóscopo Diário e me dê o horóscopo de touro"
2. Invoking the skill without a particular request, using a defined phrase such as "abre", or "abrir", or "inicie o". For example (this is not a complete list):
   • "Alexa, abre Horóscopo Diário"
   • "Alexa, inicie o Horóscopo Diário"
   • "Alexa, abre o Horóscopo Diário"
   • "Alexa, abrir Horóscopo Diário"
3. Invoking the skill using just the invocation name and nothing else: "Alexa, Horóscopo Diário".

For a complete list of all launch phrases, see Understand How Users Invoke Custom Skills.

There are three ways in which users may say your invocation name to start using your custom skill. A good invocation name works well in all three of these contexts:

1. Invoking the skill with a particular request. There are several different ways users can combine your invocation name with their specific request. For example (this is not a complete list):
   • "Alexa, pregúntale a Horóscopos Diarios sobre Géminis"
   • "Alexa, dile a Horóscopos Diarios que me dé el horóscopo de Tauro"
   • "Alexa, abre Horóscopos Diarios y dame mi horóscopo de Tauro"
2. Invoking the skill without a particular request, using a defined phrase such as "abre" or "empieza". For example (this is not a complete list):
   • "Alexa, abre Horóscopos Diarios"
   • "Alexa, empieza Horóscopos Diarios"
   • "Alexa, lanza Horóscopos Diarios"
3. Invoking the skill using just the invocation name and nothing else: "Alexa, Horóscopos Diarios".

For a list of other supported launch phrases, see Understand How Users Invoke Custom Skills. Please note that this list is a representative sample of our supported phrasing.

An invocation name must meet the following requirements:

1. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

2. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words. In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it.

   For more details about intellectual property policies, see Policy Requirements.

3. Invocation names that include names of people or places (for example, "فاطمة" ,"جدة") are not allowed, unless they contain other words (for example, "برج فاطمة" ,"اضواء جدة" ,"سوق حمادة").

4. Two-word invocation names are not allowed if one of the words is a definite article ("ال") or preposition ("ل" ,"الى" ,"حق" ,"عن" ,"فوق" ,"ب" ,"في" ,"مع"). For example, "دراجة" ,"اسبريسو" ,"للضحك" ,"للتسلية".

5. The invocation name must not contain any of the Alexa skill launch phrases and connecting words.
   • Launch phrases include "وديني حق" ,"شغلي" ,"روحي إلى" ,"تقدري تشغلي" ,"وديني ال" ,"أبدأ" and "افتحي"
   • Connecting words include "من" ,"في" ,"عن". See Understand How Users Invoke Custom Skills to learn more about launch phrases and connecting words.

6. The invocation name must not contain the wake words "اليكسا،" "امازون،" "ايكو،" or the words "skill" or "تطبيق".

7. In the Arabic language, different case letters, possessive apostrophes, or periods used for abbreviations do not exist. Words should be written in Arabic when possible, with loan words written in Latin script (i.e. English) only when it cannot be represented in Arabic. Additionally, the words must be spelled out including numbers, for example, "عشرين". The name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words.

8. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "weather" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.

9. The invocation name must be written in each language you choose to support. For example, the German version of your skill must have an invocation name written in German. If your skill is published in a non-English marketplace, the invocation name may contain English words if these words are commonly used (for example, if proper nouns, like names and places, are used). In those cases, use the English spelling of those words. In cases where spelling differs between the local language and English, use the spelling of the local language (example: use "radioplayer" in a German skill–not "radio player").

10. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

An invocation name must meet the following requirements:

1. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

2. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words. In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it.

   For more details about intellectual property policies, see Policy Requirements.

3. Invocation names that include names of people or places (for example, "Dirk", "Amsterdam") are not allowed, unless they contain other words (for example, "Dirk's horoscoop," "Amsterdam tour," "Monique's market").

4. Two-word invocation names are not allowed if one of the words is a definite article ("de"), indefinite article ("een") or preposition ("voor", "naar", "van", "over", "op", "bij", "vanaf", "met"). For example, "een fiets", "een espresso", "naar Amsterdam", "voor plezier".

5. The invocation name must not contain any of the Alexa skill launch phrases and connecting words.
   • Launch phrases include "voer … uit," "start," "speel," "hervat," "gebruik," "lanceer," "vraag," "open," "vertel," "laad," "begin," and "activeer."
   • Connecting words include "naar," "van," "in," "met," "over," "voor," "dat," "bij," "als," "en," "of". See Understand How Users Invoke Custom Skills to learn more about launch phrases and connecting words.

6. The invocation name must not contain the wake words "Alexa," "Amazon," "Echo," or the words "skill" or "app".

7. The invocation name must contain only lower-case alphabetic characters, spaces between words, and possessive apostrophes (for example, "jan's science feitjes"). Other characters like numbers must be spelled out (for example, "honderd en een"). The name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words.

8. Periods are also permissible in invocation names containing acronyms or abbreviations that are pronounced as a series of individual letters, as in NOS, where the letters should be all lowercase and separated by periods and spaces (for example, “n. o. s.”). However, if the abbreviation is pronounced as a word, as in “NASA”, then it should be all lowercase but not contain periods or spaces (for example, “nasa”).

9. The invocation name cannot spell out phonemes. For example, a skill titled "AWS Feiten" would need "AWS" represented as "a. w. s. " and NOT "aa wee es"

10. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "weer" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.

11. The invocation name must be written in each language you choose to support. For example, the Dutch version of your skill must have an invocation name written in Dutch. If your skill is published in a non-English marketplace, the invocation name may contain English words if these words are commonly used (for example, if proper nouns, like names and places, are used). In those cases, use the English spelling of those words. In cases where spelling differs between the local language and English, use the spelling of the local language.

12. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

An invocation name must meet the following requirements:

1. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

2. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words. In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it.

   For more details about intellectual property policies, see Policy Requirements.

3. Invocation names that include names of people or places (for example, "paris", "camille") are not allowed, unless they contain other words (for example, "paris en vélo", "l' horoscope de camille").

4. Two-word invocation names are not allowed if one of the words is a definite article ("le", "la", "les"), indefinite article ("un", "une", "des") or preposition ("pour", "de", "sur", "avec", etc.). For example, "un vélo", "le café", "pour moi", "de paris".

5. The invocation name must not contain any of the Alexa skill launch phrases.
   • Launch phrases include "démarre," "joue," "commence," "utilise," "lance," "demande," "ouvre," "dis," "recommence," “mets,” and "active." See Understand How Users Invoke Custom Skills to learn more about launch phrases.

6. The invocation name must not contain the wake words "Alexa," "Amazon," "Echo," or the words "skill", "app", “appli” or “application".

7. The invocation name must contain only lower-case alphabetic characters (including accents whenever necessary), spaces between words, and any required apostrophes (for example, "bruits d' animaux"). Note that there should be a space after all apostrophes (eg: d’ animaux, l’ avion). Other characters like numbers must be spelled out (for example, "vingt et un"). Accents should be included on letters where appropriate (for example, "idées de travails", not "idees de travails"). The name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words.

8. Periods are also permissible in invocation names containing abbreviations or acronyms that are pronounced as a series of individual letters, as in “NRJ”, where the letters should be all lowercase and separated by periods and spaces (for example, “n. r. j.”). However, if the abbreviation is pronounced as a word, as in “UNESCO”, then it should be all lowercase but not contain periods or spaces (for example, “unesco”).

9. The invocation name cannot spell out phonemes. For example, a skill titled "NRJ Musique" would need "NRJ" represented as "n. r. j." and NOT "enne erre ji"

10. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "météo" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.

11. The invocation name should be written in each language you choose to support. For example, the French version of your skill must have an invocation name written in French. If your skill is published in a marketplace that is not the US, the invocation name may contain English (US) words if those words are commonly used in that marketplace (for example, if proper nouns, like names and places, are used). In those cases, use the English (US) spelling of those words. Avoid use of English (US) words when your skill invocation name matches one of the following criteria:
    • Spelling differs between the local language and English (US) words
    • English (US) words resulting in overlap with existing local words or common spelling (for example, in French, 'my router,' will be more frequently recognized as 'my routeur' because of the way the English word is pronounced)
12. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

An invocation name must meet the following requirements:

1. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

2. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words. In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it. The decomposition of German compounds into several components should be avoided, e.g. "radioplayer", NOT "radio player". In the case of a compound noun, the use of prepositions is not allowed, e.g. "zuschlag", "fürsprecher".

   For more details about intellectual property policies, see Policy Requirements.

3. Invocation names that include names of people or places (for example, "Moritz", "Lukas", "Bremen") are not allowed, unless they contain other words in addition to the name (for example, "Annikas Horoskop", "Bremerhaven Stadtführer").

4. Two-word invocation names are not allowed if one of the words is a definite article ("der", "die", "das"), indefinite article ("ein", "eine") or preposition ("an", "auf", "für", "über"). For example, "ein Fenster", "das Bild", "für Elise", "aus Spaß". If the invocation name has more than two words, the above-mentioned words can be used.

5. The invocation name must not contain any of the Alexa skill launch phrases and connecting words. Launch phrase examples include "aktiviere", "beginne", "frage", "lade", "öffne", "sage", "spiele" and "starte". Connecting word examples include "dass", "mit", "nach", "ob", "von", "und". Launch phrases and connecting words are also to be avoided as part of a compound noun, e.g. "videospiele", "fragesteller". Only derivatives of launch phrases are acceptable as invocation names, e.g. "jasager", "plattenspieler", "deutschland fragt". See Understand How Users Invoke Custom Skills for a complete list of skill launch phrases and connecting words.

6. The invocation name must not contain the wake words "Alexa", "Amazon", "Echo", or the words "skill" or "app".

7. The invocation name must contain only lower-case alphabetic characters, spaces between words, possessive apostrophes after letters "s" and "x" (for example, "Alex' Pizza"). Other characters like numbers must be spelled out. For example, "hundert zwei" (every number below twenty must be written in one word e.g. "neunzehn"). Umlauts (ä, ö, ü) and special characters like the sharp s (ß) should be included where appropriate (for example: bürgerbüro, not buergerbuero; fuß, not fuss).

   The name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words. For acronyms, the invocation name must contain single letters, each followed by a period and a space. The invocation name cannot spell out phonemes. For example, a skill titled "MFG Trivia" would need "MFG" represented as "m. f. g. " and NOT "em eff ge".

   If an invocation name is a compound word, it is usually also treated and written as such, e.g.:

   • Incorrect: wörter buch
   • Correct: wörterbuch

   This also applies to loan words:

   • Incorrect: englisch trainer
   • Correct: englischtrainer

   As well as nominalized verbs:

   • Incorrect: lieder raten
   • Correct: liederraten

   Exceptions are:

   a. foreign language compounds, these are treated according to the composition rules of the origin language:

   • Incorrect: manyland
   • Correct: many land

   b. Compounds containing numbers or abbreviations are separated from the rest of the word by a space:

   • Incorrect: stagezweizweidrei
   • Correct: stage zwei zwei drei
   • Incorrect: p.c.assistent
   • Correct: p. c. assistent
   • Incorrect: stabipaderborn
   • Correct: stabi paderborn

   c. Compounds containing a proper name:

   • Incorrect: borussiamönchengladbachquiz
   • Correct: borussia mönchengladbach quiz

   d. Compounds that are ambiguous by combination, e.g. "autosoundquiz", reading one: "auto so und quiz", reading two: "auto sound quiz":

   • Incorrect: autosoundquiz
   • Correct: auto sound quiz

   e. Compounds ending with any of the following keywords: album, feed, film, filme, gruppe, hits, joke, jokes, künstler, liste, music, musik, playlist, playliste, radio, radiosender, rezept, rezepte, scherz, scherze, schwitze, song, songs, timer, video, videos, witz, witze:

   • Incorrect: wortkünstler
   • Correct: wort künstler

   f. Compounds starting with any of the following keywords: hörspiele, hörspiel

8. Periods are also permissible in invocation names containing acronyms or abbreviations that are pronounced as a series of individual letters, as in “NDR”, where the letters should be all lowercase and separated by periods and spaces (for example, “n. d. r. ”, "a. b. c.", “k. f. z.”). However, if the abbreviation is pronounced as a word, as in “NASA”, then it should be all lowercase but not contain periods or spaces (for example, “nasa”).
9. The invocation name cannot spell out phonemes. For example, a skill titled "ZDF Neo" would need "ZDF" represented as "z. d. f." and NOT "zet de eff".
10. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "Wetter" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.
11. The invocation name should be written in each language you choose to support. For example, the German version of your skill must have an invocation name written in German. If your skill is published in a marketplace that is not the US, the invocation name may contain English (US) words if those words are commonly used in that marketplace (for example, if proper nouns, like names and places, are used). In those cases, use the English (US) spelling of those words. Avoid use of English (US) words in case your skill invocation name matches one of the following criteria:
    • Spelling differs between the local language and US English (for example, use “radioplayer” in a German skill – not “radio player”)
    • English (US) words resulting in overlap with existing local words or common spellings (for example, an invocation name containing 'cloth' will lead to poor recognition, since the pronunciation of 'th' often corresponds with 's' ('kloß'))
12. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

An invocation name must meet the following requirements:

1. Use Devanagari script for Hindi words and Latin script for English words. For example, "मज़ेदार jokes" or "दैनिक राशिफल".

2. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

3. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words. In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it.

   For more details about intellectual property policies, see Policy Requirements.

4. Invocation names that include names of people or places (for example, "रमेश", "मुंबई") are not allowed, unless they contain other words (for example, "रमेश का राशिफल").

5. Two-word invocation names are not allowed if one of the words is a definite article ("एक", "प्रति"), indefinite article ("कोई", "अनेक"), or preposition ("के लिए", "के पास", "तक", "की ओर", "की तरफ़", "के प्रति"). For example, "एक cycle", "एक हाथी", "मनोरंजन के लिए".

6. The invocation name must not contain any of the Alexa skill launch phrases and connecting words.
   • Launch phrases include "से पूछो," "शुरू करो," "प्रारंभ करो," "खोलो," "खेलो," "चालू करो," "open करो," and"इस्तेमाल करो"
   • Connecting words include "और," "कि," "अगर," "के," "की". See Understand How Users Invoke Custom Skills to learn more about launch phrases and connecting words.

7. The invocation name must not contain the wake words "Alexa," "Amazon," "Echo", "अलेक्सा", "एलेक्सा", "ऐलेक्सा", "ऐमेज़ोन", "ऐको", or the words "skill", "स्किल", "ऐप", or "app".

8. The invocation name must contain only lower-case alphabetic characters, spaces between words, possessive apostrophes, or periods used in abbreviations (for example, "a. b. c.") as long as the invocation name has English words. Periods are also permissible in invocation names containing acronyms that are pronounced as a series of individual letters, as in “DU”, where the letters should be all lowercase and separated by periods and spaces (for example, “d. u.”). However, if the abbreviation is pronounced as a word, as in “UNESCO”, then it should be all lowercase but not contain periods or spaces (for example, “unesco”). In Hindi language, different case letters, possessive apostrophes, or periods used for abbreviations do not exist. Other characters like numbers must be spelled out for Hindi as well as English for example, "इक्कीस". The name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words. For acronyms, the invocation name must contain single letters, each followed by a period and a space.

9. The invocation name cannot spell out phonemes. For example, a skill titled "DU" would need "DU" represented as "d. u." and NOT "dee you"

10. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "मौसम" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.

11. The invocation name should be written in each language you choose to support. For example, the Hindi version of your skill must have an invocation name written in Hindi. If your skill is published in a marketplace that is not the US, the invocation name may contain English (US) words if these words are commonly used in that marketplace (for example, if proper nouns, like names and places, are used). In those cases, use the English (US) spelling of those words. Avoid usage of English (US) words in case your skill invocation name matches one of the following criteria:

    • Spelling differs between the local language and English (US)
    • English (US) words resulting in overlap with existing local words or common spelling
12. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

An invocation name must meet the following requirements:

1. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

2. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words.In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it.

   For more details about intellectual property policies, see Policy Requirements.

3. Invocation names that include names of people or places (for example, "archimede", "firenze") are not allowed, unless they contain other words (for example, “il laboratorio di archimede”, "le biciclette di firenze").

4. Two-word invocation names are not allowed if one of the words is a definite article ("il", "la", "gli", "lo"), indefinite article ("uno", "una", "un"), preposition ("a", "per", "di"), prepositional article ("alla", "dei", "degli"), or possessive adjective ("mio", "mia", "tuo", "nostro"). For example, "una bicicletta", "un espresso", "di fare", "per me", “ai briganti”, “dell’ orto”, “mio forno”.

5. The invocation name must not contain any of the Alexa skill launch phrases.
   • Launch phrases include "avvia", "lancia", "apri", "apriamo", "puoi aprire", "mi apri", "comincia", "inizia", "usa", "gioca con", "accedi a", "chiedi", "domanda", "riproduci". See Understand How Users Invoke Custom Skills to learn more about launch phrases.

6. The invocation name must not contain the wake words "Alexa", "Amazon", "Echo", "Computer" or the words "skill" or "app".

7. The invocation name must contain only lower-case alphabetic characters, or spaces between words. Other characters like numbers must be spelled out (for example, "quattro passi"). Accents should be included on letters where appropriate (for example, "nomi cose città", not "nomi cose citta"). The name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words.

8. Periods are also permissible in invocation names containing acronyms that are pronounced as a series of individual letters, as in “ATM”, where the letters should be all lowercase and separated by periods and spaces (for example, “a. t. m.”). However, if the abbreviation is pronounced as a word, as in “UNESCO”, then it should be all lowercase but not contain periods or spaces (for example, “unesco”).

9. The invocation name cannot spell out phonemes. For example, a skill titled "ATM" would need "ATM" represented as "a. t. m." and NOT "a ti eme".

10. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "previsioni del tempo" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.

11. The invocation name should be written in each language you choose to support. For example, the Italian version of your skill must have an invocation name written in Italian. If your skill is published in a marketplace that is not the US, the invocation name may contain English (US) words if these words are commonly used in that marketplace (for example, if proper nouns, like names and places, are used). In those cases, use the English (US) spelling of those words. Avoid usage of English (US) words in case your skill invocation name matches one of the following criteria:

    • Spelling differs between the local language or variant and English (US)
    • English (US) words resulting in overlap with existing local words or common spelling (for example, an invocation name like 'musixmelody' will lead to poor recognition results since 'x' is not part of the local alphabet and only appears in loanwords in Italian)
12. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

An invocation name must meet the following requirements:

1. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

2. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words.In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it.

   For more details about intellectual property policies, see Policy Requirements.

3. Invocation names that include names of people or places (for example, "花子", "東京") are not allowed, unless they contain other words (for example, "モリースペシャル星占い," "神戸観光スポット," "花子手作りショップ").

4. In principle, the invocation name should not contain particles. You must use two or more nouns.

5. The invocation name must not contain any of the Alexa skill launch phrases and connecting words.
   • Launch phrases include "起動して" "使って" "開いて" "スタート" "スタートして" "始めて" "開始" "開始して" "実行して" "実行".
   • Connecting word examples include "で", "を使って", "使って", "に", "の". See Understand How Users Invoke Custom Skills to learn more about launch phrases and connecting words.

6. The invocation name must not contain the wake words "アレクサ", "アマゾン", "エコー", or the words "スキル" or "アプリ".

7. The invocation name must contain only Hiragana, Katakana, or Kanji. In the case of alphabetic acronyms, use consecutive lower-case letters (for example, "nasa"). Initialisms must follow rules 8 and 9 below. Other characters like numbers must be spelled out with Japanese characters (for example, "にじゅうご" or “二十五”). The name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words.

8. If the invocation name includes abbreviations, it must include single letters, each followed by a space (for example, "a b c ", "f y i ", "u f o ").

9. The invocation name cannot spell out phonemes. For example, a skill titled "AWS豆知識" would need "AWS" represented as "a w s " and NOT "エーダブリューエス."

10. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "天気" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.

11. The invocation name should be written in each language you choose to support. For example, the Japanese version of your skill must have an invocation name written in Japanese local orthography. English and other foreign language words should be localized when choosing an invocation name (for example, クックパッド or ルンバ).

12. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

An invocation name must meet the following requirements:

1. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

2. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words. In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it.

   For more details about intellectual property policies, see Policy Requirements.

3. Invocation names that include names of people or places (for example, "maria", "são paulo") are not allowed, unless they contain other words (for example, "horóscopo da maria").

4. Two-word invocation names are not allowed if one of the words is a definite article ("o", "a", "os", "as"), indefinite article ("um", "uma", "uns", "umas"), or preposition ("para", "por", "de", etc.). For example, "a bicicleta", "um espresso", "para entreter", "por diversão".

5. The invocation name must not contain any of the Alexa skill launch phrases.
   • Launch phrases include "começar", "iniciar", "jogar", "tocar", "usar", "pedir", "perguntar", "abrir", "dizer", "falar", "habilitar", and their conjugations. See Understand How Users Invoke Custom Skills to learn more about launch phrases.

6. The invocation name must not contain the wake words "Alexa," "Amazon," "Echo," or the words "skill" or "aplicativo".

7. The invocation name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words. It can contain only lower-case alphabetic characters (other characters such as numbers must be spelled out (for example, "vinte e um")) and spaces between words. Accents and tildes should be included on letters where appropriate (for example, "rádio globo", not "radio globo").

8. Periods are also permissible in invocation names containing acronyms that are pronounced as a series of individual letters, as in “UFRJ”, where the letters should be all lowercase and separated by periods and spaces (for example, “u. f. r. j.”). However, if the abbreviation is pronounced as a word, as in “UNESCO”, then it should be all lowercase but not contain periods or spaces (for example, “unesco”).

9. The invocation name cannot spell out phonemes. For example, a skill titled "UFRJ" would need "UFRJ" represented as "u. f. r. j." and NOT "u efe erre jota".

10. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "tempo" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.

11. The invocation name should be written in each language you choose to support. For example, the Portuguese version of your skill must have an invocation name written in Portuguese. If your skill is published in a marketplace that is not the US, the invocation name may contain English (US) words if these words are commonly used in that marketplace (for example, if proper nouns, like names and places, are used). In those cases, use the English (US) spelling of those words. Avoid usage of English (US) words in case your skill invocation name matches one of the following criteria:
    • Spelling differs between the local language and English (US)
    • English (US) words resulting in overlap with existing local words or common spelling
12. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

An invocation name must meet the following requirements:

1. The skill invocation name must not infringe upon the intellectual property rights of an entity or person. For more details about intellectual property policies, see Policy Requirements.

2. One-word invocation names are not allowed, unless:
   • The invocation name is unique to your brand/intellectual property with proof of ownership established through legitimate documentation, or
   • (German skills only) The invocation name is a compound of two or more words. In this case, the word must form an actual word in the skill's language to ensure that Alexa can recognize it.

   For more details about intellectual property policies, see Policy Requirements.

3. Invocation names that include names of people or places (for example, "marta", "santander") are not allowed, unless they contain other words (for example, "horóscopo de marta").

4. Two-word invocation names are not allowed if one of the words is a definite article ("el", "la", "los", "las"), indefinite article ("un", "una", "unos", "unas") or preposition ("para", "a", etc.). For example, "una bicicleta", "un cafecito", "a almorzar" and "para divertirse".

5. The invocation name must not contain any of the Alexa skill launch phrases.
   • Launch phrases include "correr", "comenzar", "iniciar", "poner", "jugar", "reproducir", "reanudar", "usar", "utilizar", "lanzar", "pedir", "preguntar", "abrir", "decir", "cargar", "empezar", "habilitar", and their conjugations. Understand How Users Invoke Custom Skills to learn more about launch phrases.

6. The invocation name must not contain the wake words "Alexa," "Amazon," "Echo," or the words "skill", "aplicación", or "app".

7. The invocation name must be easy to pronounce correctly and be phonetically distinct to avoid being misinterpreted as other similar sounding words. It can contain only lower-case alphabetic characters (other characters such as numbers must be spelled out (for example, "veintiocho") and spaces between words. Accents should be included on letters where appropriate (for example, "horóscopo diario", not "horoscopo diario").

8. Periods are also permissible in invocation names containing abbreviations or acronyms that are pronounced as a series of individual letters, as in “UCM”, where the letters should be all lowercase and separated by periods and spaces (for example, “u. c. m.”). However, if the abbreviation is pronounced as a word, as in “UNESCO”, then it should be all lowercase but not contain periods or spaces (for example, “unesco”).

9. The invocation name cannot spell out phonemes. For example, a skill titled "UCM" would need "UCM" represented as "u. c. m." and NOT "u ce eme".

10. The invocation name must not create confusion with existing Alexa features. If your skill invocations overlap with common Alexa commands, users may get confused by Alexa's response and not enable your skill. For example, if your invocation name is too similar to the built-in "tiempo" command, Alexa may sometimes respond with your skill and sometimes respond with the built-in weather feature, providing an inconsistent user experience.

11. The invocation name should be written in each language you choose to support. For example, the Spanish version of your skill must have an invocation name written in Spanish. If your skill is published in a marketplace that is not the US, the invocation name may contain English (US) words if these words are commonly used in that marketplace (for example, if proper nouns, like names and places, are used). In those cases, use the English (US) spelling of those words. Avoid usage of English (US) words in case your skill invocation name matches one of the following criteria:
    • Spelling differs between the local language and English (US)
    • English words resulting in overlap with existing local words or common spelling
12. The invocation name should be distinctive to ensure users can enable your skill. Invocation names that are too generic may be rejected during the skill certification process, or result in lower discoverability.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "ايكو", "اودبل"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "مواصلات الرياض", "تريفيا كرة" "القدم" ,"معلم الرياضيات" ,"الكرة السحرية" ,"احصائيات السكان" ,"نكات جحا".

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "شغلي", "افتحي" ,"روحي إلى" ,"اذهبي الى" ,"وديني حق") to allow customers to naturally invoke the skill.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "uber", "dominos"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "Kaarttrucs", "Fruitanalyse", "Praten op feestjes", "Reisroutes", "Grappen van Wouter", "Cadeau-ideeën.

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "lanceer", "vraag", "vertel", "laad", "begin") to allow customers to naturally invoke the skill.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "uber", "dominos"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "vélo paris", "faits sur la pétanque", "boule magique", "blague de thomas", "tuteur de math", "statistiques pour enfants".

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "lance", "demande à", "dis à", "ouvre") to allow customers to naturally invoke the skill.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "uber", "dominos"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "Kartentricks", "Obst Analyse", "Party Small-Talk", "Kreuzfahrtrouten", "Witze von Laura", "Geschenkideen".

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "starte", "öffne", "beginne", "lade", "frage") to allow customers to naturally invoke the skill.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "uber", "dominos"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "पश्चिमी Railway", "खाना खज़ाना", "कपिल शर्मा", "बच्चों के नाम".

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "से पूछो", "प्रारंभ करो", "खोलो", "शुरू करो", and "चालू करो") to allow customers to naturally invoke the skill.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "uber", "dominos"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "trasporto di roma", "cultura generale", "palla magica", "battuta del giorno", "citazioni celebri", "assistente di viaggio".

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "lancia", "domanda a, "chiedi a", "avvia", "apri") to allow customers to naturally invoke the skill.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "ウーバー", "ドミノピザ"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "算数チューター", "浅草グルメ", "はじめくんジョーク".

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "起動して", "開いて", "開始して") to allow customers to naturally invoke the skill.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "uber", "minha pizza"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "trânsito agora", "jogos mentais", "tutor de matemática", "informações do bebê", "as piadas do tim".

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "abrir a", "abrir o", "iniciar a", "iniciar o", "pedir à", "pedir ao", "pedir pra", "pedir pro", perguntar para a, perguntar para o, "falar com a", "falar com o", "dizer à", "dizer ao", "começar a", "começar o",) to allow customers to naturally invoke the skill.

The following recommendations are not required, but will provide users with a better experience:

1. The skill invocation name should be specific to the functionality of the skill, unless the invocation name is unique to your brand or intellectual property (for example, "uber", "telepizza"). One way to achieve relevance is to qualify the invocation name with something that describes the skill's functionality or something relevant to your company or developer name. For example, "transporte santander", "adivina adivina", "tutor de matemáticas", "ruleta de la fortuna", "medida del bebé", "chistes de juan".

2. The invocation name should also fit smoothly with at least one of the Alexa skill launch phrases (for example, "lanza", "pídele a", "dile a", "empieza") to allow customers to naturally invoke the skill.

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to Settings and then History).

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to Settings and then History).

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to Paramètres and then Historique).

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to Settings and then History).

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to Settings and then इतिहास).

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to Settings and then History).

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to 設定 and then 履歴).

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to Configurações and then Histórico).

Plan on spending some time testing your invocation name once you have an initial version of your service up and running. When testing with an Alexa-enabled device, you can see how Alexa interpreted your invocation name by reviewing the history in the Amazon Alexa App (in the app, navigate to Ajustes and then Historial).