I figured out how to schedule a call in the future - however - since we cannot set the call as SCHEDULED - it defaults to CURRENT - and closes - even thought it is scheduled for the future.
Scheduling a task to make a call. Then creating a second activity to make the call - when SCHEDULED is an option is redundant and takes away from the spirit of a time saving CRM. I understand we cannot all have what we want - but this sounds like an oversight, not an intentional design. But, I could be wrong.
Perhaps, there is a completely logical answer. No matter how many ways, I ask, no one will explain the why. I can except almost anything, if I could just here a reason. Even if the answer is, "it's an oversight."
I just need to explain to my users - why we cannot create CALLS in the future via custom functions, like we can with TASKS. If anyone has a workaround suggestion, I am definitely interested.
Any insight is greatly appreciated.
Thanks in advance.
I tried to insert a graphic - but it just kept spinning. I have attached an image showing the situation.