Skip to content
New AI Custom Form BuilderDescribe the intake form. It ships branded and end-to-end encrypted.AI Custom Form Builder is here See it build
Customers

Keeping Unwanted PII out of your Service Desk

SendSafely can now be used to shield your ticketing platform from inadvertently collecting and storing unwanted and unsolicited Personally Identifiable Information (PII) submitted by customers.

Brian Holyfield · 5 min read
Keeping Unwanted PII out of your Service Desk

SendSafely can now be used to shield your ticketing platform from inadvertently collecting and storing unwanted and unsolicited Personally Identifiable Information (PII) submitted by customers.

The scenario is all too familiar, an automated identity verification or application process requiring the exchange of sensitive documents breaks down and the frustrated customer reverts to the ease and insecurity of email attachments. The unencrypted files end up in your third party service desk platform, unclassified, available to all agents and stored indefinitely.

Our SendSafely Serverless Email Gateway (SEG) can now intercept and encrypt these inbound email attachments without the need to reject insecure attachments and further frustrate end-users. Combined with one of our native Help Desk apps, SendSafely can provide an end-to-end solution for protecting PII without impacting your agent or customer workflows. Read on for more detail.

The Scenario

The benefit of protecting inbound messages from customers may not be immediately obvious, but consider the following:

Acme Bank uses a third party help desk for managing support tickets and cases. Customers can contact the Acme Bank support team by sending an email tosupport@acmebank.com.

Despite being instructed not to do so, customers frequently send sensitive email attachments that end up being stored as file attachments within the help desk platform. These files are often accessible to all agents with access to the system and frequently are stored for an unlimited amount of time.

SENDING_PII_VIA_EMAIL

The above scenario is extremely common and one that most financial services organizations try to avoid. Most of these organizations are bound by “know your customer” or “know your client“ (KYC) guidelines that require appropriate identity verification of new clients or customers.

Onboarding new customers is a process commonly managed through a ticketing system like Zendesk or Salesforce Service Cloud. Many financial services organizations use these systems because of their configurable process workflows, but they are typically not well suited for storing sensitive files that contain personally identifiable information like copies of a customer’s passport or driver license.

unencrypted_attachment_zendesk

Even if the organization has a designated system for collecting identity verification documents, it can be very difficult to stop customers from using regular email attachments to submit sensitive documents. The ubiquitous nature of email attachments leads many customers to gravitate towards this option since it is typically the easiest method despite the lack of security.

An organization could easily choose to reject these email attachments; however this goes against the current trend of striving to provide the best possible customer experience. Rejecting attachments and forcing users to resubmit using a different mechanism causes friction within the customer experience and leads to frustration.

The Solution

When we originally designed the Serverless Email Gateway (SEG), the intended use case was for transparently protecting outbound email messages sent by our enterprise customers to external recipients. The SEG is able to dynamically intercept attachments that contain sensitive information and protect the attachments using SendSafely before sending them externally.

SEG_POLICY_EVALUATION

Thanks to a recent update, the SEG can now protect both inbound AND outbound attachments.

The SEG can be configured to automatically intercept inbound email messages that are destined for a ticketing system and dynamically protect attachments before they get ingested. The diagram below shows how most third party ticketing systems receive inbound email messages.

EMAIL_FORWARDING_TO_HELPDESK

A designated email alias is configured within the company’s mail server for handling incoming email to the ticketing platform. A forwarding rule on the mail server is defined that forwards these messages to the ticketing system using a private email address that gets routed directly to the third party platform.

With the SEG, the email forwarding rule is modified to detect whether each incoming message has an attachment. Messages without an attachment can be forwarded directly to the ticketing system, but messages with an attachment get routed to the SEG instead. The SEG removes the attachment and uploads an encrypted copy of the attachment to SendSafely.

SEG_PROTECT_INBOUND_TICKETS

A SendSafely link to the attachments is then appended to the top of the original message, which is then forwarded to the ticketing system (without any files attached).

protected_attachment_in_zendesk

For companies that use Zendesk, Salesforce Service Cloud or Freshdesk, agents can access the secured attachments natively using our free apps that run directly in the agent console. Our apps even have a built-in preview modal that allow the agent to view the file contents without navigating away from the ticket.

passport_zendesk_preview_modal

The ability to protect inbound attachments with SendSafely offers many security benefits:


SendSafely: Encrypted File Transfer for Modern Business

If your organization needs a secure way to transfer files with customers or business partners, our platform might be right for you. Contact us today.

Request a Demo

Frequently asked questions

How can I keep customer PII attachments out of my help desk?

Route inbound email with attachments through the SendSafely Serverless Email Gateway. It removes each attachment, uploads an encrypted copy to SendSafely, and forwards the original message to the ticketing system with a SendSafely link instead of the file. See helpdesk security.

Can the SendSafely Serverless Email Gateway encrypt inbound email attachments?

Yes. The SEG was originally built to protect outbound attachments, and a 2020 update added inbound protection. It can intercept messages destined for a ticketing system and protect attachments before they are ingested.

How is email routed to the SEG for a ticketing system?

The mail server’s forwarding rule for the support alias is changed to check for attachments. Messages without attachments go straight to the ticketing system; messages with attachments go to the SEG, which encrypts the files and forwards the message with a secure link.

Why not just reject email attachments that contain sensitive documents?

Rejecting attachments forces customers to resubmit another way, which adds friction and frustration. Encrypting them in transit protects the data without changing the customer’s or agent’s workflow.

What security controls apply to inbound attachments protected by SendSafely?

Files are encrypted and stored separately from the key, which is embedded in the ticket link. SendSafely adds access control independent of ticket access, audit logs of every agent access, view-only download restrictions, and expiration policies that can delete files automatically.

Written by Brian Holyfield