Build your own dashboards
Dashboards, New dashboard: add widgets from a library (a number with its change on the last period, bar, line, area and donut charts, a list of records, a leaderboard, a goal) and drag or resize them on a grid. Each takes its figures live from deals, people, companies, tasks, projects, tickets, invoices, activities or time. Filter the whole dashboard by dates, workspace or owner, refresh it on its own, show it full screen on a TV, or export any widget as CSV. Start from the Sales, Support or Delivery template, keep a dashboard private or share it with a workspace or everyone; each person still sees only the figures they are allowed to.
What your team keeps on a ticket, your client never sees
A ticket in the Support Hub has a Team only panel: an internal status of your own (Waiting on dev, Needs quote), internal tags, fields you define under Settings, Custom fields, Tickets, a note for whoever picks it up, and a link to the task it is being worked in, in ClickUp, Asana, Jira or anywhere else. None of it reaches the client, in the portal or anywhere else. The ticket list shows each ticket's internal status and tags, and searches and filters by them.
Ticket webhooks
Webhooks can now listen for tickets: a ticket filed, changed, moved to another status (the one your client sees or your internal one), retagged, or answered (a reply, the client's message or an internal note). Each one carries the ticket with its team-only details and what changed, so your project tool or Slack can follow along.
Tickets in the API
The REST API reads, files and changes support tickets, their team-only details and field values, adds or removes tags, reads the conversation and adds replies or internal notes, lists every file on a ticket with a download link and attaches new ones. It is on the API page, under Support tickets.
A task waits for what it depends on
A task can be blocked by others in its project, and it cannot move to In progress, Review or Completed until they are finished or cancelled: the board and the task say which one is holding it up. A task shows what it is blocked by and what it is blocking, and no two tasks can wait on each other.
A timeline of the project's tasks
The project page has a Timeline: each task a bar from its start to its due date, subtasks under their parent, milestones as diamonds, a line for today, and arrows from each task to the ones waiting on it, red when the dates do not add up. Drag a bar to move it, or its end to change the due date. Tasks have a start date now.
Workload: who has how much, day by day
Projects, Workload shows each person's planned hours for the days or weeks ahead, from their tasks' estimates spread between start and due date, against the capacity set for them: green, amber when nearly full, red when over. Click a day to see the tasks behind it and hand one to someone else. Tasks with no date wait in their own column.
Fields of your own on tasks and projects
Settings, Custom fields now takes fields for tasks as well as projects: a job number, a site address, billable or not. They show as columns in the Projects and Tasks lists, filter and sort there, are edited on the task and the project, and are read and written by the API.
Save a project as a template, and get the whole plan back
Save as template on a project keeps its tasks with their dates from the start, subtasks, dependencies, milestones and field values. A project made from a template brings all of it back, dated from the new start. Using a template had stopped working: it works again.
Repeating work on any schedule
A task can repeat every few days, weeks or months, on chosen weekdays, until a date or for a number of times, dated from its due date or from when it was done. Each new one brings its subtasks, assignee, estimate and fields, and the task says when the next is due.
Time logged against a task
A task has a Time tab: start a timer or log time by hand, and see hours logged against the estimate. Timesheets and their export name the task the time was spent on.
Several people on one task
A task can have as many people on it as it needs, one of them the lead. Pick them on the task and see their faces on the board and in the list; each person added is told. Workload counts the task for everyone on it, the portal shows the client who is on each task, and the API and MCP read and write assignee_ids.
Statuses of your own for each project
Statuses on a project's board lets you name, colour, order and add columns: Client review, Waiting on materials, Signed off. Each one counts as one of the five built-in statuses, so reports, dependencies and repeating work still know when a task is finished. The portal shows clients your names for them.
Subtasks inside subtasks
A subtask can have subtasks of its own, up to five levels below a task. The task shows the path above it, and the whole tree comes along when work repeats or a project is saved as a template. No task can end up under itself.
Every task of every project on one timeline
Projects, Timeline has a Tasks view: the tasks of all your projects as bars on one chart, grouped by project, with a line for today. Click a bar to open its project.
Choose what your client sees
On a project with a client, each task and milestone is Shared with client or Internal: click the chip on a card, or tick several and share them together. A task under an internal one stays hidden too. Client view on the project picks which sections the client sees (progress, milestones, tasks, people, deliverables, proofs, time and budget), and Preview as client shows it as they will.
Automations on each project
Automations on a project page: when a task is created, moves to a status, gets someone on it, goes overdue or has all its subtasks done, then assign, set status or priority, add a checklist, move the due date, notify or comment. Each rule shows when it last ran and any error. Templates keep a project's automations.
Project tasks start workflows
Workflows have a Project Task trigger: created, status changed, completed, someone put on it, due date or priority changed, overdue, or due within a day. New steps create and update project tasks, comment on them and tell the people on them.
Checklists on tasks
A task can have several checklists: tick items off, give one a person and a day, drag to reorder, or make an item a subtask. Cards and rows show 3/5. Keep a checklist as a template and add it to any task. Repeating tasks and project templates bring checklists along, nothing ticked.
Link tasks to each other
Relationships on a task links it to any other task, in any project: relates to, duplicates or duplicated by.
Folders for projects, lists for tasks
Folders on the Projects page group projects, with one level of folders inside; every view, the timeline and calendar too, narrows to a folder, and Portfolio sums each folder up. Inside a project, Lists split its tasks into sections, shown as a list or as board columns.
Task calendars and task reports
Projects, Calendar has a Tasks view, and each project has a Calendar tab: drag a task to a day to move it. Reports can be built from project tasks across every project.
Support tickets in one workspace
Support, Tickets now opens a ticket beside the list instead of in place of it. On the left, saved views with live counts: mine, unassigned, waiting, SLA at risk, resolved lately, and your own statuses and tags. Tick several tickets to assign them, change their status or priority, or close them together. The keyboard does it all: j and k to move, Enter to open, r to reply, x to select, ? to see every shortcut. Each ticket has its own address, so it can be linked and the back button works.
A client reads only what is theirs on a ticket
Notes, tags and field values the team kept on a ticket used to sit on the ticket itself, where a client could have read them on their own tickets. They now live on the team-only side, and a client's portal asks only for what it shows.
The project board drags, and shows subtasks
Cards on a project's board drag between columns, show their subtasks done out of total, and open to tick them off or add one, without leaving the board.
Emails read as they were written
An email in the Support inbox now shows as an email, with its formatting (shown in a safe, sandboxed frame) and earlier quoted messages folded away, not squeezed into a chat bubble. Characters that came out garbled ("’" where an apostrophe belonged) are put right, in new mail and in mail already received, and the sender shows as their name rather than the whole "Name <address>" line.
Campaign audiences count everyone
When you build a campaign, each segment shows how many people are in it now, and the total counts each person once, leaves out anyone unsubscribed, and is exactly who the campaign will go to. A campaign with nobody to send to cannot be sent by mistake, and a list that has since been archived is pointed out.
Replying to Facebook and Instagram comments
Connecting a Facebook Page or Instagram account now asks for the permissions the social inbox needs to read comments and reply to them, and Instagram post reach and views. If replies from the social inbox failed with a permissions error, connect the account again. Every Facebook and Instagram call now uses Meta's current Graph API.