Funnalized
DEENTell me when it starts
Module 18 · Help & support

Help without searching your mailbox

Raise your issue, follow it as a live chat, see the status at any time — no email ping-pong, no second sign-in.

0Capabilities
0Paths through
0Handovers
0Entries in the catalogue

Screens from a demo workspace. Companies, people and figures are fictitious.

What it does

Help & support at work

Four capabilities people actually open Support for. Everything else it can do is listed in full in section 04 — this is only what stands on its own.

The load-bearing capability

A ticket in seconds, with a fixed number

Subject, category, priority — nothing more is needed. Every ticket immediately gets a fixed, sequential number — SUP-2026-0042, for instance — that you and we both refer to, and your description becomes the first message in the chat straight away. No new account, no external portal, no signing in elsewhere.

SUP-2026-0042

a fixed, consecutive number that you and we both refer to

The thread as a live chat

Question and answer run as a chat inside the ticket, with attachments for screenshots and files. You even see when somebody from the team is typing. Everything about one issue stays in one place — nothing trickles away into scattered email threads.

Typing now

visible in real time, all in one place instead of scattered email threads

Nothing goes under

New replies are marked as unread immediately — with a counter right in the sidebar. Tickets that have just moved rise up the list, so you know at a glance which issue is waiting for you — right in the app, without switching to your email.

Marked at once

new replies with a counter in the sidebar, freshly moved tickets at the top

Status always visible

Back to open

reply to a waiting ticket and it jumps back on its own

Open, in progress, waiting for a reply, resolved, closed: you see at any time what it is waiting on and whose move it is. If you reply to a waiting ticket, it jumps back to “open” automatically — nothing is accidentally left lying.

Interplay

Paths that run through here

A ticket hangs off the workspace it came from — with version, module and record. That is why nobody has to describe where they were.

Handovers

What Help & support receives and passes on

Comes in to Help & support
Help & support
Goes out of Help & support

Support deals with what does not work. What is missing and should be built belongs in the idea board.

Complete

Everything that is in it

0Entries in the catalogue

16 capabilities in 3 groups — complete, not curated.

Honestly

What it does not do

Every limit names the place where it happens instead.

  • No phone support.

    Everything runs through the ticket with a fixed number and visible status. A phone call leaves no history the next person can read.

  • No email chain as support.

    An email to support@funnalized.app reaches us — for instance when you cannot get into the app. It gets solved in the ticket, where attachments, history and ownership do not get lost.

  • We do not look in covertly.

    We look in for your ticket; anything beyond that we ask for, and you grant it for a limited time. Without a ticket and without your approval only in an emergency when you cannot be reached — with a stated reason, for no more than 90 days, and we inform you straight away. Every access is in the audit trail.

Follow-up

What teams want to know beforehand

How fast do I get an answer?

You choose the priority when you create it, and the status is visible at any time — instead of a promise nobody can verify.

Can I reopen a closed ticket?

Yes. If it was not solved, it was not solved — reopening hangs off the same history, not off a new ticket.

Does support look into my workspace?

To work on your ticket, yes — and create or correct things there if needed. Every access is recorded in the ticket history, ends with the ticket, and you can end it earlier at any time. On request you get a report of everything that was discussed and done. Anything beyond that we ask for, and you decide whether at all, and with which of your own roles. The one exception is an emergency without a ticket when you cannot be reached: then only with a stated reason, for no more than 90 days, and we inform you straight away.

All 16 entries as a list

Why not email support? 5

  • A ticket in seconds, with a fixed number Subject, category, priority — nothing more is needed. Every ticket immediately gets a fixed, sequential number — SUP-2026-0042, for instance — that you and we both refer to, and your description becomes the first message in the chat straight away. No new account, no external portal, no signing in elsewhere.
  • Categories and priorities Classify your issue — bug, feature wish, question, integration, billing or other — and mark how urgent it is: from low to urgent. That way it reaches the right people faster and in the right order.
  • One fixed thread per issue instead of a frayed email chain
  • A status instead of guessing whether somebody is already on it
  • Nothing goes under in an overflowing inbox

From question to solution 4

  • The thread as a live chat Question and answer run as a chat inside the ticket, with attachments for screenshots and files. You even see when somebody from the team is typing. Everything about one issue stays in one place — nothing trickles away into scattered email threads.
  • Status always visible Open, in progress, waiting for a reply, resolved, closed: you see at any time what it is waiting on and whose move it is. If you reply to a waiting ticket, it jumps back to “open” automatically — nothing is accidentally left lying.
  • Rate and reopen Once a ticket is resolved you can briefly rate how satisfied you were. And if it turns out that not everything was settled after all, you reopen it with one click — the thread does not break. If your request settled itself or the ticket was opened by mistake, you can close it yourself; any running support access to your workspace ends at once.
  • Below the chat sits the access report: when somebody from our team was in your workspace and what they changed there — the same content as the downloadable report (HTML or PDF), without internal notes. If somebody still has access for your ticket, you end it right there yourself

Keeping an overview 7

  • Filter by status, category and priority Three filters, and they run on the server. That is why the count above the list counts the whole filtered set and not just what is currently loaded — a list that names a different number than it shows is worse than none.
  • Search across every ticket Search goes to the server as well, not to the page already loaded. It waits a moment instead of firing on every keystroke.
  • Unread counter in the sidebar When support replies, the sidebar counts along straight away, without reloading — until you open the ticket. You never have to check whether something happened.
  • Nothing goes under New replies are marked as unread immediately — with a counter right in the sidebar. Tickets that have just moved rise up the list, so you know at a glance which issue is waiting for you — right in the app, without switching to your email.
  • Sorted by last activity: freshly answered cases sit at the top
  • Load more instead of page numbers — the list grows, the filters stay put
  • The moment a ticket is created, a notice in the app confirms it — with the number and a way back into the ticket
The neighbours

The module before, the module after

All 21 sit in a fixed order — from here it continues in both directions.

Help & support is module 18 of 21 — the same order as in the menu and the footer.

One message at launch. After that you'll find me in the top right of the app.

Help & support is one of 21. You get all of them.

Sign up and you'll hear from us the moment we go live. Not a newsletter — one message.

€50€150/ month · permanently

Waiting list

Only your email address. No spam, unsubscribe at any time.

See all modules

€50€150/ month · permanently

50 founder placesTell me when it starts