Skip to content

Churnkey + Querri

Why customers cancel, from every Churnkey session

Querri reads each Churnkey cancel session, with the offers presented and accepted, survey choice, written feedback and outcome, so retention questions can draw on billing and product data too.

Querri only reads from Churnkey and never changes your records. SOC 2 Type II, HIPAA and ISO 27001:2022 certified, and your data is never used to train a model.

What you can answer

Questions teams ask about their Churnkey data

Which cancellation reasons are growing month over month?

Survey answers sit inside individual sessions, so a trend by reason takes exports and pivot tables. Querri groups sessions by survey choice and month and flags a reason that jumps.

Nightly insights & monitors

How much revenue did saved customers keep paying afterward?

Churnkey records who accepted a discount or pause; what they paid next lives in billing. Querri joins sessions to your billing data by customer so the value of each offer is on one dashboard.

Dashboards

What are customers saying in their written feedback?

Free-text feedback is hard to scan once there are hundreds of sessions. Querri reads it alongside survey choice and outcome and answers questions like 'what do people who cancel anyway mention most?'

AI Chat

What comes over

What Querri reads from Churnkey

Querri copies this data into your Library on a schedule, next to every other system you connect, so one question can draw on all of it.

  • Cancel sessions
  • Offers presented
  • Accepted offers
  • Survey answers
  • Customer feedback
  • Save outcomes
  • Sentiment scores
  • Session totals

Refreshed on your schedule

Each sync reloads the data you picked, daily, weekly or monthly, or whenever you run it by hand.

Read only

Querri reads from Churnkey and never creates, edits or deletes anything there. Every answer runs on Querri's own copy.

Who sees what

Querri's own sharing and row-level access decide who sees which rows, in chat, dashboards, Claude, ChatGPT and the API.

How to connect

Connect Churnkey to Querri

  1. 1

    Ask the Connector Agent

    Say "connect Churnkey" or pick it from the connector catalog.

  2. 2

    Sign in or add your credentials

    Churnkey needs an API key and your App ID. Enter both in the secure form, which the Connector Agent never sees.

  3. 3

    Choose what to bring in

    Pick the data you want and how often it refreshes, then approve the first load.

  4. 4

    Ask your first question

    The data lands in your Library, ready for chat, dashboards and scheduled reports.

FAQ

Churnkey and Querri: common questions

How do I connect Churnkey to Querri?

Connect with a Churnkey API key and your App ID. Once you ask the Connector Agent for Churnkey, both go into the secure form, where they are encrypted and kept out of the agent's sight.

What Churnkey data comes into Querri?

Cancel flow sessions with customer, billing provider, mode, survey choice, feedback, offers presented and accepted, save type, cancel or abort outcome and sentiment scores, plus a total session count.

How often is Churnkey data refreshed?

On the cadence you pick, daily, weekly or monthly, with manual syncs in between when you need them. Each sync replaces the session data with a complete fresh copy from Churnkey.

Can I combine Churnkey with Stripe in Querri?

Yes. Querri also connects to Stripe, and both land in one Library, so cancel sessions can be read next to subscriptions and invoices for the same customer.

Does Querri change anything in Churnkey?

No. Querri only reads from Churnkey. It never creates, edits or deletes records there, and every answer runs on Querri's own copy of the data.

Is my Churnkey data secure in Querri?

Yes. Querri is SOC 2 Type II, HIPAA and ISO 27001:2022 certified, credentials are stored encrypted, and your data is never used to train a model.

Ask your Churnkey data a question today

Connect Churnkey, add the rest of your systems, and get answers your whole team can check.