Questions, answered

Navbatly is a support desk for web agencies and freelancers, made by Karve Digital. Each request becomes a ticket numbered per client, hours count against the client's contract in the month they were worked, each client gets a plain-English monthly report, and Client Clock counts the days each project waits on the client.

Agencies, studios and freelancers who look after clients on support plans, project budgets or hourly work. If you build things for clients and wait on them for content, access or approvals, Client Clock is for you.

The part of Navbatly that tracks what you need from your clients. Each ticket lists its client actions, each asked of one person at the client with its own clock of days waited. Your client sends them from their private link, and each project's target date moves by the days it waited. How Client Clock works.

No. Each client gets a private link, with no sign-in, where they see what's waiting on them and send it, with files if they need, read their monthly report and send you a new request. You can turn the link off at any time.

Clients can also email your ticket inbox, and you can email the monthly report to the client's contacts.

Yes. Your team has a ticket inbox, shown on your team's settings. An email to it from an address you have for a client, the client's own or a contact's, opens a ticket, files included, as a request from their link does, as long as the client has a contract running.

Every email you send a client about one ticket goes out with that ticket's own reply address, so when they answer, it lands on the ticket as their reply. Emails about several tickets, the report and the pause notice reply to your team.

When an email can't open a ticket, because the sender isn't one of a client's addresses, or the client is archived or has no contract running, nothing opens and nothing is emailed back, so point those clients to their request link. Auto-replies and bounces are dropped the same way.

Yes. They can drop up to 10 files, each up to 10 MB, into a request or into what they deliver: images, PDFs, Office documents, CSV, text or zip files. Files attached to an email to your ticket inbox, or to an answer to a ticket's email, come in too.

Yes. The report line, notes on client actions, the pause notice and the note on a report email take bold, italics, lists and links. Raw HTML and unsafe links are removed before anyone sees them.

A day counts when a client action is still outstanding at the end of that day, so one delivered the day it was asked has waited none. If you send one back, its clock runs again and adds to the same total. For a project, a day counts once however many actions were outstanding that day.

Yes. On your team's reminder days, 3, 7 and 14 days to start with, Navbatly emails each person a list of everything they still owe, with a link to send it. You can change the days, send none, or switch reminders off for one client. The clock keeps counting either way.

The agreed date moved later by each day the project has waited on the client since it was agreed or last changed. Clients see it on their private link, with any change to the agreed date.

An email you can send a client saying a project's work is on hold until they deliver what is outstanding. Navbatly suggests one once the project has waited 21 days (you can change that), but only you decide to send it, and it changes nothing else about the project.

Time counts in the month it was worked, not the month the ticket was opened. Each entry is included in the plan, billable on top, or no charge.

On a support plan, unused hours can roll over, up to a cap if you set one, and you choose what happens when a month runs over: show it, bill it, carry it into next month or write it off.

Client contact is time spent with the client: calls, meetings and emails. Delivery is the work itself: building, fixing, updating and testing. Both count against the contract, and the split shows where the hours went.

The plain-English line you write for each ticket, never your internal subject or notes. Tickets are grouped into work completed that month and work in progress, each with that month's hours, under the hours used and left on their plan or budget. Only the labels you choose appear on reports.

The report also lists the client actions they delivered that month and those still outstanding, with the days each one waited.

Yes. New terms apply from the month you choose, and earlier months keep the terms they had, so reports you've already sent stay the same.

A client request that nobody has assigned, answered or scheduled yet. It stays on the New requests list, soonest response due first, until someone picks it up.

No. Estimates never count. If you log time on a backlog ticket, that time counts in the month you worked it, unless you mark it as no charge.

With New project. Name the project and the client, and Navbatly adds the client, the project and an hourly task contract in one step, ready for tickets. Add the agreed date if you have one.

Talk to us about plans: email [email protected] and we'll talk it through.

Navbatly has an MCP server at https://navbatly.com/mcp. Add it to Claude as a custom connector, or to any app that supports MCP, and sign in with your Navbatly account when asked.

The assistant can then work with tickets, time, client actions, clients and reports in the teams you belong to, with the same permissions you have. What the assistant can do.

Owners can do everything, including deleting the team. Admins run clients, contracts, plans, templates, labels and reports, invite people and manage everyone's time. Members work tickets: they open them, reply, log time, and edit or delete their own.

With an email and password, with optional two-factor authentication, or with a passkey.

Yes. Export a month's hours by contract, or every time entry, as a CSV file. Each client's report can also be printed or saved as a PDF.

Create your team, add your first client and contract, then open a ticket. If you'd like a walkthrough first, email [email protected].