Dan,
The agent, in the UI, ends a conversation by using the disconnect button. There is a button labeled "End Messages" at the top of the message text history in the Agent UI. Once that is done the conversation is then disconnected, and Agentless api can then be called to send a message to the end user from the same sms provisioned number that the agent was using, since the conversation is now disconnected.
When you say "time based". I think you are referring to the threading timeline which defines how long the same Conversation Id will be reused, for additional messages after that conversation is disconnected. That setting plays no role in this specific scenario though. The problem here is there is an existing "active" conversation. The active term there is the key, it means connected conversation. "Bad request: An active conversation is already in progress"
Thanks,
Greg
------------------------------
Greg Boston
Genesys - Employees
------------------------------
Original Message:
Sent: 04-01-2021 11:07
From: Dan Fontaine
Subject: Agentless outbound texts are failing even a while after conversation is closed!
So, how does an agent end a conversation. Isn't the response/reply time based? That is, the agent really can't end the conversation?