Skip to content

Settings and activity

2 results found

  1. 7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Caleb Gates commented  · 

    Calendars are hot but duplicating development efforts is not. We tried to train users to just not say our invocation name if they want to use the calendar but that only confuses them because they don't have the same grasp on the "levels" of Alexa ("Alexa Core", "In a skill", "Native features", "Custom Development Features"). If we could access their linked calendars within our skill we could avoid custom account linking, a separate account linking website for our skill, and loads of confusion on the part of our user. This would allow us to spend our time and money improving the voice eco system in other ways.

    Caleb Gates supported this idea  · 
  2. 29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Caleb Gates commented  · 

    This behavior should be default. Perhaps the idea was consistency for live skills helps users but that's not the case. It's even more confusing to our users when we cannot change the invocation name to account for collisions with other Alexa features.

    Caleb Gates supported this idea  ·