WaymarqClients and winning work
Client requests
What a client asks for, separated into asks, decided one at a time — and a page where they can see what happened to each.
Clients send things. One message, four different asks: a change to something you're building, a question, a new idea, "keen for a chat". You read it against the plan, work out what's new and what's already covered, and reply — and next week they ask again, phrased differently, because nothing told them what happened to the first one.
Client requests is the piece in the middle. A client sends a request from the same page they see the plan on; it lands on your project as a list of distinct asks; you decide what each one is; and their page shows the outcome of every ask, so the same thing stops being asked three ways.
How a client sends one
Every share link (see Sharing with clients) has a Your requests section under the plan: a box for their name, a message, and up to twenty files — plans, drawings, screenshots. No login, no account. Whatever they send appears below with what happened to it.
You can also log a message yourself — a WhatsApp, an email — from the project's Client requests page, attributed to them. In practice this is the one you'll use most.
What happens to it
Each request becomes one or more asks:
- With AI on for the project, the message is read against your plan — the task list, your standing decisions, and everything this client has asked in the last ninety days — and separated into its distinct asks. Each is labelled (detail on a task, new work, change request, question, wants a chat, already raised), matched to the task it's about where one fits, and given a proposed note or description. Every one is a guess for you to confirm. Nothing is added to the plan until you say so.
- With AI off, or past twenty digests for that client in a day, the message arrives as one ask and you sort it yourself. Split into asks turns one message into several — what AI would have done, done by you.
Deciding each ask
On the project's Client requests page, each ask has the same set of actions:
| Action | What it does | What the client sees |
|---|---|---|
| Attach to a task | Puts their words on the task as a client note, in their name, with any files they sent. The note is flagged until you tick it as read. | Added to "Visual design". |
| Raise a work order | Creates an unpriced work-order draft, so you decide whether to quote for it or waive it — where that decision already lives. | Raised as a change: "…". |
| Reply | Words only, shown under their request. Nothing else changes. | Your reply. |
| Ask them | One question back, with an answer box on their page. The ask waits, then comes back to you with the answer attached. | We need one thing from you: … |
| Noted | For a thank-you, or a request for a call. | Noted — we'll be in touch. |
| Dismiss | Quiet unless you write a reason. | Noted, or Not going ahead: your reason. |
| Confirm — already raised | When AI spotted a repeat. It's pre-marked, never confirmed for you. | Already raised — see above. |
The task's status decides what attaching means. On a task not yet started, the note is simply attached. On one that's underway, you choose between add it now (the assignee is told the scope moved) and park as a follow-up (the note goes on the task, and a work-order draft is raised to pick up afterwards). On a finished task, you reopen and attach — through the normal status path, so the reopen is on the record — or raise a work order instead. Detail on finished work is usually a defect or a change, and those are billed differently.
Raise everything as a work order
If you'd rather price every ask than sort it, set the project to Raise every ask as a work order on its Share page. Anything with work in it becomes an unpriced draft the moment it arrives; questions, requests for a call and repeats still come to you. Nothing is agreed or priced until you do it — a draft commits nobody to anything.
Let them ask the plan
Optionally, the client's page can carry an Ask about the plan box — "when's the visual design due?", "what's in the Design phase?" — answered automatically from the plan they can already see, and nothing else. It never mentions money, never reads your notes, and never changes anything; when the plan doesn't hold the answer it says so and offers to send the question as a request instead.
It's off by default — switch it on per project from the Share page, where AI is on for the project — because it runs on your AI budget from a public page. It's capped at twenty questions a day per link, and every question and answer is listed for you on the Client requests page: a question it couldn't answer is a hint about what the plan is missing.
Where you'll see them
- A banner on the project overview while anything is waiting — above everything else, because a person is on the other end of it.
- The Client requests page, under Manage in the project sidebar.
- A From the client panel on any task that has a client note, with a tick to mark it read.
- Optionally, an email or push when one arrives — off by default in Account → Notifications, since a busy client can send ten a day.
What the client never sees
Money in any form — not the work order's price, not whether you're charging — internal comments, your own notes on an ask, other clients. Their page is built from a short list of allowed fields, the same way the share link's plan is, so none of that can appear by accident.
For agents
The same actions are available over the REST API under Client requests, so an agent can triage the inbox — list what's waiting, attach, raise, reply, ask, or split — with exactly the choices a person has and nothing more.