You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have prepared a model to discuss a behaviour change in the telephone skill.
It is based on my experience with other voice guided applications.
The contact name match should involve all naming fields: name, surname, nickname, second name, display name, etc.
There could also be some well defined priority when matching, like:
nick > display name > name + surname (mum > Nick's mum > Terrance Mummers)
name > 2nd name
surname > maiden name
The data fields read by the tts when presenting multiple contacts or single contact phone types might be a subject of user preferences and as such could be modifiable in the skill settings.
I have prepared a model to discuss a behaviour change in the telephone skill.
It is based on my experience with other voice guided applications.
The contact name match should involve all naming fields: name, surname, nickname, second name, display name, etc.
There could also be some well defined priority when matching, like:
The data fields read by the tts when presenting multiple contacts or single contact phone types might be a subject of user preferences and as such could be modifiable in the skill settings.
Uploading the Dia source file for the diagram.
dicio-call.dia.gz
The text was updated successfully, but these errors were encountered: