Skip to main content
Connect Simplesat to bring your customer satisfaction surveys into MSPortal, where the scores sit next to the tickets and technicians that earned them. Responses flow into the same CSAT and NPS reporting MSPortal already uses, so your Simplesat data appears on the CSAT dashboard, in reporting blocks, and in the Service Stats scorecard.
Simplesat is currently a beta integration. If it is not available in Settings > Integrations, contact support@msportal.ai.

​
Prerequisites

  • A Simplesat account with permission to create API keys
  • A Simplesat API key
  • MSPortal.ai integration management permission
  • Your Simplesat customer names, so they can be matched to MSPortal companies

​
Connect Simplesat

1

Create an API key

In Simplesat, open Account Settings and create an API key for MSPortal. Copy it to a secure location.
2

Open the setup wizard

In MSPortal, go to Settings > Integrations, find Simplesat, and click Configure. Setup runs as four steps: Connect, Configure sync, Map companies, and Review.
3

Test the connection

Paste the API key and run the connection test. MSPortal reports how many customers, surveys, and responses your account exposes, so you can confirm the key reaches the data you expect.
4

Save the connection

Once the test succeeds, click Save connection. MSPortal stores the key in Vault and does not display it again.

​
Choose What to Sync

The Configure sync step controls which Simplesat data MSPortal pulls. Click Save sync settings after changing the toggle.
Turn Surveys and responses off if you only want Simplesat customers available for company mapping. The background response sync honors the setting and skips its run rather than syncing anyway.

​
Map Companies

The Map companies step matches the company names discovered from Simplesat to companies in MSPortal. Company discovery runs in the background, so new names may take a few minutes to appear. Use Quick match to propose matches automatically. It reads your full Simplesat customer list against your full MSPortal company list, so large tenants do not lose valid matches. Review the proposals, adjust anything it got wrong, and save.
Saving a mapping also attaches responses that already synced under that name, so history is not stranded on an unmapped company. You do not need to re-sync after mapping.

​
Review Sync Status

The Review step is the health check for the connection. It reports: The step also calls out the connection’s overall state: a sync in progress, a sync that needs attention with the latest error, incomplete company mapping with a count of what is left, or confirmation that everything is mapped and up to date. From here you can jump straight to the CSAT dashboard or to CSAT display settings to control how much satisfaction detail appears around MSPortal.

​
Where Simplesat Data Appears

Once responses are syncing, Simplesat scores show up wherever CSAT and NPS already do:

CSAT dashboard

Scores, trends, and verbatim feedback at Surveys > CSAT

Service Stats

Per-technician CSAT alongside tickets and SLA at User Statistics > Service Stats

Client Health

Satisfaction as a scored component of each client’s health

Reporting blocks

CSAT overview, trend, by-company, and recent-feedback blocks on any report

​
Scores attach to technicians

Simplesat lists the team members on each response. MSPortal attributes a response to its technician by email address, which is what puts a real CSAT figure next to that person’s tickets, resolution time, and SLA attainment on User Statistics > Service Stats.
A technician’s Simplesat email must match their PSA email for the response to land on the right person. Responses whose technician cannot be matched still count toward company and tenant CSAT.

​
Run a Sync on Demand

  • Click Sync now in the wizard to run company discovery and, when response sync is enabled, the survey, question, and response sync.
  • Click Refresh on the Simplesat card in Settings > Integrations to do the same from outside the wizard.
Both run in the background. The Review step updates on its own as the sync progresses.

​
Managing the Connection

  • Reopen the wizard to replace the API key or change the sync toggle. An unchanged key saves without re-testing.
  • Disconnecting Simplesat removes the integration, its Vault credential, the synced Simplesat data, and the company mappings. This cannot be undone, and it does not remove anything from Simplesat itself.

​
Troubleshooting

​
Best Practices

  • Map every discovered company before you rely on client-facing CSAT reporting, so no responses sit without a company.
  • Keep technician email addresses consistent between Simplesat and your PSA so Service Stats attributes scores correctly.
  • Check the Review step after the first full sync, then use the mapped count as your ongoing coverage signal.
  • Use CSAT display settings to decide how much satisfaction detail client users see before you share reports.

Surveys

Build MSPortal’s own CSAT and NPS campaigns

MSP Tools

Where User Statistics and Service Stats live

Integrations

Connect and manage every MSPortal integration

Reporting

Add CSAT blocks to client reports