--00000000000074b43905e3db7b69 Content-Type: text/plain; charset="UTF-8" Timothy - I'll include that in the conversation, thanks for flagging - but as we don't have the licensing restriction there, assumption is that we can move to TheKey sooner - is your preference to move branding in Toronto sooner or later? Thanks, Lucas On Fri, Jul 15, 2022 at 1:32 PM Timothy Thomas wrote: > Thanks Lucas. Is there an alternate timeline for Toronto? > > On Fri, Jul 15, 2022 at 1:23 PM Lucas Motro wrote: > >> Thanks Kim, yes will circle back here on NY branding timeline after >> circling up with Adam. We were scheduled to meet yesterday but rescheduled. >> >> On Fri, Jul 15, 2022 at 1:19 PM Kimberly Guerci >> wrote: >> >>> Hi all...adding Lucas as he will be meeting with Adam to discuss >>> rebranding of Mavencare to TheKey through a DBA. I think once Lucas has >>> his meeting we will have a better idea as to how to move forward. >>> >>> On Fri, Jul 15, 2022 at 11:27 AM Alexa Graziani >>> wrote: >>> >>>> Hi Audra, >>>> >>>> Can we please have an internal meeting to get caught up on what we are >>>> legally allowed/not allowed to do with the Mavencare name / transitioning >>>> to TheKey before coming up with ideas and meeting with the Mavencare team >>>> on this? I am still unsure of where this landed. >>>> >>>> Sincerely, >>>> >>>> On Fri, Jul 15, 2022 at 7:24 AM Isabelle La wrote: >>>> >>>>> Hi Alexa/Audra and Mavencare Team, >>>>> >>>>> Apologies for my delay getting this email out but we meant to send >>>>> this last week. During last week's IT Meeting with Mavencare, as we are >>>>> starting to transition away from the @mavencare.com email domain, the >>>>> question arose about how to handle web leads that are coming in through >>>>> Mavencare's main website that is then using distribution list for >>>>> leads@mavencare.com and being sent to the local care teams. >>>>> >>>>> Not sure what volume is like but our assumption is that we will >>>>> eventually need to move away from any of these website dependencies as we >>>>> near the end term of when we are allowed to legally carry on with the >>>>> Mavencare name. Not knowing the intricacies, we figured we needed to have a >>>>> broader discussion with the right players managing both websites and how >>>>> leads are coming in from the respective websites to find a proper solution. >>>>> One of the ideas is to just have Mavencare indefinitely redirect their >>>>> current main website URL to the new Mavencare website hosted by TheKey - >>>>> which I would assume requires approval from the Mavencare folks but we are >>>>> open to any and all long-term solutions proposed by those closer to how the >>>>> websites/leads are managed (ex. Nukul, Alexa, etc). >>>>> >>>>> Please let us know your thoughts and feel free to include any >>>>> important players to help in this decision making process that I may have >>>>> not included in this original thread. >>>>> >>>>> >>>>> -- >>>>> *Isabelle La * >>>>> Project Managemen