How to Manage Client Requests at an Agency Without Living in WhatsApp
Paul Boards ·
To manage an agency's client requests outside WhatsApp, set up a single place where every request becomes a task, with client, owner, deadline, and status. WhatsApp still works for quick contact, but the rule becomes simple: a request that hasn't become a task doesn't exist. A management system like Scrumboards helps because it brings tasks by client, email, forms, and reports into the same workspace.
The rest of this guide shows how to build that workflow, how to introduce the change to clients without it feeling like red tape, and which agreements keep the phone from becoming the request hub again.
Why WhatsApp turns into the request hub
Clients send a message because it's fast and because the agency replies. Over time, the client group chat piles up design requests, caption tweaks, payment receipts, product photos, and four-minute voice notes explaining the campaign. All mixed together.
The problems show up in day-to-day work:
- A Friday-night request is buried under twenty messages by Monday.
- The account manager forwards it to the designer in another group, and the context gets lost along the way.
- Nobody knows whether the change was requested before or after approval.
- At the end of the month, the agency can't show how many requests the client made.
The four-step workflow
1. Intake: every request comes in through a tracked channel
Choose one to three entry points and tell the client what they are. The formats that work best:
- Request form. In Scrumboards, the CRM has forms you can publish and embed on any page. Fields like asset type, desired date, reference, and file attachment save ten back-and-forth messages.
- Email. A shared inbox on the agency's domain, inside Scrumboards itself, for people who prefer to write.
- WhatsApp with transcription. If the client insists, the account manager turns the message into a task the same day and replies with its number or link.
2. Triage: the request becomes a task with an owner
One person per shift handles triage. For each request, they set the client, project, owner, priority, and deadline. Task templates speed this up a lot: "feed post," "story," "design revision," and "monthly report" start out with a checklist and a default deadline.
3. Production: the status tells the story
Use a few statuses that everyone understands. For example: "Intake," "In production," "Internal review," "With client," "Revision," "Approved," and "Published." Scrumboards' status history records every move and who delivered. When the client says "I asked for this last week," the answer is in the task.
4. Follow-up: the client knows where to look
Instead of texting "it's done" on WhatsApp, the account manager sends the client's weekly report as a link that opens without a login. It shows what came in, what was delivered, and what's waiting for approval.
Build the workflow with one client this week. Create the request form, three task templates, and your agency's statuses. Create the request workflow on the Free plan.
How to introduce the change to the client
The conversation works best when it focuses on what the client gains and when they have to learn as little as possible:
- Explain the reason in one sentence. "So none of your requests get lost, we're going to log everything in one place."
- Show them the form. Send the link and fill it out together the first time.
- Agree on a response time. Requests that come in by 3 p.m. get a reply the same day, for example.
- Keep WhatsApp for emergencies. Define what counts as urgent: a live post with an error, a stalled campaign, a crisis.
- Send the first weekly report. When the client sees the list of what was done, they understand the value of tracking.
Internal agreements that keep the workflow in place
- Hand-offs happen only through tasks. The account manager doesn't send requests to the designer by message. They create or update the task and mention the person.
- Files live in the task. Photos, briefs, and references are attached there, not in someone's camera roll.
- Team chat in its own room. Scrumboards Rooms keep the team's conversation, with mentions and attachments, separate from the client.
- Meetings with a record. With the virtual office's video meetings, the client joins by link. Whatever is decided becomes a task at the end of the call.
- Timer running. Hours per task show how much each client consumes, which helps when renegotiating packages.
A sample week
Monday, 9 a.m.: the agency's clothing store client fills out the form asking for three stories for Thursday's sale. The task is created in the "Social media" project with a Wednesday deadline. The account manager assigns the designer and the copywriter.
Monday, 2 p.m.: the copywriter asks ORION, BrainPilot's copywriting agent, for a first draft of the captions in the store's brand voice, which is already in the client profile. She reviews and edits it.
Tuesday, 4 p.m.: the designs move to "With client." The store asks to swap the photo in the second story. The task moves to "Revision" and the history logs the rework.
Wednesday, 11 a.m.: approved. On Friday, the weekly report shows the three stories delivered, one revision, and the time spent. If the account manager had taken Tuesday off, whoever covered for her would have found everything in the task.
Common rollout mistakes
Too many statuses
Fifteen statuses look organized on day one and turn into confusion by week two. Start with seven or fewer and only add another when the team actually misses it.
A long form
If the request form has twenty fields, the client goes back to WhatsApp. Ask for the essentials: asset type, date, goal, and an open field for references.
Triage with no set time
When nobody has a fixed time for triage, requests pile up at intake. Two slots a day, at 10 a.m. and 3 p.m., work for most small agencies.
Management working outside the system
If a partner keeps asking the team for things by phone, the rest of the team takes the rule as optional. The change has to start with the people in charge.
What to measure after a month
- How many requests came in through a tracked channel and how many still arrived only via WhatsApp.
- How many tasks missed their deadline.
- How many revisions per client, in the revisions report.
- Hours per client compared with the contract value.
These numbers show whether the workflow stuck and give you a basis for the renewal conversation.
Frequently asked questions
Do I need to stop using WhatsApp with clients?
No. It stays for quick contact and emergencies. What changes is that every request becomes a tracked task.
Does the client need a login to the system?
To make a request, they can use a public form. To follow along, they receive reports via a link that opens without a login.
Who should triage the requests?
One person per shift, usually from account management. They set the client, owner, priority, and deadline.
How do I keep the team from going back to passing requests by message?
Agree that hand-offs only count through tasks and use mentions inside them. Management checks the report to make sure everything has an owner.
Does it work for businesses that aren't agencies?
It works for any team that receives requests from internal or external clients, such as consultancies, IT, and operations.
Start with the front door
The first step is deciding where requests come in. After that, triage and statuses come naturally. See how the tasks, CRM, and email modules work together, get answers in the FAQ section, or explore the full platform.