Intuitive DTD2 SmartPlan
This company raves about DTD2. That being said how about we have a KW Created Smart plan Much like the birthday smart plan, Monthly neighborhood nurture, and the home anniversary that uses the AI to effectively schedule a task for the next corresponding day for that specific DTD2 task. Whether it may calling, texting, emailing, or sending a postcard.
Tips: Each smart plan should be dedicated to one thing
- One for Calling
- One for texting
- One for Email
- One for Postcards
All to keep up with the models for DTD2 and because not all agents are at the same level of business to send out postcards because of finances and they don't want to archive any task due to that conditions. Let's not also forget their contacts' preferred method of contacting them some might not check emails and we don't want to waste a credit for that
P.S.:The AI should preemptively dived the total number of the total contacts for that week's DTD2 category and schedule them among the weekdays.
Example: Jan 3 2022 is to call all the in our database A&W with 50 contacts total for that category:
Smart plan A: (Calling) The AI would divide the 50 total contacts automatically to Place 10 contact w/ a task for Monday, 10 other contacts w/ a task for Tuesday, 10 other contacts for Wednesday, etc. All dedicated to ONLY calling
Smart plan B & C: (Texting & Emailing) will do the same in a separate smart plan.
P.s.s: for Tullio & command email the agent can ONLY edit the text NOT the format as far as timing and date setting.
Smart plan D: (postcards) the same to send time them out on different days so it wouldn't be so time-consuming doing and prepping all 50 on a Monday whether someone does it manually or they pay a provider.

-
Madison Parker commented
To address this, I’ve created a workaround that might also inspire a future enhancement. For my DTD2 SmartPlan, I only add myself as the contact, ensuring the plan runs smoothly since all tasks are manual. The SmartPlan spans all 52 weeks of the DTD2 system and generates weekly tasks to call, text, send a social message, and mail a notecard to the respective letters for that week.
When it’s time to complete these tasks, I filter my contacts by the DTD2 tags I've created and assigned to the respective contacts to make it easy to identify who I need to call. For the other tasks, I use the search-by-last-name feature to locate contacts for texting, sending social messages, and mailing notecards. While this system works, setting it up is time-consuming and may be confusing for some users.
If SmartPlans had a date-specific feature, it could add more flexibility to SmartPlan creation by allowing individual contacts to be assigned to the plan without the hassle of determining the correct start date. This improvement would not only streamline the process but also make implementing the DTD2 system significantly easier for agents, ensuring no one falls through the cracks.
Making DTD2 functionality a default feature could further benefit users by providing a strong business foundation and simplifying engagement with their database.
-
Randyl Walters commented
This could also be accomplished by creating a smart plan format whereby the smart plan is scheduled to run at set intervals regardless of when a contact is added to it. Thus if A+W creates call tasks for all A+W tags, it will run every quarter. Any new contacts added with the A+W tag will not start immediately, nor will the agent have to look up the DTD2 schedule and select the appropriate time to start, it will be added to the smart plan immediately, but will not RUN until the designated date. That may be a simpler way to solve the problem.
An agent could then create a smart plan such as this for each activity they would choose to do.
Additionally, if there were a way to add tags to steps in a smart plan, then if they choose to set up calls, they need only set up 12 steps for the first quarter and then repeat it quarterly. All DTD2 calls could be completed on one step.
The same functionality could be added for other tasks as well. Let's say an agent wants to send a holiday greeting. As it stands, if the greeting has a text and an email step, it will throw off an error for those contacts who don't have a phone number or those who do not have an email. What if you were able to add contacts with the "has phone number" tag to the call step and contacts with the "has email" tag to the email step? This is the same function within the larger function - it's like nesting one smart plan functionality inside the other so to speak.