ResponZDocs

Integrations

Two integrations are enough to get full value from ResponZ. Intercom is the data source. GitHub is what powers release-to-support correlation.

Intercom

Intercom is the primary and only required integration. ResponZ ingests three categories of data:

  • Conversations — including parts, attachments metadata, tags and assignees.
  • CSAT ratings — used to calibrate the AI quality score against real feedback.
  • Outbound campaigns — surveys, emails and series for the Engagement module.

Scopes requested

ResponZ requests read-only scopes only. Concretely: list and read conversations, list and read contacts (no PII export), read CSAT and team metadata. We do not request write_conversations, write_contacts or any admin scope.

How to connect

  • From Onboarding → Step 1, click Connect Intercom.
  • You are redirected to Intercom for OAuth approval, then back to ResponZ.
  • If your IT policy blocks OAuth, paste an Intercom personal access token instead.

Good to know

Disconnecting from Settings → Connections immediately stops new ingestion. Existing analyses remain available according to your retention setting.

GitHub

GitHub is optional but recommended. It powers release-to-support correlation in the Trends module.

Connect up to 8 repositories. ResponZ detects merges to main, master, prod and production and uses the merge commit metadata (title, PR number, author) to annotate the trends timeline.

Scopes requested

Read access on repository metadata, commits, pull requests and branches. No code is ingested or stored. No write access of any kind.

Coming next

  • Notion — pull your internal docs into the scoring policy so the AI knows your style.
  • Slack — push weekly digests, low-score alerts and churn-risk pings to a channel.
  • Linear & Jira — turn documentation gaps into tickets in one click.

Tip

Need an integration that's not listed? Tell us at hello@responz.io — we ship the most requested ones first.

Next

Glossary

All the vocabulary used across the platform.