-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Account Manager introductions #298
Comments
@laneymangan here's the email copy I've been mentioning. Thoughts/ edits welcome! You can ignore the top where I'm doing some agency grouping, since not all agencies will need this. I'll also give this to Kathryn to take a look at after you :) |
Adding Kathryn as an assignee since she is reviewing along with us as we edit, make plans for specific agencies, etc 🙂 |
It looks good! I made one comment on the doc. Do I need to assign it back to you @o-ram? |
@o-ram - I like the instructions! Let me know when you want me to review :) |
Thank you! @kathrynmsullivan and @laneymangan ready for you both to take one more look over this and then I think it's ready for us to use as we continue to roll out the official introductions to individual agencies. |
I think it looks great! No edits. Let me know if I can help with creating Hubspot tasks or anything else here @o-ram |
Looks great, good job GOOD JOB! |
@laneymangan thanks for the offer! If you have time, would love for your help with creating Hubspot tasks. Definitely not an urgent thing though, so no worries if you don't have time. We've just been crossing agencies off at the bottom of the doc who either have received an intro or don't need one, but the ones left should likely be moved into Hubspot. |
Tasks have been created and will continue to be completed and tracked there |
Send emails to all on listCreate HubSpot tasks for needed introductions, since they will roll out. Creating the tasks will satisfy completion of this portion of the issue.Once complete, fold mention/announcement of this into some sort of wider Cal-ITP communication - will be folded into the weekly slack message posted on Friday. We determined it does not need a special announcement of its own.
The text was updated successfully, but these errors were encountered: