Check that a dialogue & utterance have been identified in the route before trying to retrieve it from storage
Remove get transcript by utterance index as not best way to deal with ordering of utterances within a dialogue
Dialogue doesn't need an index. CouchDB sequential UUIDs will do just fine
No need for sequential idx for each utterance in a dialogue

Sequence of utterances, that make up a transcript can be generated just fine, and possibly more accurately from the utterance's creation timestamp
Now using requests so update req
Use a view (map/reduce) to get number of dialogues