--000000000000ceff5105de3af7e3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable So my plan is for us all to see the demo next week (i hope you were invited) and Ken and Matt will be on and then we can discuss all of these points as a team. Hope they come to the same conclusion. On Wed, May 4, 2022 at 10:20 AM Timothy Thomas wrote: > Ok however this prevents us from RIF'ing these mavencare employees as we > don't have anyone trained on the software. > > On Tue, May 3, 2022 at 10:51 PM Angie Markwell > wrote: > >> Thanks - we are obligated to keep it another 4 months or so. Matt and Ke= n >> are going to determine its capabilities so stay tuned. I agree it is not >> very user friendly and has no reporting capability. >> >> On Mon, May 2, 2022 at 1:38 PM Timothy Thomas >> wrote: >> >>> Hi Angie. Please scan the email below. Maventech sounds like a >>> nightmare. I need permission to move away from asap if were expected to >>> grow. >>> >>> ---------- Forwarded message --------- >>> From: Taneshia Persaud >>> Date: Mon, May 2, 2022 at 8:09 AM >>> Subject: Mavencare Jira Issues >>> To: Timothy Thomas >>> >>> >>> Good morning Timothy, >>> >>> Please see attached. Anything in blue highlights any issues since the >>> acquisition. Many still remain unresolved, pending investigation. I hav= e >>> been getting some push back from the tech team, stating they are able t= o >>> proxy log in and do not experience the same problems as the caregivers. >>> However, the CG states these problems still exist. >>> >>> When we met with Maventech's team last week, they claimed that the M+ >>> App check in/out issues and booking sets are not considered "high" >>> priority. However, I beg to differ. CG who are unable to check in/out = via >>> the app forces them to call/text the office instead which are unnecessa= ry >>> if the app worked. This adds to the workload: one to troubleshoot the i= ssue >>> (we troubleshoot IT issues, NOT the tech team), and then two, the time = it >>> takes to check them in/out. >>> >>> The portal is slow and finicky even on its best days. Some days you try >>> to push jobs 3-5x before it works the way it should, as recently as Apr >>> 14th. I will say these issues have been more prevalent within the last = 1-2 >>> months. Other times the bookings show negative hours although the date, >>> hours, rate and rate type are all correct. >>> >>> With booking sets, especially for our larger cases or those clients who >>> have ongoing shifts, it takes a very long time for the system to refres= h >>> after each adjustment is made. When the bookings set renders an issue, = we >>> have to manually add in each booking/shift one by one. Most recently, e= ven >>> after you make all the adjustments, as you get to the final page to >>> "confirm" your changes, it gives you an error message so you have to st= art >>> the process all over again from scratch. >>> >>> There have been issues with adding booking sets not saving w