ABCDEFGHIJKLMNOPQRSTUVWX
1
App FeatureTypes of user actions / requestInformation required to fulfil user requestDifferent ways in which users will speak out the informationGrouping of user inputs based on information spoken in input App response - screen transitions & voice confirmation / promptNotes/Comments
2
<Give a description of the end user's higher level intent, eg: Pay Bill, Book a ticket, View a plan, Order food, etc><List variations that could happen with this intent, where each variant could need different inputs. Eg Pay Electricity Bill vs Pay Mobile Bill or Book a bus vs Book a flight which would need different inputs from the user>

<Add a row/cell for each variant>		<For each of the variant in the previous column, list the data that would be needed to satisfy that user intent/variant>

<Add a row/cell for each item needed>		<List some sample ways in which the user could trigger that user intent/variant>

<Dont create multiple cells for each utterance, but just put them one below the other, but in a single cell>		<List the variants based on what information could be missing. Eg when booking a ticket, user might not say the destination or source, etc>

<Add a row/cell for each sub possiblity>		<For each of the variant row in the previous column, document how the app should respond/react. Including what should be spoken back and what screen transitions should happen>
3
4
5
<Give a description of the end user's higher level intent, eg: Pay Bill, Book a ticket, View a plan, Order food, etc><List variations that could happen with this intent, where each variant could need different inputs. Eg Pay Electricity Bill vs Pay Mobile Bill or Book a bus vs Book a flight which would need different inputs from the user>

<Add a row/cell for each variant>		<For each of the variant in the previous column, list the data that would be needed to satisfy that user intent/variant>

<Add a row/cell for each item needed>		<List some sample ways in which the user could trigger that user intent/variant>

<Dont create multiple cells for each utterance, but just put them one below the other, but in a single cell>		<List the variants based on what information could be missing. Eg when booking a ticket, user might not say the destination or source, etc>

<Add a row/cell for each sub possiblity>		<For each of the variant row in the previous column, document how the app should respond/react. Including what should be spoken back and what screen transitions should happen><Add any comments or notes related to the interaction flow such as potential next steps, user choices, exceptions, assumptions etc.>
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100