Use case
Client request tracking with IDs and receipts
Client requests arrive by email, chat, calls and meetings, and the one that slips is the one the client remembers. In Phloz every request gets a reference, like ACME-R17, the moment it is filed, and the client gets a receipt by email. The request, its conversation and its progress stay under that one ID until the work is done.
Why client requests get lost
Most agencies take requests wherever the client sends them: an email thread, a Slack message, a comment on a call. Nobody owns the list, so each request lives in one person's inbox until it is done or forgotten. The client cannot see where it stands, so they chase, and every "any update on this?" costs someone a context switch. Without a record of what was asked and when, a small request that grew is hard to point to when the retainer runs over.
Every request gets an ID and a receipt
A client files a request in your branded portal: what they need and the details. Phloz gives it the next number in your request series (ACME-R17) and emails the client a receipt straight away. A new email from one of the client's contacts to the client's forwarding address files itself the same way, when the sender's domain passes DMARC email authentication; a request that comes by phone, or an email that can't be verified, is logged by your team, from New task or from "Log as request" on the client's message, and gets the same kind of ID. Your prefix comes from your workspace name and can be changed (2 to 6 characters); tasks have their own series, like ACME-142. Numbers are handed out by the database and never reused, so a reference a client quoted months ago still points at the same request.
Accept, decline or merge
New requests wait in a Needs triage group on your Tasks page. Accept one with an assignee, decline it with a reason the client reads, or mark it as a duplicate of another, and the client is emailed the decision. A duplicate tells the client which reference now tracks the work, when that item is shared with them. Clients cannot set priorities or deadlines, so your queue stays yours, and a request is never deleted: declined is a decision the client can see.
The client sees progress, not your internal work
In the portal, a request reads Received, then Accepted or Declined. Once you share it, the client follows a progress bar from Received to Accepted, In progress and Completed, with the due date, and is emailed when it starts, when it is done and when you need their approval. Internal tasks, assignees, comments and blockers stay internal. The client can ask for an update once every 48 hours, and can say a finished request is not finished.
One ID across email, search and AI
Every email about a request carries its ID in the subject, [ACME-R17]. A reply to any of them lands in that request's conversation, and so does a new email from one of the client's contacts that quotes the ID in its subject. Your team finds a request by pasting its ID into search, brackets and all, and a link to it opens it for any teammate who can see the client. An AI assistant connected to Phloz's MCP server (Growth and above) can look a task up by its ID too.
Common challenges agencies hit on this
The recurring obstacles agencies report when running this use case. Honest list — these aren't Phloz-specific problems, they're patterns we see across most agencies regardless of tooling. Worth recognising even if you don't end up on Phloz.
- Requests come in through email, chat, text, calls and meetings, so there is no single list, and the one that slipped is the one raised at the renewal meeting
- Clients chase for status because they cannot see it, and every chase interrupts whoever holds the request
- A helpdesk numbers the requests but feels like support, with tickets and auto-replies, and the work still has to be copied into the project tool
- Small requests add up to scope creep, and without a record of what was asked and when there is nothing to show when the retainer runs over
How agencies use this in practice
The pattern that works across most agencies running 5–50 clients: scope the use case as a discrete operational surface, assign a single owner (usually the ops lead or tracking engineer), set a recurring cadence (weekly check, monthly audit, quarterly review), and connect it to the rest of the agency's work via the tracking map and the per-client task surface.
The 1-2-week setup window is the same regardless of tool — the differentiator is whether the tool ships the primitives you need (client, tracking node, recurring task, audit template) or makes you build them yourself out of custom fields. Phloz ships them; generic PM tools don't. That's the entire trade-off, and it's only worth paying for once you have the client volume to need it (typically 5+ retainers).
Frequently asked questions
The three questions agencies ask most often about this use case. Honest answers — same data we'd give a friend evaluating the approach.
- Is Phloz a helpdesk for client requests?
- No. A request in Phloz is a task with a reference the client can quote and a receipt, not a support ticket: there are no SLAs, queues or canned replies. It lives in the same task list as the rest of the client's work, so accepting a request is the moment it becomes scheduled work, with an assignee and a due date.
- What does the client see in the portal?
- Their requests, each with its reference and status, and the conversation about it. Once you share a request, they also see its progress and due date. They never see internal tasks, assignees, comments or blockers. Clients sign in with a magic link, with no password, and the portal is on every plan, the free Starter plan included, with no fee per client user.
- Can I change the prefix or renumber requests?
- You can change the prefix: owners and admins set it in Settings, from 2 to 6 characters starting with a letter, and every task and request shows the new prefix at once. Old references still open the right item, because the lookup ignores the prefix. You cannot renumber: numbers are handed out in order and never reused.
Related in Phloz
Other use cases
Other ways agencies put Phloz to work.
14 days free for new workspaces · No credit card · Starter tier free forever