Fichaloto

Tickets and support

Ticketing that lives next to your projects and your hours

What somebody asked for and what broke, with the conversation beside it, without leaving the place where the client, the project and the hours already are. The stuff that does not fit in a loose email and must not be lost.

The problem is not a missing helpdesk. It is that the helpdesk is somewhere else.

Most small companies run incidents out of a shared mailbox, and the ones who have moved on have a separate ticketing tool with its own users, its own client list and its own idea of who is who. Two systems that do not talk.

You notice the day somebody asks how many hours went into looking after a client: the time is in one place, the tickets in another, and nobody joins them up. In Fichaloto the ticket lives where the client, the legal entity, the project and the people already live, so that question is a report rather than an afternoon of spreadsheets.

A ticket is not a task, which is why it sits apart

A task is put there by whoever plans, lives inside a project, and is part of a plan. A ticket is opened by whoever has the problem, may have no project at all, and stands on its own. Putting both in the same list forces the plan to fill up with things nobody planned.

So Support is its own block in the menu — day work, not settings. A ticket can still point at its project when it has one, which is what lets you join the two later.

Your statuses, not ours

The board columns come from a catalogue you own: rename them, recolour them, reorder them, add the ones you need. The only thing the code looks at is which behaviour each status declares, and there are five:

  • New — just opened, nobody has looked at it. This is the number you check on a Monday.
  • Open — someone is on it. You can have three different statuses with this behaviour if that is how your team works.
  • Waiting — parked on somebody outside. The response clock stops here, which is what makes the SLA figure honest instead of an excuse.
  • Resolved — done, pending confirmation from whoever asked. Still counts as open: closing what the customer has not seen is how support statistics get faked.
  • Closed — accepted, or dropped with the reason written down. It does not reopen; you open a new one, and each ticket's history stays readable.

You decide who gets emailed, on every single update

This is the part that decides whether a ticketing tool gets used or abandoned. On every comment and every status change, the ticket itself asks whether to notify, and who. Participants come pre-ticked; you untick whoever does not need bothering.

The usual alternative — notify everyone, always — ends in a mail rule that files tickets into a folder nobody opens. The other one — never notify — ends in tickets dying of silence. Asking each time costs one click and avoids both.

Every email sent is recorded with recipient, time and body. That is what settles «I never got that».

Response targets by type, not one blanket promise

Each ticket type carries its own response target: a critical incident is not answered on the same clock as a question, and promising one figure for everything means promising the shortest and missing it. A type with zero hours is, explicitly, a type with no date commitment.

Anything past its date is flagged in the list and on the board, and can reach you by email on Monday with the rest of the weekly summary.

Who sees what, with no surprises

Without the permission to read tickets, a person is not shut out: they see their own — the ones they open, the ones they own and the ones they are pulled into. That is their job, not a privilege. Seeing everyone else's is what the permission is for.

And speaking in the thread, pulling people in, and sending the notification email are three separate permissions: you can have a director following an incident without letting them post, and a team that comments without being able to drag half the company into the thread.

Frequently asked questions

Can tickets be opened from outside, by email or API?

By API, yes: tickets, comments and participants are entities like any other, with the same verbs, so a form on your site or your CRM can open them. Email intake is not there yet, and we would rather say so than imply otherwise.

Do tickets track time?

Hours go against the project, which is where they are compared with the estimate and with what is billable. What you can do is run a report across both, because the ticket points at its project and its client.

Can a ticket be deleted?

One with no conversation, yes. One with comments, no: you move it to a closed status and write why. What was said is usually the only thing that explains a decision six months later.

What does the ticketing cost?

Nothing extra: it comes with the platform, like everything else. And there is no per-agent or per-ticket pricing: anyone with permission uses it, whether that is three people or the whole company.

Getting started

Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.

What we have written about this

Keep reading