Hi cavagnaro,
The easier way how to implement required functionality is an add-on for MM/MCR called "Content Analyzer". This is separately licensed option allowing you to defined some statistical model using natural language, screen the incoming interactions against that model and do some action based on the result of screening (e.g. auto-reply). I played with CA for a while so my experience is very limited but it seems to be quite powerful. Of course, it isn't easy to create the model and "train" the engine. Please look at "Multimedia 7.2 User's Guide" for more information.
The second way is more work demanding but I would say it's possible to achieve required functionality too.
1st case - auto-reply for common questions
---
You have to create set of screening rules and screen each incoming interaction against these rules. Each rule contains several keywords related to particular common question. If the engine finds defined keywords in the subject or body then you identified potential common question. The hardest job is definition of the keywords because the basic engine (without Content Analyzer) doesn't allow you to defined a weight of the keywords.
Example - the rule is screening for the words "hour" and "deliver". If you receive a message "Which are the delivery hours" then that message will be identified. But if someone sends you a message "What time you can deliver the goods" then the identification fails. Of course, it's possible to create more complex question using logical operators (AND, OR) but it's not so easy to create the right "formula".
2nd case - getting some data from email's body and using it in the routing
---
Again the answer is "screening rules". It's possible to define a screening rule using regular expression and attach found string to UserData. Once you get the data you can process them in the strategy and generate an auto-response (just an example).
I’m using it for one of our customer and it’s working pretty well. The clients of our customer have to enter some code to the email’s body otherwise the email isn’t routed to the agents. It was quite easy to implement that functionality and to be honest we spent most of the time fine-tuning the regular expression. It should be much easier for you if the body is generated and formatted by some web application.
Hope the information above helps you.
If you have more questions just let me know.
Cheers,
René
PS. Based on your activity on this forum you can have as many questions as you want
