Detected country: US
logo
Open AppStatusSubmit Ticket
GuideAPI References
‌
‌
‌
logo

Powered by

  • Home
  • Security & Compliance
  • Handling PII with External Form Redirects (Zero-Collection Flow)

Handling PII with External Form Redirects (Zero-Collection Flow)

3min read

Share

This guide explains how to configure Brainfish so your AI support agent never intentionally collects Personally Identifiable Information (PII) or sensitive account identifiers (such as email addresses, phone numbers, or order/account IDs), and instead redirects customers to your own external web form or ticketing portal where data is submitted directly to your systems.

1. Detecting When PII Is Needed & Redirecting to an External Form

Supported today via Procedures + URL/Callback CTAs + Agent Custom Instructions.

  • Procedures: Define the scenarios where account-specific or sensitive information is required (for example, order lookups, billing/refund requests, identity verification, or account changes) and instruct the agent to route the user to your external form instead of collecting details in chat.
  • URL CTA Buttons: Inside a Procedure, embed a URL Call-to-Action (CTA) pointing to any https:// URL (opening in a new tab or the same tab).
  • Callback CTAs (Optional): If your form is embedded on your own site (such as a modal or in-app support drawer), you can use a Callback CTA to trigger custom JavaScript on your host page without navigating away.
  • Custom Instructions: Reinforce the routing rule at the agent level so the agent consistently hands off to the Procedure's CTA whenever PII would otherwise be required.

2. Submitting Directly to Your Ticketing or Backend System

Yes, external form submissions bypass Brainfish completely.

  • When a customer clicks a URL CTA, their browser navigates directly to your external https:// form (for example, a Jira Service Management portal, Zendesk/ServiceNow/Salesforce form, or your own custom web form).
  • All fields entered on that form are submitted directly from the customer's browser to your external system. None of that form data passes through Brainfish servers or LLM providers.

Configuration tip: Do not enable Brainfish's built-in Support Form or workflow ask_in_conversation input mappings for PII fields, and do not append PII as URL query parameters on the redirect link.

3. Preventing Brainfish from Asking for PII

  • Instruction-driven control: Preventing the agent from requesting email addresses, order/account IDs, or other PII is configured through Agent Custom Instructions and Procedure wording (for example: "Never ask the user for their email address, order/account ID, or personal information. When account-specific details are needed, immediately present the external support form CTA.").
  • Important limitation: Because this behavior is enforced via LLM instructions and Procedures rather than a deterministic code-level block, it is highly reliable in normal operation, though not a hard technical guarantee.
  • Configuration checklist:
    • Ensure no attached workflow playbooks map PII fields as ask_in_conversation.
    • Keep Brainfish's native Support Form and escalation email prompts disabled on the channel.

4. Handling Customers Who Voluntarily Type PII in Chat

Even when Brainfish does not ask for PII, a customer may still type sensitive information into the chat input unprompted. Here is how Brainfish handles voluntary PII today:

  • Analytics PII Masking: Brainfish automatically masks common PII types (including email addresses, phone numbers, dates of birth, street addresses, credit card numbers, SSNs when prefixed, and IP addresses) when conversations are viewed in Analytics (for example, john@example.com is masked as j***@example.com).

  • Key limitations to note:

    • Masking happens at Analytics read time, not pre-ingress: If a customer voluntarily types PII into chat, that message transits the Brainfish API, is processed by the LLM, and is stored in the conversation database before being masked in Analytics views.
    • Custom identifiers and names are not masked: Company-specific identifiers (such as order IDs, ticket numbers, or account IDs) do not match a standard PII pattern, and personal name redaction is intentionally disabled to avoid false positives on product/help terminology.
  • Recommended mitigations:

    1. Add a short notice in your widget/chat welcome message (e.g., "Please do not enter email addresses, order/account IDs, or personal details in chat").
    2. Add a rule in Custom Instructions: "If a customer volunteers an email address, order/account ID, or other personal details, do not repeat it back; direct them to submit it via the external form."

5. Architecture & Data Flow Diagram

Zero-collection PII flow diagram showing external form redirect and voluntary PII handling

Summary Comparison

ScenarioDoes PII pass through Brainfish?How it is handled
Intended flow (URL / Callback CTA redirect)NoCustomer is redirected to your external form/portal; Brainfish never sees the submission.
Customer volunteers standard PII in chat (email, phone, card, etc.)Yes (in transit, LLM, DB)Masked in Analytics views (j***@example.com); agent instructed not to echo and to redirect.
Customer volunteers custom IDs (order/account ID) or namesYes (in transit, LLM, DB)Not automatically masked; mitigated via widget notice + Custom Instructions redirect.

Share