How Sovereign Financial Group turned fragmented advisor requests into structured Salesforce workflows

Sovereign Financial Group is a registered investment adviser. It works with planning-based financial advisors, builds advice around cash-flow planning using tools like eMoney, and supports both those advisors and their end clients. Alongside its internal team, it supports 21 external advisors, and that number is growing.

Nick Thiede is its Chief Operating Officer. He has spent almost fifteen years in financial services, starting in compliance, moving into technology in the advisory space, and now bringing both to operations.

Salesforce was already the hub for everything operational at Sovereign Financial Group. The operations at Sovereign built a service model on top of it: every piece of work defined as a standardised request, with an expected turnaround and someone who owns it.

Nick and Sovereign Financial Group had built the right operating model, but requests were landing everywhere except Salesforce. The service model needed a practical solution.

Advisors are often away from their desks, meeting clients, and many work without support staff. A request form requires someone to log in, find the right menu and complete every field. Between appointments, with a phone in hand, that is a lot to ask. Even on mobile, "it's not a really easy to use user experience."

Comfort with a CRM varies from one advisor to the next. In practice, the requests came, but they arrived everywhere except Salesforce.

"Things were going in Microsoft Teams chats, or emails, or phone calls, or just personal conversations," Nick says. "They weren't making their way into the system."

Nothing that stayed in a chat thread could be tracked, measured or managed. His team saw individual requests handled, but never the pattern: what was stalling, where things were falling through the cracks. He calls the old process "archaic."

Even the work that did reach Salesforce told them little: only 7% of records carried a request type more specific than a general question.

It is a familiar pattern. The process is sound, and the intake is where it breaks.

Sovereign wants to support all advisors equally well, and boost adoption of technologies available. A firm that invests in Salesforce and builds a service model on the platform gets none of that back if the people it serves work around it.

Sovereign runs Salesforce with the Salentica overlay for wealth management, and tracks client work on a custom request object rather than standard Cases. That one detail ruled out most of the obvious answers. Native email-to-case handling is built around Cases, so it "just wasn't an option for our organization."

The firm demoed several third-party tools. Each fell short somewhere specific. Some could only write to certain objects. Some left the manual work in place. Where an email did not match cleanly, several "flagged an error" instead of attaching it sensibly.

One requirement removed options early, and it had nothing to do with email. "Customer data is extremely important for us," Nick says. "So with this email analysis, it was important for us to find a tool that we can control the access."

The question that led Sovereign to Ortoo was about behaviour, not software. "How do advisors do business normally?" Nick asks. "A lot of them have a cell phone in front of them. They can talk, they can send an email."

Sovereign implemented Email-to-Anything, the email intake engine within Ortoo Orchestrator. Email-to-Anything is how a request gets in. Orchestrator is what runs it once it is there.

An advisor sends an email to a single address, from wherever they are, and carries on with their day. "And boom, it created a request for us," Nick says. "It used AI to examine the email, fill in all the fields that they would traditionally fill out themselves, and really just queued up an email back to them with some of the missing information as well."

Orchestrator reads the message, applies AI to interpret free text, and fills the fields on Sovereign's custom request object. Where something is missing, it drafts the follow-up. What reaches the operations team is a structured request with an owner attached, and a record both sides can see. The aim, Nick says, is to "provide ownership, accountability, and transparency to the advisors and to end clients, to understand where their requests are or their work items are throughout the process."

The tools Sovereign looked at differed less in what they did than in what happened after the contract was signed. "A lot of the other tools were kind of 'figure it out yourself, here you go,'" Nick says.

Ortoo's team took the requirements, turned solutions around quickly and built to fit. Sovereign's CEO put forward ideas of his own during the build, and those went in too. "When we sign up with vendors, we look for partners," Nick says. "And Ortoo has been a great partner for us, not just a vendor."

Implementation was short. "A couple weeks, the team took it, built a solution, followed up with us, took our feedback, made a couple more tweaks, and we were ready to go live," Nick says. "So it's very quick and very easy."

The AI needed some tuning, but none of it, Nick says, proved cumbersome. A few rounds went into customising how data should be presented and what should be left out.

Three things have mattered most since.

The first is that Ortoo works in alignment with Sovereign's architecture. The custom request object that ruled other tools out was treated as ordinary. "This was truly like an open infrastructure to Salesforce, however you want to turn it," Nick says. "They could work with any object, any tool, put it in any framework."

The second is cost. Sovereign connects its own OpenAI account, so the model, the token structure and the spend all sit with the firm.

The third is the one that decides whether an adoption problem has really been solved.

For a firm whose growth depends on onboarding advisors, that matters. Each new service line is a configuration rather than a project, which makes the technology easier to take up, "instead of kind of a do-it-yourself environment."

Nick came up through compliance, and he is direct about what has changed in the market and what has not. "You see your AI note takers, and then those are developing even further on the operations side," he says, "tools like Ortoo here using AI behind the scenes to improve and orchestrate better the workflow."

New capability does not lower the bar for a regulated firm. Sovereign set its condition before anything was signed: no AI unless client data could be protected and kept secure, ahead of every other consideration. Nick put that to the Ortoo team in the early conversations. Working sessions with the team covered the secure setup, with a closed environment, model training switched off, and client information staying inside Sovereign's own boundary.

Control over execution mattered as much as control over data. Sovereign put a human in the loop, and kept the loop small. The review step only runs when something is missing. A complete email creates the request directly: no follow-up to send, so nothing to review. Where information is missing, Orchestrator drafts the reply, and selected supervisors check it, edit it if needed, and release it. That component is visible only to them, so it adds no work for anyone else. "We don't just have to trust AI to be right or wrong," as Nick puts it.

AI reads and interprets. Deterministic logic decides what happens next. Every action is recorded. Sovereign audits the AI and the prompts behind it, checking that what the system reads is being interpreted correctly. That discipline became policy: an internal AI governance protocol that now covers every AI tool the firm adopts, with documented prompts and actions available for regulatory review.

Key outcomes

• 4x as many requests reach Salesforce
• 95% arrive correctly categorised, up from 7%
• More people are submitting requests than before the change
• Request types that were never recorded are now visible on Salesforce

Work that used to sit in chat threads and phone calls is now a record, with a type, an owner and a history. Managers can see what is in flight and where it stalls.

Adoption is the clearest change, and it did not move in a straight line. When Sovereign added structure on its own, fewer people submitted requests, not more. Automated email intake and orchestration reversed that, and took participation past where it started.

Advisor satisfaction is measured on a six-point scale, chosen deliberately so that nobody can sit in a neutral middle. "We've seen a lot of the satisfaction scores go up from fours and fives now to fives and sixes across our Salesforce environment," Nick says.

The less visible result may matter more. What is recorded can be counted. Before, as Nick puts it "there wasn't a good data set, there wasn't a consistent data set."

That has changed what Sovereign's managers are able to discuss. "We've had a lot more productive conversations around: where do we need to improve these requests? How can we make these requests easier for our advisors?" Nick says.

Sovereign started with the client service team, extended to trading, and is now extending to a general service line. As the firm adds advisors, business lines and products, the same intake orchestration model carries them.

The data the system has produced is what makes the next step possible. "We love data, we love collecting data, and we love creating insights off of data," Nick says. "So with this huge data environment that we've collected, now we can really lean into AI."

The assumption underneath has not changed: "Users aren't going to stop using email. That's just the nature of life." He is equally clear about the limit. Sovereign is "never going to take out the personal side, especially around advice."

Nick's advice to peers running Salesforce starts from the same observation the project did. Advisors like their emails, and they send requests there. So the question worth asking is what happens to those emails, not how to get people to stop sending them.