# data[].attributes.body
I do not think you get the credit you deserve for pushing this team in the direction it needs to go. You are the mad AI scientist that fuels this teams purpose.

# data[].attributes.body
I think the way people on this team speak to each other is quite outlandish. Having a attitude and being rude is nothing to be proud of. It almost seems as if individuals actually thrive off of demeaning others on this team during huddles.

# data[].attributes.body
You have been instrumental to my learning thus far as a UC admin. Thank you.

# data[].attributes.body
Despite negotiations with RingCentral, our product team was the last to know, and we are now dedicated to delivering the project the SVP of Serving wants by the end of the year. This is LOA on steroids, with two of the three teams under Product Delivery demanding support. Using the hammer, we will be pummeled by every request they need. We are outnumbered, and meanwhile, RingCentral can replace OrecX with InGenius and do a sales co-pilot. 2025 won't be like 2025.

Footnote: Despite 5 engineers, 2 architects, a team of 15, and the support of CDW, RingCentral is being brought in.

# data[].attributes.body
Despite the Head of Underwriting, SVP, personally asking for summarization, despite both VPs practically begging for it, despite the VP of Product Development/Underwriting offering to work with us, and despite the Enterprise Architect for Artificial Intelligence and the Chief Architect at UWM willing to assist, we fought each other while CX swooped in and took the prize.

# data[].attributes.body
Mixed into Slurpee

# data[].attributes.body
I appreciate you helping me with some bossiness logic question for Number reassignment project.

# data[].attributes.body
So everyone is different and I dont really care if the meeting are in the morning or evening but if possible can we not change meetings the day of. That way we know what our schedule is going to look like for the day. Obviously super important meetings will come up just would like to avoid it if possible.

# data[].attributes.body
Everything does not have to be a meeting! Some topics can be discussed through email or a simple shoulder tap. I found myself having very little task time to actually complete task. I'm struggling to find the time for my current project for call summarization but am constantly asked about timelines. It can be frustrating!

# data[].attributes.body
I feel like the team has been collaborating well together and communicating when issues arise

# data[].attributes.body
It would be cool (if possible) if we could agree to no meetings before 12 PM as a team, I realize some collaboration from other teams or other business needs may require it but can WE as a team not schedule any trainings or scrum events until AFTER noon? Some of the best work of the day is in the morning and it will at least allow us devs to make progress for the day before we are required to jump from meeting to meeting.

# data[].attributes.body
Some team members have concerns, questions, and thoughts on the standups. Lets take some time to talk through it.

# data[].attributes.body
Taking on more responsibilities, learning more processes, and starting their days working without waiting for instruction. These things deserve recognition.

# data[].attributes.body
Constantly having to pivot to clean up mistakes and fix issues caused by others Teams who have control over the data we use to do our jobs, but no responsibility in curating and maintaining the consistency and accuracy of said data (DEA for OrecX Hierarchy issues and Brand360 Team for the Data we use to brand people in First Orion)

# data[].attributes.body
As everyone settles more into their roles and assist each other in their workflows, the Team has come together and is gelling better. The Fuddles and Team activities also reinforce this.

# data[].attributes.body
I really appreciate the entire team's support and backing of me as a leader. This is my first time actually being a people leader. Yes, I have unconsciously been the leader in different roles across my career, but I can trust all of you, I respect all of you, and I appreciate the vice versa (well I at least hope y'all trust me and respect me lol). Best team a leader could ask for - hands down!

# data[].attributes.body
Hear me out...

We, and by we I mean devs, come up with a tool that lets us enter our daily FTBs into, and then when it comes time to generate an SLR, it shows us a summary of FTBs that we can use to create the SLR. Or something that combines the two into one thing and removes some of the copy paste feelings.

# data[].attributes.body
It's not easy being new to a team, or new to an industry. Good job on both accounts. Keep on keepin on. And get that knowledge, and experience!

# data[].attributes.body
We need an end to end support map that is color coded by the team that owns the part.

# data[].attributes.body
I'm still a bit confused on who supports specific parts of the whole process. We need an end to end support map that is color coded by the team that owns the part.

# data[].attributes.body
When folks go on PTO, we've done a good job as a team to make sure things get addressed. Brittanni stepping up and keeping us focused and on task. Pat and Gjon always stopping by to see who's working on what and if they can help in any way. Mars pitching in and covering some of Aaron's responsibilities with Twilio. Erik keeping a firey Orecx on the tracks. Kyle getting into the mix and dirtier (in a good way) every day. Josh and his basketball cosplay, love the positive attitude!

# data[].attributes.body
As we used the API tools "those people", aka the devs, were able to make it so it gathered the results from the numbers being setup and listed which were a success and which were missing in Twilio. This removed the manual crawl we would perform after the numbers were processed to pull out all of the ones we would need to submit a port request for. Depending on the volume of missing numbers, this could take a few admins a few hours. Now we can just pull the details of a job and get both lists as needed. Brilliant.

# data[].attributes.body
The amount of records we were able to process in Twilio, thanks to the API tools that the devs setup, was astounding. for example, flipping a Studio Flow by hand allows me to do about 100+ an hour. With the API tools, we're doing about 200 every couple of minutes. Also, the 100+ an hour isnt stress free, far from it. The 200+ every couple of minutes is more or less "fire and forget" and not stressful on the admin at all.

# data[].attributes.body
Michael's testing on the new API endpoint is impressive! He volunteered to take on the task and is so good to create the test cases and completed the tests timely to speed up the deployment process.

# data[].attributes.body
I love the team collaboration and cross-team collaboration for my LO phone number reassignment project. All the involved parties are willing to help.

# data[].attributes.body
I am so honored to have you on our team, I'm excited to see all the great work you do. Also great job on the number reassignment project, you do a great job of communicating your needs and impediments.

# data[].attributes.body
Working with The Tech Pros, Josh, and Yovan on the number reassignment project has actually gone smoother than I expected. They have been receptive to help, and also the communication has improved since the start of the project.

# data[].attributes.body
Oreo will always be god tier. Anything else is a peasant compared to it...

# data[].attributes.body
Back and forth confusion on the Voice Insights project and if/when it'll get developed. The MVP still feels a bit fluid as well (to no fault of anyone) due to business projects such as ROMULUS & LOA.

# data[].attributes.body
I've REALLY enjoyed being able to develop the frontend of Voice Insights. What started as practice sort of transition into an opportunity to get ahead of things for the project.

# data[].attributes.body
Thank you for all the things you do and how you juggle multiple projects and initiatives for the team. While you take ownership of a lot of things, its also nice that you include us and get our opinions on things as well. I appreciate that :)

# data[].attributes.body
I know you've been told numerous times already but wonderful job hitting the ground running and immediately reaching out to people to get things done for your story! Looking forward to testing it when finished!

# data[].attributes.body
A few team members before the team was created, had some pretty awesome ideas on how to improve Call-Analytics and give additional tools to the CX individuals. These ideas came from team members and not the business so it seems like a great opportunity for the team to do something proactively. However, it seems lately that higher leaders and other IT teams / business teams have been metaphorically arguing and fighting over who should do this or that for the business. We have a wonderful opportunity to develop something useful to the business and its something a lot of the team members are eager to develop, so I don't understand why there is so much pushback at this time. I understand business needs change but this would be a big moral hit to some of us if this is stopped or diverted to another team. I know a lot of this stuff is ongoing but as I said, "just venting".

# data[].attributes.body
You're you.

# data[].attributes.headline
Other Teams more receptive to Helping us

# data[].attributes.subject
Other Teams more receptive to Helping us

# data[].attributes.body
We don't have to fight as hard to get it across to teams outside our Vertical that these projects will only move when everyone is equally informed and willing to assist each other

# data[].attributes.body
You're amazing and my first favorite.

# data[].attributes.body
cherry & coke mix