Velocity powered by Wavelink

Grammar Files

Grammar files define which speech-to-text words and phrases the Speakeasy engine will recognize on a user device. The terms listed here are what the engine looks for and compares verbal responses against. When the engine finds a matching term, it executes an associated command or enters the term into the a field.

Speakeasy for Velocity does not currently come with any default grammar files. You must create your own based on the commands, phrases, and responses you expect users to make when navigating a session.

To create a grammar file:

Use a word processing application like Notepad

Save the file in .bnf format

Follow the required grammar file structure

Add grammar terms as well as any alternate return values

Watch a related video (3:38)

As a best practice, we recommend breaking up terms into multiple grammar files. Once separated, you should use scripts to load and unload specific grammar files so that the performance of the Speakeasy engine doesn't affect the performance of the Velocity Client.

The more grammar files associated with a scope, the higher the chance that the engine will return an inaccurate value.

I want to know how to...


Was this article useful?    

The topic was:

Inaccurate

Incomplete

Not what I expected

Other