We currently dial our members via Power dialing, 3 times (main, alt, main phone) based on wrap outcomes with 48 hours in between calls. We use rules, filter and recycle functions to prioritize callable members. My question is all about the scheduling of a callback, how do you ensure the dialer does not redial the member outside of the scheduled callback booked through the power dialer campagin?

Desire:

• would like to call a member and if the outcome is that they would like a callback at a specific date/time (without queue assignment) we are able to schedule it and the dialer would then stop dialing them and the scheduled callback would be the next outreach to the member. 
• would like to use the scheduled callback queue assignment to route scheduled callbacks to a different queue to be called back at the scheduled date/time and when this happens they are reviewed from the current call campaign the call originated from and only called through the scheduled date/time booked within the queue it is scheduled to.

Experience we are getting:

• if we set the wrap for the scheduled callback wrap up as uncallable the dialer does not redial the member through the dialer campaign but also does not allow the scheduled callback to happen in originated dialer campaign or an assigned queue
• if we use the assign queue option the scheduled callback is moved to the queue and dialed at the proper date/time but does not get removed from the originating dialer campaign and therefore still gets additional calls via the dialer even though they have a scheduled callback booked

Does anyone have a work around or can anyone explain how this is supposed to operate? is the scheduled callback function only available for call campaigns only placing 1 round of calls? Seems like a feature flaw?

Here is my suggestion:

1. Use Wrap-up rule to run a workflow and supply the contact information and desired
2. Workflow will take the contact information hold the contact in the workflow for the desired day and time
3. Workflow will insert the contact into the contact list at that time and dial it as normal.

Let me know if there are any questions. 

We currently dial our members via Power dialing, 3 times (main, alt, main phone) based on wrap outcomes with 48 hours in between calls. We use rules, filter and recycle functions to prioritize callable members. My question is all about the scheduling of a callback, how do you ensure the dialer does not redial the member outside of the scheduled callback booked through the power dialer campagin?

Desire:

• would like to call a member and if the outcome is that they would like a callback at a specific date/time (without queue assignment) we are able to schedule it and the dialer would then stop dialing them and the scheduled callback would be the next outreach to the member. 
• would like to use the scheduled callback queue assignment to route scheduled callbacks to a different queue to be called back at the scheduled date/time and when this happens they are reviewed from the current call campaign the call originated from and only called through the scheduled date/time booked within the queue it is scheduled to.

Experience we are getting:

• if we set the wrap for the scheduled callback wrap up as uncallable the dialer does not redial the member through the dialer campaign but also does not allow the scheduled callback to happen in originated dialer campaign or an assigned queue
• if we use the assign queue option the scheduled callback is moved to the queue and dialed at the proper date/time but does not get removed from the originating dialer campaign and therefore still gets additional calls via the dialer even though they have a scheduled callback booked

Does anyone have a work around or can anyone explain how this is supposed to operate? is the scheduled callback function only available for call campaigns only placing 1 round of calls? Seems like a feature flaw?

Interesting concept. You are saying, run a workflow on wrap up, put a wait step that is as far out as the scheduled callback and insert into a new campaign. Keep in mind the wait has a max of 72 hours. 
There are limits around workflow execution per minute/hour - with this you would have workflows out there for 2 days that are "executing" so how would that count towards the limits?

Here is my suggestion:

1. Use Wrap-up rule to run a workflow and supply the contact information and desired
2. Workflow will take the contact information hold the contact in the workflow for the desired day and time
3. Workflow will insert the contact into the contact list at that time and dial it as normal.

Let me know if there are any questions. 

We currently dial our members via Power dialing, 3 times (main, alt, main phone) based on wrap outcomes with 48 hours in between calls. We use rules, filter and recycle functions to prioritize callable members. My question is all about the scheduling of a callback, how do you ensure the dialer does not redial the member outside of the scheduled callback booked through the power dialer campagin?

Desire:

• would like to call a member and if the outcome is that they would like a callback at a specific date/time (without queue assignment) we are able to schedule it and the dialer would then stop dialing them and the scheduled callback would be the next outreach to the member. 
• would like to use the scheduled callback queue assignment to route scheduled callbacks to a different queue to be called back at the scheduled date/time and when this happens they are reviewed from the current call campaign the call originated from and only called through the scheduled date/time booked within the queue it is scheduled to.

Experience we are getting:

• if we set the wrap for the scheduled callback wrap up as uncallable the dialer does not redial the member through the dialer campaign but also does not allow the scheduled callback to happen in originated dialer campaign or an assigned queue
• if we use the assign queue option the scheduled callback is moved to the queue and dialed at the proper date/time but does not get removed from the originating dialer campaign and therefore still gets additional calls via the dialer even though they have a scheduled callback booked

Does anyone have a work around or can anyone explain how this is supposed to operate? is the scheduled callback function only available for call campaigns only placing 1 round of calls? Seems like a feature flaw?

We currently dial our members via Power dialing, 3 times (main, alt, main phone) based on wrap outcomes with 48 hours in between calls. We use rules, filter and recycle functions to prioritize callable members. My question is all about the scheduling of a callback, how do you ensure the dialer does not redial the member outside of the scheduled callback booked through the power dialer campagin?

Desire:

• would like to call a member and if the outcome is that they would like a callback at a specific date/time (without queue assignment) we are able to schedule it and the dialer would then stop dialing them and the scheduled callback would be the next outreach to the member. 
• would like to use the scheduled callback queue assignment to route scheduled callbacks to a different queue to be called back at the scheduled date/time and when this happens they are reviewed from the current call campaign the call originated from and only called through the scheduled date/time booked within the queue it is scheduled to.

Experience we are getting:

• if we set the wrap for the scheduled callback wrap up as uncallable the dialer does not redial the member through the dialer campaign but also does not allow the scheduled callback to happen in originated dialer campaign or an assigned queue
• if we use the assign queue option the scheduled callback is moved to the queue and dialed at the proper date/time but does not get removed from the originating dialer campaign and therefore still gets additional calls via the dialer even though they have a scheduled callback booked

Does anyone have a work around or can anyone explain how this is supposed to operate? is the scheduled callback function only available for call campaigns only placing 1 round of calls? Seems like a feature flaw?