Skip to content

Use casesSaaS startups

Support that sees the account, the plan and the bug

SaaS tickets are about accounts: billing, access, bugs. Flatdesk shows the customer's plan and payments next to the ticket, sends bugs to Jira, and knows who a signed-in chat user is, at $49 per agent per month, or $39 billed yearly with 100 AI answers per agent included.

Start your 14-day free trialSee pricing
The Flatdesk inbox with open conversations, owners and an AI answered label

What it does for this

  • Plan and payments on the ticket

    The customer's Stripe plan, its status and renewal date, and their latest payments and refunds, beside the ticket. It uses a restricted key.

  • AI actions with limits

    Give the AI actions: refund a payment, cancel a subscription, or call your own endpoint to reset a password or change a plan. You set the limits, and anything over one waits for a person.

  • In-app chat that knows who's writing

    Inside your app, signed-in users skip the form and the ticket shows who they are, verified.

  • Bugs to Jira

    Turn a bug report into a Jira issue from the ticket, with the customer's words and a link back. The ticket shows the issue's status, so you know when it's fixed.

  • HubSpot, Slack and your own tools

    See the customer's HubSpot contact on the ticket, post to Slack when a ticket needs a person, and use the REST API, signed webhooks, Zapier or Make.

  • Claude and Cursor can use it

    Flatdesk is an MCP server. Connect Claude, Cursor or another AI tool with your API key and ask it to find, read, tag, assign or answer tickets.

Where it falls short

If you need these today, another help desk fits better.

  • No SOC 2 or ISO 27001 report yet. The security page lists these first.
  • Email and website chat only. No phone or social channels.
  • No app marketplace. Integrations are the ones listed above plus the API.

Questions

Can the AI refund a Stripe payment?

Yes, if you give the Stripe key write access. You choose the actions and the limits; anything over a limit waits for a person to approve.

Does it verify who is chatting from inside our app?

Yes. When a signed-in user opens the chat widget inside your app, they skip the form and the ticket shows who they are, verified.

Is there an API?

Yes: a REST API for tickets and customers, signed webhooks, and an MCP server for tools like Claude and Cursor. Details are on the developers page.

Keep reading