storage
A database per tenant
Not a shared column. Your organisation gets its own database, reached over its own subdomain, so a token from one tenant is a miss in another.
Everything an agency runs on
Suporta is a multi-tenant helpdesk with a database per organisation and a subdomain to match. Inside it, the modules were designed together, so a leave day changes sprint capacity and a timelog becomes an invoice line.
confirmation_number
Tickets
Intake that survives contact with a real client
Clients file tickets in their own portal, staff file them from Outlook, and Sentry files them by itself. Everything after that is designed to keep the thread readable six months later.
check_circle SLA priorities and breach alerts
Clients of SLA-enabled companies set the priority at creation; the deadline follows, and a breach check runs every minute.
check_circle Internal and client-visible replies
Discuss the ticket next to the ticket. A reply marked for the client is emailed, with a send status and a resend button when it fails.
check_circle Editable replies with an audit trail
Authors can fix their own reply, forever, and every reader sees the edited label. Admins cannot edit yours.
check_circle Company-scoped mentions
Mention your team or the client users of that ticket's company. A client can never enumerate another company's users.
check_circle Internal priority tags
High, medium and low live separately from the client's SLA priority. Staff set it, clients only see it.
check_circle Sentry becomes a ticket
Issues sync in every fifteen minutes and become tickets, ready to be picked up by an agent automatically.
view_kanban
Sprints and capacity
Planning that knows who is actually available
Capacity in Suporta is not a guess. It is each developer's working days and development hours per day, minus their approved and pending leave, over the exact dates of the sprint.
check_circle Sprint board and story points
Backlog, active, review and done, with points per column and a search across the whole board.
check_circle Real capacity, leave-aware
Per-member development hours per weekday, with full-day leave removing the day and half-day leave removing half.
check_circle Support reservation
Reserve a percentage of the team for ongoing support, so sprint capacity reflects the week you will really have.
check_circle Auto-fill per developer
Fills each developer up to their own budget, on the projects they are allocated to. Uncovered projects never fall through.
check_circle AI reshuffle suggestions
Ask for a redistribution across the team, informed by which tickets are turning negative. Advisory: preview it, then apply.
check_circle Sprint closure that rolls forward
Preview per-developer points before you close, then push the incomplete work to the next sprint or back to the backlog.
timer
Time and billing
Hours that turn into an invoice without a spreadsheet
A timer in the sidebar, a quick-log on the ticket, and a report view built for the conversation you have with your accountant at month end.
check_circle Live timer with a required note
Company, project, ticket, pause and resume, and a description prompt on stop so no entry is a mystery later.
check_circle Two invoice states
A freelancer invoicing their hours to you and you invoicing the client are separate flags. One never silently sets the other.
check_circle Token cost per entry
Log the ad-hoc AI spend that went into the work, right next to the hours it went with.
check_circle Not-yet-billed work list
Filter the report to everything you have not passed on to the client yet. That filter is remembered per user.
check_circle Excel export with totals
Hours and token euros per row, totalled at the bottom, filtered by date and client.
check_circle Per-client AI spend report
Agent token spend grouped per client with a per-project breakdown, priced and marked up for invoicing.
monitoring
Dashboards
A different home screen for each person
A client, a support engineer and an admin do not need the same numbers. So they do not get them.
check_circle Clients see what is waiting on them
Tickets grouped by real status, plus an explicit list of the ones whose last reply came from someone else, and why.
check_circle Support sees their own load
Assigned to me, resolved in the last thirty days with points, a status breakdown and a personal attention list.
check_circle Admins see the team
Open, overdue, unassigned and resolved this month, sprint progress in points, and the latest attention report. Every tile deep-links into a filtered list.
check_circle Attention reports
A daily sweep flags tickets that are long-open, inactive, or trending negative in tone, with the actual tickets listed per bucket.
check_circle Live activity feed
Real-time over websockets, with polling as fallback. Clients see completions only; staff see everything.
check_circle The AI control room
Running agents, the needs-a-human queue, pull requests approved, hours saved, cost per ticket per phase, and merged per month.
workspaces
Everything else
The modules a services business actually needs
Built into the same system, on the same data. Not integrations you have to maintain.
check_circle Projects and multi-company
Projects belong to companies, users are allocated to companies, and clients only ever see their own.
check_circle Notes
A notes editor with sharing, real-time collaboration, autosave with conflict detection, and an offline queue.
check_circle Shared calendar
Internal events plus two-way sync with Microsoft 365 and Google Calendar over webhooks.
check_circle Leave management
Requests, approvals and public holidays, feeding straight into sprint capacity.
check_circle Roles and permissions
Admin, support and client roles with granular permissions on every endpoint.
check_circle Weekly client report
An automatic Friday mail to client users per company: completed, new, updated and still open, bucketed per project.
Connected to what you already run
Each one is a settings page with a status pill, not a support ticket to us.
merge
Bitbucket
Repositories, branches, pull requests and approvals
bug_report
Sentry
Issues become tickets automatically
mail
Microsoft 365
Calendar sync and the Outlook add-in
calendar_month
Google Calendar
Two-way sync over webhooks
forum
Slack
Notifications where the team already talks
groups
Microsoft Teams
The same, for the Microsoft half of the world
cloud
S3 / GCS
Attachments on the storage you already pay for
payments
Mollie
Subscriptions and billing
Boring where it counts
bolt
Real-time by default
Tickets, notes, the activity feed and the agent dashboard all push over websockets, with polling underneath as a fallback.
translate
English and Dutch
The whole interface, the mails, the mobile app, and even the language your agents work and report in.
history
Everything is logged
Ticket activity, agent runs down to the individual tool call, and every claim and status a local agent reports.
admin_panel_settings
Roles that hold at the API
What a client cannot see in the interface, they also cannot request. Restrictions are enforced server-side, not hidden client-side.
workspace_premium
Plans and free trial
Features are gated per plan, and a free trial unlocks everything so you can judge the whole thing.
Put your ticket queue to work
Fourteen days, every feature unlocked, no credit card. Bring your own model, or point it at the Claude Code you already pay for.