Notify Conference Calls [notify_conference_call] records are getting triggered automatically when incident is created.Issue Notify Conference Calls [notify_conference_call] records are getting triggered automatically when incident is created.ReleaseQuebec or priorCauseAs per trigger rule, the workflow "On-call: Assign by Acknowledgement" and then subflow"On-Call: Assign by Acknowledgement per Rota" would get triggered.If the user has voice setup, then it is expected that the 'On-Call: Assign by Acknowledgement Voice' workflow would also get triggered for Press 1 to accept and Press 2 to reject use case.- The workflow 'On-Call: Assign by Acknowledgement per Rota' then executes the 'On-Call: Send Notification' which is responsible to initiate a notify conference with one participant which is an expected OOB (out of box) behavior.- WF activity definition, 'On-Call: Send Notification' where this logic is stored.Resolution- The workflow 'On-Call: Assign by Acknowledgement per Rota' then executes the 'On-Call: Send Notification' which is responsible to initiate a notify conference with one participant which is an expected OOB (out of box) behavior- Notify is really just notifying user and not initiating a conference call - The reason SN initiated conference call was that notify_call -> Call table didn't have 'source' field. Hence, a conference was used which had source populated. Currently notify_call supports source, so the feature might be possible to do using notify_call. This will be reviewed / worked on by our internal teams.