2022-11-15T07:54:45.970346+00:00 app[web.1]: ReferenceError: resbody is not defined
2022-11-15T07:54:45.970348+00:00 app[web.1]: at /app/index.js:197:5
2022-11-15T07:54:45.970349+00:00 app[web.1]: at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2022-11-15T07:54:45.970349+00:00 app[web.1]: at next (/app/node_modules/express/lib/router/route.js:137:13)
2022-11-15T07:54:45.970350+00:00 app[web.1]: at Route.dispatch (/app/node_modules/express/lib/router/route.js:112:3)
2022-11-15T07:54:45.970350+00:00 app[web.1]: at Layer.handle [as handle_request] (/app/node_modules/express/lib/router/layer.js:95:5)
2022-11-15T07:54:45.970350+00:00 app[web.1]: at /app/node_modules/express/lib/router/index.js:281:22
2022-11-15T07:54:45.970351+00:00 app[web.1]: at param (/app/node_modules/express/lib/router/index.js:354:14)
2022-11-15T07:54:45.970351+00:00 app[web.1]: at param (/app/node_modules/express/lib/router/index.js:365:14)
2022-11-15T07:54:45.970352+00:00 app[web.1]: at Function.process_params (/app/node_modules/express/lib/router/index.js:410:3)
2022-11-15T07:54:45.970352+00:00 app[web.1]: at next (/app/node_modules/express/lib/router/index.js:275:10)
Are you working on the on-prem (open source) version of Tiledesk? Or in the cloud version (the tiledesk.com subscription based service)?
Furthermore I see that you are using this code-based Dialogflow integration tutorial:
This tutorial refers to a self-developed dialogflow connector. Are you planning to develop your own Dialogflow connector? This makes sense if you have particular needs in Dialogflow integration.
Consider that we already provide a Tiledesk native connector, available in cloud and on-prem.
I asked you these questions just to better understand your issues.
I was able to do the handoff using custome code in the Fullfilment (Dialogflow interface) calling the API Rest.
I have notice that assigment is done to all the group (no directly to an agent), and they have to pick up each conversation. How conversations can be assigned directly to the agents based on the availability?
This is how the conversation arrives to the Group:
We can close it. We have identified that during testing the agent didn’t reply and it was causing issues, for avoiding that, in development, we have turned off this feature in the Smart Assign.