florentin
Start free
ProductBillingCredits & balancesMeteringCheckoutCustomer portalSupport & ticketingAuth & accountsAPI keys & accessTeams & rolesFeature flagsWebhooks & eventsAnalyticsAI-first / MCPStripe integrationMulti-tenant & white-labelTax & currenciesSecurity & fraudImport & migration
SolutionsAI builders & APIsSaaSTools & automationsAgenciesStartupsEnterpriseMonetize an APIUsage-based billingPrepaid creditsSubscriptions & plansOutsource the portalLaunch a partner program
DevelopersQuickstartProvider docsCustomer docsAPI reference (Scalar)Webhooks & eventsAuth, errors, idempotencyMCP / AI agentStatusChangelog
Pricing
Start freeSign in
Home · Produkt · Support & ticketing
Module

Your helpdesk — built in, not bolted on.

A complete ticketing system inside Florentin: a support portal for your customers, an agent inbox for your team and AI drafts from your knowledge base — under your brand, right where customers, plans and credits already live.

Start free →Docs
The problem

You don't want to build this yourself.

A second tool like Zendesk or Intercom charges per seat and still doesn't know your customers — subscription, balance and plan live elsewhere. Florentin's ticketing runs in the same system: every case carries the customer context, the AI answers only from your knowledge base, and your agent can triage via MCP.

  • Build a helpdesk yourself — inbox, status, email threading, attachments
  • Pay per seat for a tool that doesn't know your customers & plans
  • AI replies that hallucinate instead of drawing from your knowledge
Features

What Support & ticketing does

✓
Customer support portalCustomers open & track tickets, attach files, reopen.
✓
Agent inboxViews, assignment, status, priority, tags, internal notes.
✓
AI drafts (KB-grounded)Off · draft · auto — strictly from your knowledge base, never invented.
✓
Reply guardChecks tone, spelling and your rules before sending.
✓
CSAT & feedback1–5 rating after resolution, thumbs on AI replies.
✓
Portal & email channelInbound emails become tickets; replies by email with threading.
How it works

In three steps

Customer reaches out

Via the support portal or by email — both become a ticket.

AI drafts from your knowledge

Florentin proposes a reply — only from your knowledge base, with confidence.

Agent approves

The guard checks tone & rules, your agent sends in one click; CSAT comes back.

In detail

Specifications

Kanäleportal · email · API · MCP
KI-Modioff · draft · auto (confidence threshold)
KI-Quelleyour knowledge base only — no invented answers
Statusopen · in progress · waiting · resolved · closed
Anhängeup to 5 files · 10 MB · PNG/JPG/PDF/CSV/ZIP
ZufriedenheitCSAT 1–5 · feedback on AI replies
Verwaltunginbox · REST API · MCP tools
Example

A customer emails at 11pm. Florentin drafts a reply from your knowledge base, the guard checks tone and spelling. In the morning your agent approves it in one click — status resolved, CSAT request sent, all in the same system as subscriptions and credits.

FAQ

Frequently asked

Does this replace Zendesk or Intercom?
For many teams yes — and unlike a third-party tool it knows your customers, plans and credits without any sync.
Does the AI invent answers?
No. It answers only from your knowledge base; with no source it proposes nothing. You choose between off, draft and auto.
Do I need the AI?
No, it's optional. Without AI you have a full ticketing system; with AI you get drafts or auto-replies — with your own or our model key.
Can contacts without an account have tickets?
Yes — contact-only tickets (email only) and internal team-only tickets are supported.
Related

Related modules

01Customer portalYour customers manage themselves.→02AI-first / MCPGive your agent the Florentin MCP.→03Webhooks & eventsFlorentin events into any tool or automation.→

Build your product. We'll handle the rest.

All integrated — auth, billing, credits, portal, access. Stripe fully included.

Start free →