A health insurance startup, a wealth management firm, and a public consumer finance company faced different versions of the same problem: exchanging sensitive information securely added friction for customers and extra work for staff. These Secure Message Center use cases show how DataMotion helped simplify secure exchange within the portals and systems organizations already used.
In regulated industries, protecting sensitive information is essential. The challenge is doing so without making customers navigate unfamiliar portals or forcing staff through disconnected systems. If you are deciding whether secure messaging belongs in your self-service experience, consider the signs that a portal may need a more connected approach to secure communication.
Here is what changed for each organization after implementing Secure Message Center:
- Health insurance: A nine-step exchange became three. Customers submitted information through an existing portal, and authorized agents could pick up where a colleague left off.
- Wealth management: Clients used familiar credentials to access secure communications, while clients and advisors gained the ability to exchange larger files.
- Consumer finance: Secure exchange connected more than a dozen departments without requiring the company to replace its existing infrastructure.
Different businesses and different obstacles, but a shared goal: make secure communication part of getting the work done, not another hurdle along the way.
Health Insurance: Ensuring an Optimal Customer Experience
A health insurance startup had compliance-related and internal-efficiency challenges that interfered with the customer experience. The need to exchange personally identifiable information and protected health information securely added steps for both staff and customers.
Consider a policyholder who calls with a question about coverage. The customer-service representative needs a prescription image or other sensitive information to review eligibility and records. In the previous process, the representative had to move outside the call-center workflow to initiate a secure exchange.
Nine Steps, Then Three
Before: a separate encrypted-email portal
- The representative leaves the call-center application.
- The representative opens Outlook.
- The representative sends an encrypted email through a separate system. In this workflow, entering “Secure” in the subject line triggered encryption.
- The customer receives an email with a link to a secure portal.
- The customer clicks the link and creates an account.
- The customer sets up a username, password, and registration details.
- The customer logs in to the portal.
- The customer navigates an unfamiliar interface.
- The customer uploads the information, submits it, and logs out.
After: Secure Message Center inside the existing portal
- The customer logs in to the company’s standard portal with credentials already in use.
- The customer uploads the requested information and selects submit.
- The secure exchange is complete.
The prior process required a significant context switch for the representative and an unfamiliar journey for the customer. It also created continuity issues. If the customer called back and the original representative was unavailable, another authorized representative could lack access to the encrypted notes or communication history, forcing the process to restart.
After implementing DataMotion Secure Message Center, the secure message repository enabled authorized representatives to see where the previous representative left off. That can be the difference between a handoff and a restart.
The former process also depended on a manual action: entering a specific word in the email subject line to trigger encryption. In that workflow, a security-related step relied on the representative remembering to take the right action. Embedding secure exchange into the portal removed that step from the representative’s workflow.
Outcome Summary
- Challenge: Sensitive-information exchange forced representatives out of the contact-center desktop and pushed customers into a second portal with separate credentials.
- What changed: Secure exchange was embedded in the existing customer portal and supported by a shared secure message repository for authorized representatives.
- Result: Nine combined representative-and-customer steps were reduced to three, with continuity across authorized representative handoffs.
Wealth Management: A Better Secure Communication Experience
A wealth management company was using a traditional secure-exchange solution. Clients were increasingly frustrated by having to log in to a third-party portal rather than the firm’s own customer portal. They cited the extra steps and frequently forgotten usernames and passwords as persistent obstacles.
Why the Firm Did Not Build It Internally
The firm explored new approaches, including redesigning its own secure message and document-exchange functions. It ultimately decided that building and maintaining this type of application was outside its core competency. The issue was not only creating a secure communication experience; it was also maintaining the integrations, administrative processes, and customer experience over time.
DataMotion integrated Secure Message Center into the firm’s existing workflow. The firm could support secure communication without asking every client to adopt a completely new destination.
Some clients preferred not to use an unfamiliar portal at all. Others were comfortable using a portal but wanted an easier access process. The firm addressed that need by integrating the portal with its single sign-on environment, enabling clients to use credentials they already used on the firm’s website.
How the Integration Supported the Workflow
- Single sign-on helped avoid issuing a separate set of portal credentials.
- Secure exchange was integrated into the firm’s existing portal and application workflow.
- Clients and advisors could exchange larger files than the firm’s prior process allowed.
Flexibility was essential. Secure Message Center accommodated the firm’s existing workflow while giving the organization room to retire applications it no longer needed. The result was a simpler client experience without requiring the firm to make secure communication software development a permanent internal responsibility.
Outcome Summary
- Challenge: Clients disliked a third-party portal with separate credentials, while an internal rebuild was outside the firm’s core focus.
- What changed: Secure Message Center was integrated into the existing workflow, and the third-party portal was connected to the firm’s single sign-on environment.
- Result: Clients used credentials they already had, while clients and advisors could exchange larger files than before.
For related background on Secure Message Center flexibility, security, and compliance, see Flexibility, Ease, Security and Compliance: Meet DataMotion’s Secure Message Center.
Consumer Finance: Merging Security, Compliance, and Ease
Mergers and acquisitions involve more than a new company name and brand identity. Organizations also need to integrate systems, processes, and customer communication workflows. This consumer-finance use case involved creating a smoother secure communications process for customers and customer-service representatives while accommodating the secure communication needs of more than a dozen departments.
Because sensitive information was involved, customer-service representatives had to obtain permission before responding to certain customer inquiries. If a representative did not already have access to secure messaging, the process could require conversations with the security team and multiple stakeholders to request licenses, secure inbox access, change orders, file-transfer access, and new credentials.
With disconnected systems across departments and numerous approval steps, permission could take up to two weeks. Customers could then wait weeks for a response.
Nobody was happy. Nobody.
For the information-security team, the burden was not simply encryption. It was provisioning, managing access, and establishing a consistent record of secure interactions across disconnected processes. The organization needed a way to connect departments while preserving familiar workflows and supporting secure customer exchange.
DataMotion took a fit-for-purpose approach: integrate secure exchange into existing systems rather than require the organization to dismantle its infrastructure. Staff and customers could continue to work in familiar environments while secure communication became more consistent across departments.
Outcome Summary
- Challenge: After an acquisition, disconnected departmental systems meant a customer-service representative could need multi-team approval to send a single secure message.
- What changed: A fit-for-purpose integration layered secure exchange onto existing systems across more than a dozen departments rather than replacing infrastructure.
- Result: Secure exchange was made more consistent across departments while staff and customers remained in familiar environments.
Secure Portal or Secure Email? The Wrong Question
Read the three stories together and a pattern emerges. The debate is often framed as secure portal versus secure email. Both can be part of a secure communication strategy, but either approach can create unnecessary friction when it becomes a disconnected destination.
A separate portal can mean new credentials, forgotten passwords, help-desk requests, and notification emails that customers may not immediately recognize. In the health-insurance example above, the prior encrypted-email process also depended on a manual subject-line step to trigger encryption. Those are not universal characteristics of every secure portal or secure email workflow. They are examples of why organizations should evaluate the full communication journey, not only the point at which a message is delivered.
The more useful question is whether a customer, employee, or partner has to leave the environment where they are already working or authenticated. When secure exchange is integrated into the portal, application, agent desktop, or workflow they already use, it can reduce separate credentials, avoid unnecessary manual steps, and make the secure channel part of completing the work.
DataMotion can serve as a secure exchange layer connecting the portal, agent experience, underlying systems, and participants in a protected interaction.
The Three Use Cases Side by Side
| Challenge | What Changed | Result | |
|---|---|---|---|
| Health Insurance | Sensitive-information exchange forced representatives out of the desktop and customers into a second portal | Secure exchange embedded in the portal; shared secure message repository for authorized representatives | Nine steps reduced to three; continuity across authorized handoffs |
| Wealth Management | Clients disliked a separate portal login and frequently forgot credentials | Third-party portal connected to the firm’s single sign-on environment; applications retired | Clients used familiar credentials; larger files could be exchanged |
| Consumer Finance | Multi-team approval was needed before a representative could send some secure messages | Fit-for-purpose integration across more than a dozen departments | More consistent secure exchange while staff and customers remained in familiar environments |
Securing a Compliant, Simpler Experience
For organizations in regulated industries, compliance requirements cannot be optional. But secure communication does not have to create unnecessary inefficiency in internal workflows or a difficult experience for customers.
DataMotion Secure Message Center helps organizations support encrypted, auditable, identity-aware exchange of sensitive information between internal and external users while bringing secure interactions closer to the systems and workflows where work happens.
For more information about Secure Message Center and DataMotion’s secure communication solutions, contact the DataMotion team.
Related Secure Message Center Resources
- Flexibility, Ease, Security and Compliance: Meet DataMotion’s Secure Message Center
- Protecting Sensitive Information on the Daily: Meet DataMotion’s Secure Message Center
- Balancing Security, Compliance, and Usability: Your Secure Message Center FAQs
Frequently Asked Questions
How does DataMotion’s Secure Message Center improve customer experience?
Secure Message Center can bring secure exchange closer to an organization’s existing portal and workflow, reducing unnecessary steps for customers and employees. In the health-insurance use case above, an exchange that previously required nine combined customer and representative steps was reduced to three, while authorized representatives retained continuity across the secure interaction.
Can secure messaging fit into a company’s existing workflow?
Yes. DataMotion can support a fit-for-purpose approach in which secure exchange is integrated into the systems and workflows an organization already uses rather than requiring a wholesale replacement of its infrastructure. This article includes examples involving customer portals, single sign-on, customer-service workflows, and multi-department processes.
How can regulated organizations support secure communication without hurting customer experience?
The goal is to make the protected path clear and practical. Secure communication can support customer experience when employees and recipients do not have to navigate unnecessary system changes, duplicate credentials, manual security steps, or disconnected handoffs. Organizations should evaluate the complete workflow, including how an interaction is initiated, accessed, routed, tracked, and continued.
