Customers are more accountable with their information and maintaining the accuracy. They have more control of what they want TinyEYE Service Providers to provide to their schools and students. The Customer Success Team won't spend time on gathering and maintaining this information. The information would be visible to placed Service Providers and they can reach out directly to the Decision Maker for clarity rather than the Customer Success Team. Will no longer have to enter this information in 2 platforms.
I am hoping this idea can be revisited by Product, and wanted to add another note as it's come up a couple times this year, if we could prompt service information a customer should enter, something regarding their Discharge Process would be very helpful, as we get questions about this from practitioners and do not currently collect it. In cases where we have made notes, we never know if the information has changed or is still accurate (puts TE at risk of giving misleading information), so it's best to be reviewed and received yearly by the customer.
I am very supportive of passing more accountability to the customer to provide information, requirements, timelines, etc.
We also need to understand that there is often a significant gap in times between receiving a closed-won need.....getting initial information to support recruitment....getting the final caseload or specific special education needs, receiving scheduling requirements or restrictions, etc...some or all of which may shift the placement confirmations and timelines.
As this is explored, please ensure that Sourcing & Recruitment are a part of the development. :)
This idea would be hugely beneficial to customers and practitioners, as well as the Customer Care Team! We currently have a situation requiring significant cleanup and efforts for our team in response to a misunderstanding of assessment reporting related requirements that impacted 8+ practitioners and five schools. If the customer could more clearly communicate expectations in one place for all practitioners as a source of truth and assume responsibility for that with this method, it would save a lot of time, and frustration for both customer and practitioner as work needs to be redone in response to misunderstandings. Additionally, the information entered into Monarch by the customer could feed into Salesforce to help with clarity around recruitment expectations (often practitioners will want to confirm what IEP system is used, or if Medicaid is required, for example) while considering a placement.
This could be part of the customer intake process and where we collect service level information for customers. It would require set up of a billing customer account and they would need to input it in, and then the salesforce integration could feed it back to Salesforce to support recruitment. Things like assessment types and information, case management scope, IEP system and documentation expectations. It would be so much more helpful to put the accountability on the customer to provide this information in their own words to support startups and recruitment. It would help avoid escalations and miscommunications down the road, or at least put the responsibility on the customer to maintain accurate information.
Magnitude is: all active customer accounts in Monarch. It would eliminate manual tasks for this internally but also mitigate customer issues that currently land at TinyEYEs doorstep and a failure on our part to communicate these requirements to practitioners.
Didn't know which one to add this to :)
We don't need to capture this in Salesforce, except items to support recruitment, if we put the onus on the customer to input this at startup. Then they are accountable to maintain this information accuracy. So we need a way for customers to outline their expectations regarding assessments, progress notes, IEP meetings, or other service delivery item requirements in Monarch that the practitioners can view and apply as they work with them.
We are finding that without this available there is no way for this information to be relayed consistently to practitioners, and sometimes it's not but comes up later when it is found that the services are not meeting the customers requirements.
See Tlicho and mismatch in how practitioners are doing assessments vs. what school might want. We are learning each practitioner is doing these differently so also poses challenges for customers to locate information on assessments.
To overcome this we currently have to manually create Good to Know documents that TinyEYE then becomes the proprietor of, and responsible for the information therein. We then take responsibility if it is not maintained or current. Instead, if the customer could develop this and input expectations on a few topics to easily communicate to their new or returning practitioners through the Monarch office directly.