thanks a lot for your links!<p>I maintain a sort of microblog just about these topics:
<a href="http:&#x2F;&#x2F;www.twitter.com&#x2F;solyarisoftware" rel="nofollow">http:&#x2F;&#x2F;www.twitter.com&#x2F;solyarisoftware</a><p>Me too I just discovered Chris Messina&#x27;s definition of &quot;conversational commerce&quot;, definition that I like.<p>About &quot;personality&quot;:<p>Maybe some years ago we have called this just &quot;user profiling&quot;.<p>In facts approach I suggested (modeling dialogs as a composition of state machines: <a href="http:&#x2F;&#x2F;www.github.com&#x2F;solyaris&#x2F;dialogs" rel="nofollow">http:&#x2F;&#x2F;www.github.com&#x2F;solyaris&#x2F;dialogs</a>) is just a workflow framework indipendent by the personality&#x2F;profiling implemenentation.
- On one side personality&#x2F;profiling could be delegated to to some &quot;inerithed class&quot; (of what I defined as &quot;elemental&quot; dialogs).
- on the other side I&#x27;d delegate in the &quot;interpret&quot; method.<p>Let&#x27;s consider the usual ecommerce workflow. This could be splitted in 2&#x2F;3 successive dialogs:<p>1. compiling a shopping cart - dialog<p>2. setting the delivery address - dialog<p>3. setting the delivery time - dialog<p>So, by example, in the delivery address dialog, the chat bot (or &quot;conversational agent&quot;) know the buyer person interacting (because he stored somewhere the buyer address in a previous &quot;profiling&quot; dialog ), so the chatbot could simply propose to use the stored address or submitting a new one.<p>Just to say, that, for business workflow, maybe the &quot;personality&quot; maybe is just a smart profiling.
isn&#x27;t it ?<p>giorgio