Simplesat
Simplesat captures customer feedback and CSAT scores through surveys, integrating directly with helpdesk systems for real-time performance insights
Verdict
Common use cases
- Log new customers after sales calls
- Sync team member details from HR updates
- Update customer info before sending surveys
- Onboard support agents to satisfaction tracking
- Refresh contact records during account reviews
Integration
- Vendor
- Simplesat
- Category
- crm
- Auth
- API_KEY
- Tools
- 2
- Composio slug
simplesat
Tools
- Create or Update Customer
This tool creates or updates a customer in simplesat. if a customer with the provided email address already exists, their information is updated; otherwise, a new customer is created.
- Create or Update Team Member
This tool creates a new team member or updates an existing one if a team member with the same email address is found. it is an independent action that requires only basic team member information (email, first name, last name, and optionally
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations page. 2. Find Simplesat in the MCP directory and click Connect. 3. You'll be prompted to enter your Simplesat API key — retrieve this from your Simplesat account under Settings > API. 4. Paste the key into Switchy and click Authorize; Switchy confirms the connection with a green checkmark. 5. Open any Space and type '@Simplesat' to see available tools in the autocomplete menu. 6. Test the connection by running '@Simplesat create a customer with email test@example.com and name Test User' — if Simplesat responds with a customer ID, you're live. 7. From now on, any team member in that Space can @mention Simplesat to create or update customer and team member records on the fly.
What teammates see: by default, memories from Simplesat are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Add New Customer
@Simplesat create a customer with email jordan@acmecorp.com, name Jordan Lee, and company Acme Corp.Open in a Space →
Update Customer Details
@Simplesat update the customer with email jordan@acmecorp.com to reflect their new company name Acme Industries.Open in a Space →
Onboard Team Member
@Simplesat create a team member with email alex@ourcompany.com and name Alex Martinez.Open in a Space →
Sync Team Member Info
@Simplesat update the team member with email alex@ourcompany.com to use the name Alex Rivera.Open in a Space →
Bulk Customer Prep
@Simplesat create customers for the following emails: sam@startup.io, priya@techco.com, and morgan@designstudio.net.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@simplesat create a customer record for jane.doe@acmecorp.com with name Jane Doe and company Acme Corp
Customer created successfully in Simplesat. Jane Doe (jane.doe@acmecorp.com) has been added to your account with company set to Acme Corp. This customer can now receive satisfaction surveys and their responses will appear in your Simplesat dashboard. The customer ID is cus_8x7k2m9p.
This example shows the MCP's upsert behavior: if jane.doe@acmecorp.com already exists, her record updates instead of creating a duplicate. Requires a valid Simplesat API key with customer-write permissions. Useful for syncing CRM contacts into your feedback loop before sending surveys.
@simplesat update team member support@acmecorp.com to have name Support Team and set their role to agent
Team member updated in Simplesat. Support Team (support@acmecorp.com) now has role 'agent' and will appear in survey attribution reports. If this email didn't exist, a new team member record was created. Changes take effect immediately for any new survey sends.
Demonstrates the upsert pattern for team members. Simplesat uses team member records to attribute survey responses to specific agents or departments. If the email is new, this creates a record; if it exists, this updates role and name. No delete operation is exposed by this MCP.
@simplesat I just closed a support ticket for jane.doe@acmecorp.com handled by support@acmecorp.com — ensure both records exist so I can send a CSAT survey
Both records confirmed in Simplesat. Customer Jane Doe (jane.doe@acmecorp.com) and team member Support Team (support@acmecorp.com) are now present in your account. You can proceed with sending a CSAT survey via Simplesat's native survey tools or integrations. Note: this MCP creates/updates contact records but does not trigger survey sends directly.
This synthesis example shows how the AI can reason about prerequisites for a downstream workflow (sending a satisfaction survey). The MCP handles the contact-sync step; actual survey delivery happens in Simplesat's UI or via a separate automation. Useful for ensuring data hygiene before survey campaigns.
Use-case deep-dives
When Simplesat MCP makes sense for small support desks
A 6-person support team closes 40-60 tickets a day in Zendesk and wants every resolved ticket to trigger a CSAT survey in Simplesat without manual export work. The Simplesat MCP handles this if your workflow is create-or-update customer records at ticket close, then fire the survey. The two-tool scope is narrow: you're syncing customer data and team member rosters, not pulling survey responses or analytics back into Switchy. If your team needs to analyze CSAT trends or route follow-ups based on scores, you'll still export from Simplesat's dashboard. This MCP is the right call when your bottleneck is keeping customer records current across systems, not when you need bidirectional survey intelligence. For teams under 10 people with straightforward ticket-to-survey handoffs, the API key setup and limited tool surface keep friction low.
Simplesat MCP for client-facing team turnover
A 12-person agency onboards 3-5 new account managers each quarter and needs their profiles live in Simplesat so client surveys attribute to the right rep. The create-or-update team member tool solves this if your HR system or onboarding checklist can trigger the sync when someone joins. The MCP doesn't pull existing team data or handle offboarding deletions, so you're using it as a one-way write layer during new-hire setup. If your agency has high churn or complex role hierarchies that Simplesat tracks, you'll still need manual cleanup in their UI. This integration wins when your pain is "we forget to add new hires to Simplesat for two weeks" and your team size makes a lightweight API key approach viable. Agencies over 25 people or with multi-brand survey routing should evaluate whether the two-tool limit covers their edge cases before committing.
When solo consultants should skip the Simplesat MCP
A solo consultant or 2-person consultancy finishes 8-12 client projects a year and wants post-project CSAT surveys without paying for a full CRM integration. The Simplesat MCP technically works: you create customer records as projects wrap and Simplesat sends the survey. But the overhead of maintaining an MCP connection, managing API keys, and writing Switchy prompts to trigger the sync is higher than logging into Simplesat once a month and manually adding clients. The two-tool scope also means you can't automate survey reminders or pull scores into a dashboard from Switchy. If you're under 20 surveys a year and don't have a CRM feeding customer data already, the MCP adds complexity without saving meaningful time. Save this integration for teams where customer volume or onboarding frequency makes manual entry a weekly tax.
Frequently asked
What does the Simplesat MCP do in Switchy?
The Simplesat MCP lets your AI agents create and update customer records and team member profiles in your Simplesat account. It's useful for syncing customer data from other tools or automatically adding team members when onboarding. The MCP doesn't fetch survey responses or analytics — it's purely for managing the people in your Simplesat workspace.
Do I need admin access to connect Simplesat?
You need API key access to your Simplesat account. Simplesat uses API key authentication, not OAuth, so whoever connects it must have permission to generate API keys in your Simplesat settings. Typically this requires admin or owner-level access. The key grants full write access to customers and team members, so treat it like a password.
Can the Simplesat MCP send surveys or pull feedback data?
No. This MCP only creates or updates customer and team member records. It can't trigger surveys, fetch survey responses, or access any analytics. If you need to act on feedback data, you'll need to use Simplesat's webhooks or reporting API directly — the MCP doesn't expose those capabilities.
Why use this instead of Simplesat's API directly?
The MCP is faster for ad-hoc tasks where you want an AI agent to handle the logic. Instead of writing code to check if a customer exists and then decide whether to POST or PATCH, you just tell the agent "add this customer" and it figures out the rest. For scheduled bulk imports, the API is still better.
Who on the team should connect the Simplesat MCP?
Whoever owns your customer success or support ops workflows. Since the MCP writes to your customer and team member lists, you want someone who understands your data hygiene rules and won't accidentally overwrite records. One connection works for the whole Switchy workspace — multiple people don't need separate API keys.