Where does call control belong?

[matthewblack]

Howdy,

This is more of a question/discussion around the separation of responsibilities as it relates to this driver.

Right now, this drivers intent is to handle the conversational AI experience once a user is actively connected to a call (and has a SID).

For users that don't call into the the Twilio number and automatically create a session, it's left up to the developer to build specific call control features. Some common examples are:

• Generating an Outbound Call
• Modifying Calls In Progress
• Enqueuing / Queuing Calls
• Bridging / Joining Calls
• Etc

Will this driver help with any call control functions or is specific call control better left up to the individual developer to facilitate and Stealth / Stealth-Twilio-Voice is best served for once an active session (SID) is present and the conversational AI experience starts?