We are opening
Personal identifiable information (PII) anonymization on a request basis for
Enterprise and
Ultimate editions. Kindly raise a request using the
Early Access Form.
While customer support teams increasingly rely on AI-powered capabilities to improve response quality and efficiency, it is equally important to make sure that sensitive information is protected at every stage of data processing. Organizations expect strong privacy controls when their data is shared through Generative AI models.
Personal identifiable information anonymization is designed to ensure that Personally Identifiable Information (PII) is masked before any data leaves Zoho Desk and is sent to the AI models, so that the organizations adopt AI confidently, without compromising on compliance, security, or customer trust.
Availability
Permission Required
Only users with Support Administrative Profile Permission can configure PII anonymization for the departments they have access to.
Some common scenarios where PII anonymization becomes essential are:
- Protecting sensitive customer data - Banks, insurance companies, and healthcare providers often handle sensitive information like account numbers, folio numbers, health records, and personal details. Masking this information ensures that sensitive data is not exposed when AI features are used.
- Using AI in privacy-focused organizations - Some organizations are wary about using Generative AI models due to concerns about data security. By masking personal information before it is shared with AI models, businesses can safely use AI features without risking data exposure or violating internal security policies.
- Departments level privacy needs - Not all departments handle the same type of data. For example, a finance team may work with more sensitive information than a customer onboarding team. PII anonymization allow organizations to apply different masking rules for each department based on their needs.
Business Scenarios
Healthcare organizations handle sensitive patient information, including personal identities, medical records, and insurance details.
Anonymizing PII before sharing ticket content with AI helps prevent the exposure of patient identities and confidential health information during AI-powered ticket summarization, sentiment analysis, classification, and response generation. This allows AI to understand the patient's issue and assist support representatives without accessing identifiable patient information.
Financial institutions handle sensitive customer and payment information, including credit card details, banking credentials, transaction records, and cryptocurrency wallet addresses.
Anonymizing PII before sharing ticket content with AI helps prevent the exposure of customers' financial information during AI-powered payment dispute analysis, ticket summarization, classification, and response generation. This allows AI to understand and process financial complaints without accessing confidential payment credentials or identifiable banking information.
E-commerce and document delivery organizations handle sensitive customer information, including personal identities, contact details, government-issued identification numbers, and visa application documents.
Anonymizing PII before sharing ticket content with AI helps prevent the exposure of customer identities and confidential travel documents during AI-powered ticket summarization, delivery issue analysis, classification, and response generation. This allows AI to understand delivery-related complaints and assist support representatives without accessing identifiable customer information.
Understanding PII anonymization
PII anonymization works by identifying and masking PII before data is sent from Zoho Desk to any AI model. After the AI model generates a response, the masked values are re-identified within Zoho Desk to retain the context for agents.
The system automatically detects and masks PII based on predefined categories.
Commonly used fields that can be categorized as PII and masked:
Data type | Components |
Personal | - Person Name
- Date of Birth
- Username
- Social Media Handle
- Passport Number
- Passport Expiration Date
- Visa Number
- Identity Card Number
- Identity Document Number
- National ID Number
- Driver’s Licence Number
- Birth Certificate Number
- Student ID Number
- Registration Number
|
|
Contact | - Phone Number
- Mobile Phone Number
- Landline Phone Number
- Fax Number
- Email
- Email Address
- Address
- Postal Code
- IP Address
|
|
Financial | - Credit Card Number
- Due or Expiration Date
- Credit Card Brand
- CVV
- CVC
- Bank Account Number
- Iban
- Transaction Number
- Folio Number
|
|
Health and Sensitive | - Medical Condition
- Medication
- Blood Type
- Health Insurance Id Number
- Health Insurance Number
- Insurance Number
- National Health Insurance Number
|
Business and regulatory | - Organization
- Insurance Company
- CPF
- CNPJ
- Tax Identification Number
- Social Security Number
- Flight Number
- Train Ticket Number
- Reservation Number
- Licence Plate Number
- Vehicle Registration Number
- Serial Number
- Digital Signature
|
These categories collectively cover a wide range of commonly used PII values.
Points to Remember
- PII masking is only supported for the English language data.
- PII is masked before data is sent to AI models and re-identified after the response is received.
- Masking helps preserve conversational context, but generation quality may be slightly impacted.
- PII masking applies only to AI interactions and does not alter ticket data stored in Zoho Desk.
- Configuration can vary across departments based on business requirements.
Enabling PII anonymization
Admins can select and mask specific categories or all categories based on departmental needs.
To enable PII anonymization
- Navigate to Setup > Privacy and Security > PII anonymization.
- Enable Configure PII for Anonymization.
- Under Configurations, add Departments for which PII masking should be applied.
- Click Save.
PII identification and masking for multiple departments
For organizations with multiple departments, admins can use the mass update option to apply the same PII masking configuration across departments at once by selecting the relevant departments and clicking Update Configuration.
To configure departments for PII anonymization
- Navigate to Setup > Privacy and Security > PII anonymization.
- Click Configure.
- Select the desired department.
- Click Save.
- Click Update Configuration.
- Select an entire Data type or specific components under a data type.
- Click Add PII.
To remove a department from PII anonymization
- Navigate to Setup > Privacy and Security > PII anonymization.
- Click Configure.
- Select the desired department.
- Click Remove Departments.
- Click Remove in the Remove Department Configurations alert.
Testing PII masking using playground
Before rolling out the configuration, admins can test how PII masking works using the Playground. Ensure that PII anonymization is configured and saved for at least one department before testing.
To work in the PII Playground
- In the PII anonymization configuration page, click Playground next to the configuration.
- Select the department for which PII masking has been enabled.
- Enter sample content in the Redaction field, or click Select Ticket to choose an existing ticket.
- Click Test to view the masked output and verify how PII is redacted before being sent to the AI model.