Skip to main content

Customer Sources

Connect the tools where your customers report issues. Sailfish pulls in reports from these channels and automatically correlates them with the technical context needed to resolve them.

How Issues Flow In

Customer issues reach Sailfish through two paths:

  1. CS platform → Sailfish — A customer reports an issue in your CS tool (Zendesk, Salesforce, Pylon). The report is auto-categorized or manually escalated as a bug. Sailfish matches it to the user's session and correlates the technical context.
  2. In-app Report Issue modal — A user reports an issue directly from your application. Sailfish captures the session, a screenshot, and the full backend/frontend context from that moment.

Supported Sources

SourceStatusSetup
ZendeskAvailableConnect Zendesk →
SalesforceAvailableConnect Salesforce →
PylonAvailableConnect Pylon →
In-App ReportingAvailableSetup guide →

Zendesk

Connect Zendesk to automatically correlate support tickets with Sailfish session data.

Setup

Sailfish Settings > Integrations page with the Zendesk "Connect" button highlighted

  1. Open the Zendesk integration settings in the Sailfish dashboard
  2. Click Connect

That's it — Sailfish handles the rest. Incoming Zendesk tickets are automatically matched to user sessions using the ticket requester's email address.

What You Get

  • Support tickets automatically linked to the user's Sailfish sessions
  • One-click navigation from a ticket to the exact session replay
  • Full technical context (errors, network requests, logs) attached to each ticket

Salesforce

Connect Salesforce to correlate support cases with Sailfish session data.

Setup

Step 1: Connect in Sailfish

Sailfish Settings > Integrations page with the Salesforce "Connect" button highlighted

  1. Open the Salesforce integration settings in the Sailfish dashboard
  2. Click Connect
  3. Authorize access to your Salesforce org

Step 2: Add the Sailfish panel to your Salesforce case view

After connecting, add the Sailfish component to your Salesforce case page layout so agents see session context inline:

  1. Open Salesforce Setup > Object Manager > Case > Lightning Record Pages
  2. Edit your active case page layout in the App Builder
  3. Drag the Sailfish component onto the page
  4. Save and activate the updated layout

Once configured, agents see Sailfish session data directly within the Salesforce case view — no tab switching required.

What You Get

  • Sailfish session context embedded directly in the Salesforce case view
  • Full technical context (errors, network requests, logs) alongside case details
  • One-click navigation from a case to the exact session replay in Sailfish

Pylon

Connect Pylon to capture customer-reported issues and correlate them with session data.

Setup

Step 1: Get a Pylon API key

Pylon Settings > API page showing where to generate an API key

  1. In Pylon, navigate to Settings > API
  2. Generate a new API key
  3. Copy the key — you'll need it in the next step

Step 2: Create a webhook in Sailfish

  1. Open the Pylon integration settings in the Sailfish dashboard
  2. Find Pylon and click Connect
  3. Enter your Pylon API key
  4. Copy the webhook URL that Sailfish generates

Step 3: Set up a trigger in Pylon

  1. In Pylon, navigate to Workflows > Triggers
  2. Create a new trigger for the conversation events you want to send to Sailfish (e.g., new conversations, bug escalations)
  3. Add a Webhook action and paste the Sailfish webhook URL from Step 2
  4. Save and activate the trigger

Once configured, matching Pylon conversations automatically flow into Sailfish and are correlated with user sessions.

What You Get

  • Customer conversations automatically linked to the user's Sailfish sessions
  • Full technical context (errors, network requests, logs) attached to each conversation
  • One-click navigation to the exact session replay

In-App Reporting Widget

The Sailfish in-app reporting widget lets your users report issues directly from your application. When a user submits a report, Sailfish automatically captures:

  • The user's current session and page
  • A screenshot of what they see
  • Their description of the problem
  • Full backend and frontend context from that moment

See In-App Reporting for setup instructions.