TickFlowTickFlowWeb
PricingFAQ
Sign In
Get started free
Skip to content
  • Overview
  • How it works
  • Features
  • Security
  • Pricing

How it works

One ticket. Two places. One source of truth.

Your client works in a branded portal. Your team works in ClickUp. Step through one ticket and see what each side does, and what TickFlow Web does in between.

your-agency.tickflow.coClient portalIn progress
ticket · files · repliesstatus · public replies
ClickUp · Client supportYour teamacme-dental

Step through it

From report to resolved.

Use the tabs or the arrow keys. Each step shows your client, TickFlow Web and your team side by side.

Your client
Opens + New ticket on their portal, or reports from the page with the browser extension, or from their own site with the feedback widget. Title, description, priority, type and files.
TickFlow Web
Checks who is asking and which client account they belong to. That account decides the tag the ticket will carry.
Your team, in ClickUp
Nothing yet. Nobody had to watch an inbox.
shop.acme-dental.example/checkout
Pay nowdoes nothing
  • Screenshot, annotated
  • The element: button#pay
  • Page URL
  • Or a screen recording with audio
1 / 6

What syncs

Both ways. Except what you keep to yourselves.

The ticket is the ClickUp task: the portal reads it and writes to it through ClickUp’s API, so there is no second copy to drift out of date.

→From the portal to ClickUp

  • Each new ticket, as a task in the one list you chose
  • The client’s tag, so you can tell clients apart
  • Title, description, priority and ticket type
  • Screenshots, recordings and files, as attachments
  • The client’s replies, posted with their name

←From ClickUp to the portal

  • The task’s status, in friendly words
  • Your public replies
  • Files your team attaches to the task
  • Priority, ticket type and due date

Stays in ClickUp

  • Comments that start with internal, private or !!
  • Comments from ClickBots
  • Every other list, space and task in your workspace
  • Your ClickUp itself: clients never get a ClickUp login

A comment that is not marked is treated as a public reply. Make it a habit in your team to start private notes with internal.

Getting started

Four steps to your first real ticket.

An organisation admin does this once. Your team keeps working in ClickUp throughout.

  1. 01

    Connect ClickUp

    Paste an API token from your ClickUp. TickFlow tests the connection one check at a time, so you know exactly what to fix if one fails, and stores the token encrypted.

  2. 02

    Pick your support list

    Choose the workspace, space and list your tickets should land in. TickFlow can add a Ticket Type field to that list, or use the one you already have.

  3. 03

    Brand your portal

    Your subdomain, logo, icon, favicon and brand colour. It is the address your clients bookmark.

  4. 04

    Add a client, invite people

    Each client account gets its own tag. Invite its people by e-mail or share a join link; their admins can invite the rest of their team.

See every feature

See it run on your own ClickUp.

Start free. Connect ClickUp, pick your support list, brand your portal and invite your first client.

Start freeSee pricing

Questions first? Write to hello@tickflow.co or read the FAQ.

Open a ticket.
TickFlow Web

The client support portal for ClickUp teams: your clients report and follow up in a portal with your brand on it, your team works in ClickUp. Built by Orthoplex Solutions in Canada.

hello@tickflow.co

TickFlow Web

  • Overview
  • How it works
  • Features
  • Security
  • Pricing

Get started

  • Start free
  • Sign in
  • FAQ
  • Privacy policy
  • Terms of service

Also from TickFlow

  • TickFlow SDK
  • TickFlow Field
© 2026 Orthoplex Solutions. TickFlow and TickFlow Web are products of Orthoplex Solutions.Names, tickets and people in the illustrations are made up.TickFlow is an independent product and is not affiliated with, endorsed by, or sponsored by ClickUp. ClickUp™ is a trademark of Mango Technologies, Inc. Chrome is a trademark of Google LLC, named to show compatibility.