Feedback Scopable reads
Surveys, questions, customers, responses, and answers used to calculate mapped client CSAT and NPS context.
Live customer feedback integration
SimpleSAT feedback in the client record.
Scopable connects to SimpleSAT so mapped client dashboards can show CSAT and NPS beside the account context used for reviews, planning, and follow-up.
Built for MSP teams that already collect feedback in SimpleSAT and need satisfaction signals attached to the correct client before a QBR or account review.
Exact supported scope
Read feedback without changing the source.
The integration reads five SimpleSAT surfaces and keeps the provider as the feedback source of truth. The setup guide documents every click and permission.
Read-only boundary
Scopable does not send surveys, update SimpleSAT customers, or write changes back to feedback records.
Credential handling
The key is tested first, stored in the tenant's secure vault, and represented in the app only by a redacted hint.
Client mapping
A confirmed mapping connects a SimpleSAT customer to the correct Scopable client before dashboard metrics appear.
Product state checked 2026-09-01. Docs source last updated 2026-09-01. Anything broader should be treated as unverified until it appears in the setup guide or product release notes.
Data-flow proof
From a response to mapped client context.
Connection and mapping are separate checks. That boundary prevents an API key from silently attaching one customer's feedback to the wrong client.
Create a scoped key
Create one SimpleSAT key for Scopable with read access to responses, answers, customers, surveys, and questions.
Test and save
Paste the key in Scopable, run all five read checks, and save only after the provider accepts every scope.
Sync feedback
Scopable ingests the provider records needed to interpret responses and maintain source freshness.
Confirm the client
Review the SimpleSAT customer in Mappings and confirm the correct Scopable client when an automatic match is not certain.
Use the account signal
Review mapped CSAT and NPS context on the client dashboard before planning follow-up or an account review.
Limits
This is a read-only feedback connection.
The integration is read-only. Survey delivery, customer updates, and feedback write-back remain in SimpleSAT.
A connected key does not attach feedback to a client until the SimpleSAT customer mapping is confirmed.
No synced responses is shown as no data, not as a zero score.
A stale or failed sync remains visible so an old score is not presented as current feedback.
Security review
What the technical validator should check.
Customer feedback can include sensitive comments. Scopable keeps credentials and raw provider payloads out of the browser-facing setup state.
- Create a dedicated key for Scopable so it can be rotated independently.
- Prefer Custom permissions with the five required read scopes instead of Full access.
- Keep the one-time API secret out of tickets, docs, chats, and screenshots.
- Confirm the connection test reports all five read checks before saving.
- Review the customer mapping before relying on feedback in a client meeting.
Buying path
Decide here, configure in the setup guide.
Use this page to validate fit and limits. Use the docs when an admin is ready to create the key and confirm client mappings.
SimpleSAT setup guide
Use this for screenshots, API key permissions, connection testing, mapping, rotation, and troubleshooting.
Read the setup guideSimpleSAT launch note
See the shipped scope, the read-only boundary, and the first proof to complete after connection.
Read the launch noteIntegrations hub
See where customer feedback fits beside PSA, Microsoft, distributor, RMM, and documentation sources.
See all integrationsvCIO software
See how client context supports QBR preparation, roadmap decisions, and follow-up work.
See the vCIO workflowSimpleSAT questions
What SimpleSAT data does Scopable read?
Scopable reads surveys, questions, customers, responses, and answers. It uses those records to calculate mapped client CSAT and NPS context.
Does Scopable write data back to SimpleSAT?
No. The SimpleSAT integration is read-only. It does not send surveys, update customers, or change feedback in SimpleSAT.
Which SimpleSAT API key permissions are required?
Use a custom key with read access to responses, answers, customers, surveys, and questions. A full-access key also works but grants more access than Scopable needs.
Why does a connected account show no client feedback?
The feedback must be synced and the SimpleSAT customer must be mapped to the correct Scopable client. A connected key alone does not attach responses to a client.
How is the SimpleSAT API key stored?
Scopable tests the key before saving it in the tenant's secure vault. The browser receives only a redacted key hint and connection status after setup.
Connect one feedback source to one real client.
The first proof should show a successful read-scope test, a confirmed customer mapping, and the expected CSAT or NPS context on that client's dashboard.