Digital Assistant and Mobile

Get Involved. Join the Conversation.

Topic

    Wouter Sligter
    how to transition to a different skillAnswered
    Topic posted January 3, 2019 by Wouter SligterGreen Ribbon: 100+ Points, tagged Bots, Conversational AI 
    86 Views, 5 Comments
    Title:
    how to transition to a different skill
    Content:

    use case: HR Digital Assistant with two (or more) access levels.

    Each access level (let's say 'employee' and 'manager') gets redirected to a 'skill' with content only available to this group.

    Since DAs can't perform actions I'd create an on-boarding skill that captures employee number from the user, check it against the db and sends user to either 'employee' skill or 'manager' skill.

    Please advise if you think this is best practice?

    If so, how do I transition from on-boarding skill to 'employee' or 'manager' skill?

    Best Comment

    Grant Ronald

    I assume you are someone going to get people to log in to determine if they are a manager or an employees - in which case you can simply have different flows - for example the system.intent for the manager might actions to "hireEmployee" and "fireEmployee" as well as "LogExpense" but for the employee you either

    a) only have LogExpense as an action on the intent

    b) have all the intents for the employee but the actually action for e.g. "fireEmployee" is an out put "sorry you don't have permissions to fire someone".

    Comment

     

    • Grant Ronald

      It depends - one of the advantages of the DA design is that from within a skill you could call another skill (e.g. whilst ordering a pizza you check your bank balance to see if you have enough money for a pizza).  That doesn't mean you can't have your architecture as two separate skills but from what you say it really sounds like the same skill but with different access levels/paths - in which case I'd keep it as the same skill.

       

      • Wouter Sligter

        Hi Grant, thanks for your answer. Would I be able to ensure 'employees' get limited access through the use of contexts? I want to be sure that they won't see any 'manager' content by typing utterances that correspond with manager intents. Or what do you reckon is the best way to go about setting this up?

    • Grant Ronald

      I assume you are someone going to get people to log in to determine if they are a manager or an employees - in which case you can simply have different flows - for example the system.intent for the manager might actions to "hireEmployee" and "fireEmployee" as well as "LogExpense" but for the employee you either

      a) only have LogExpense as an action on the intent

      b) have all the intents for the employee but the actually action for e.g. "fireEmployee" is an out put "sorry you don't have permissions to fire someone".

    • Grant Ronald

      yes