A Year of Tickets, Solved in the First Meeting

A financial advisory practice came to Tech Dynamix with a problem that had been open for a year and a provider relationship that had stopped fitting.

The provider was large and competent. For a small practice, that size meant every call was answered by somebody new who started from the beginning, and nothing carried over. The people were capable, but the model gave none of them the chance to know the client.

Email was the problem that made it unbearable. As a financial advisory practice, it ran its email through an arrangement hosted by its broker-dealer, built around the compliance requirement that every message be captured and reviewable by the back office. The arrangement met that requirement on paper, but the email itself was a constant source of trouble, and a year of support tickets had produced a year of patches.

• A basic back-office email problem, open for a year
• A new person on every call, each starting from scratch
• Email hosted through the broker-dealer, serving the compliance requirement and little else
• A small practice paying for a support model built for much larger clients

Nobody at the practice could say whether the problem was hard or simply unowned. A rotating team can't settle that question, because when each ticket gets fresh eyes, every recurrence looks new, and nobody is in a position to say "we've seen this three times, so the approach is wrong."

The practice sat down with Tech Dynamix for a first meeting, described the year-old problem, and got the answer in that meeting.

The fix was to stop treating the broker-hosted arrangement as untouchable. The compliance requirement is real: every message must reach the back office for retention and review. That requirement governs where copies of the mail go, and it says nothing about who has to host the mailbox.

So the practice moved to its own Microsoft 365, with journaling set up to deliver compliance copies to the back office automatically. Compliance kept everything it was entitled to, and the practice got reliable email it controls.

None of that is exotic. It's the kind of answer that comes up when somebody looks at the whole problem along with the ticket in front of them, and it's why keeping the same people on an account matters. Continuity is what lets someone notice a pattern and fix its cause.

Then came the part everybody worries about when switching providers, and it went smoothly. The outgoing provider handed over what was needed, and Tech Dynamix handled the rest in a day, from handover to running. Switching is often imagined as a month of disruption, and when nothing is documented it can be.

Four years later the practice is still a client. What they mention most is that the person who answers the phone knows them, and things get fixed fast.

• The year-old email problem solved, with the answer proposed in the first meeting
• Their own Microsoft 365, with journaling delivering compliance copies to the back office automatically
• A switchover completed in a day
• Four years of the same people answering the phone

For anyone in a similar position, the lesson is about diagnosis. The practice spent a year assuming its email problem was difficult when it was unowned, and that difference is invisible from inside a support queue. If a problem has survived a year of tickets, ask whether any one person has looked at it from end to end.

That's also the case for switching IT providers when the fit has stopped working. A first conversation costs nothing, and sometimes it solves the problem on the spot. Our post on why businesses leave their IT provider covers the other common reasons.