Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.statisfy.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Connect Attention with Statisfy

The Attention integration pulls call conversations and transcripts from your Attention workspace into Statisfy. Conversations are matched to the right customer account by attendees and surface alongside the rest of the activity timeline. Prerequisites:
  • Admin access to both Attention and Statisfy
  • An Attention API key
  • A connected CRM (Salesforce or HubSpot) — non-CRM integrations are gated until at least one CRM sync has completed

​
What Gets Synced

Data TypeDescription
ConversationsCalls recorded in Attention with metadata
TranscriptsSpeaker-tagged transcripts from Attention
AttendeesMeeting participants (internal and external)
AI InsightsSummaries and notes Attention generates for each conversation

​
Generate an Attention API Key

  1. Sign in to Attention as a workspace admin.
  2. Open your workspace settings and create a new API key. Refer to Attention’s API documentation for the latest steps.
  3. Copy the key — you’ll provide it to Statisfy in the next step.
Keep the key secure. An Attention API key can read every conversation the issuing workspace has access to.

​
Steps to Connect with Statisfy

  1. Log in to Statisfy.
  2. Navigate to Integrations → Attention → Connect and paste your API key. Credentials are stored encrypted in Google Cloud Secret Manager.
  3. Once connected, the bootstrap job runs a one-time historical backfill. Conversations and transcripts flow into Statisfy.
  4. The periodic sync runs on a recurring schedule with a short lookback window so updates to recent conversations are picked up.
  5. Find synced conversations on each Account under AI Timeline → Source: Attention, or in the global Activities view filtered by source.

​
Sync Behavior

Time-bounded pulls:
  • Conversations are fetched in pages from the Attention API using a date range.
  • Each periodic run looks at the last couple of days so updates to recent conversations are caught.
Owner and attendee resolution:
  • Statisfy classifies internal vs. external attendees by email domain.
  • Speaker labels in the transcript are passed through as-is from Attention.
Error Handling:
  • If Attention returns HTTP 401, the credential is automatically marked invalid in Statisfy — reconnect with a fresh key.
  • Non-200 responses raise an error so the run is retried on the next schedule.

​
Troubleshooting

  • Verify the API key has not been rotated or revoked in Attention.
  • If Statisfy detects an HTTP 401, the credential is automatically marked invalid — reconnect with a fresh key.
  • Ensure your CRM integration (Salesforce or HubSpot) has completed at least one successful sync. Until then, Attention periodic jobs are skipped.
  • Confirm the call’s external attendees match an existing account by email domain or CRM linkage.
  • Very recent calls may not yet have a finalized transcript in Attention; they’ll appear on a later run.
  • Statisfy deduplicates by conversation ID within a run. If you also have another meeting source (e.g., Gong, Zoom) connected, the same call could surface from multiple sources. Filter by Source in the Activities view to see where each entry came from.

​
Need Help?

If you face any challenges with the Attention integration, please contact support@statisfy.com. Our team will assist you.