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 quietly stopped fitting.

The provider was not bad. It was big, and for a small practice that meant every call was answered by somebody new, and every somebody new started from the beginning. Nothing carried over. The people were competent; the model gave none of them the chance to know the client.

The problem that made it unbearable was email. As a financial advisory practice, their email ran through an arrangement hosted via their broker-dealer, built around the compliance requirement that every message be captured and reviewable by the back office. The arrangement technically satisfied that requirement and practically satisfied nobody: 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 arrangement, 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 just unowned. That distinction matters, and it is exactly what a rotating cast can never establish: when each ticket gets fresh eyes, every recurrence looks like a new problem, and nobody is positioned to say "we have seen this three times, the approach is wrong."

What we did

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. But the requirement is about where copies of the mail go, not about who has to host the mailbox. So the practice moved to its own Microsoft 365, with journaling configured to deliver the compliance copies to the back office automatically. Compliance kept everything it was entitled to. The practice got modern, reliable email it actually controlled.

None of that is exotic. It is the sort of answer that surfaces when somebody sits with the whole problem instead of the ticket in front of them, and it is why continuity of people is not a soft benefit. It is the mechanism by which problems get solved instead of managed.

Then came the part everybody fears about switching providers, and it did not happen. The outgoing provider handed over what was needed, and Tech Dynamix took care of the rest in a day. One day, from handover to running. Switching is routinely imagined as a month of disruption, and sometimes, when nothing is documented, it can be. It can also be a Tuesday.

Four years later the practice is still a client, and the thing they mention is not the migration. It is that when they call, the person who answers 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 the back office its compliance copies automatically
• A switchover measured in a day
• Four years of the same people answering the phone

The lesson for anyone in a similar seat is about diagnosis. The practice spent a year assuming its email problem was difficult. It was not difficult. It was unowned, and the difference between the two is invisible from inside a support queue. If a problem has survived a year of tickets, the question worth asking is not "why is this so hard" but "has any one person looked at this from end to end."

That is also the honest pitch for switching providers when the fit has stopped working: not that the next provider knows magic, but that a first conversation costs nothing, and sometimes it solves the thing on the spot.