Creative requests need a reliable front door
A client asks for a campaign banner in Slack. An account manager forwards an email about a landing page. Someone from the agency team drops an urgent social request into a project channel. The designer gets a partial brief, the due date is unclear, and no one knows if the work is included in the retainer.
That’s a familiar intake problem for marketing and creative agencies. Requests come from different people and places, and the details vary. The task of turning them into usable work often falls to an account manager who has to chase information, interpret what the client meant, decide who should handle it, and make sure it gets tracked.
The issue isn’t that people don’t care about process. It’s that the process usually depends on someone remembering every step while they’re already managing several accounts. A request can sit in a Slack thread, get duplicated in a project board, or start production before the team has agreed on what “done” means.
Automating creative request intake gives every request a consistent path from first message to trackable task. It doesn’t remove the account manager’s judgment. It reduces the manual work around capturing the request, filling in missing details, routing it, and keeping its status visible.
What the current process costs
The cost of a request isn’t limited to the time spent creating the asset. The agency also spends time finding the request, clarifying the scope, assigning it, and explaining delays when someone later asks for an update.
Those small interruptions add up across accounts. An account manager might spend part of the morning checking Slack, email, and a project board, then spend the afternoon answering questions about the same requests. If each new ask needs a separate round of clarification, the agency pays for the same administrative work again and again.
That matters when account managers are already carrying reporting and client communications. Account managers may also spend time on reports, decks, and updates. Intake automation doesn’t solve that reporting burden by itself, but it can stop unstructured requests from adding more coordination work to an already crowded role.
There’s a margin issue, too. Producing assets can eat into an account’s profitability. When briefs arrive incomplete, production time stretches. Teams may create the wrong version, wait for missing copy, or find out late that the client expected several formats rather than one.
Operational leakage is worth examining for marketing and creative agencies. Request intake alone may not account for all of it. The relevant question is how much paid time your team spends clarifying, rerouting, duplicating, and tracking work that could follow a defined process.
Map the request before automating it
Start by looking at the actual sources of incoming work. Don’t design the workflow around the one channel people are supposed to use. List the channels they use now.
That might include:
- Client email and forwarded email
- Slack or Teams messages
- A form on the client portal
- Account manager notes from a call
- Internal requests from strategy, paid media, or production
- A project management board where someone creates tasks manually
For each source, ask what happens next. Who reads the request? Who decides if it’s in scope? Who follows up when the brief lacks an asset size, due date, audience, or approval owner? Where does the approved task get created?
The answers usually reveal that the agency has more than one intake process. A client might submit a request through a form, while an account manager puts internal asks into Slack. The team may also have different rules for design, copy, video, paid media, and web work.
Write down the distinctions that affect routing. For example, a new campaign concept may need strategy before design, while a resized ad may go straight to production. A client request may need an account manager to confirm scope, while an internal request may only need a team lead’s approval.
If approvals are a separate bottleneck, it helps to map that handoff as well. This guide on automating creative approvals at your agency covers what happens after the work is ready for review. Intake should connect to that process rather than create another disconnected queue.
Turn each request into a structured brief
The goal isn’t to make every request form long. The goal is to capture enough information for the next person to understand the job and move it forward.
A useful intake brief usually includes:
- Client or internal team
- Requester and contact details
- Type of work, such as copy, design, video, or campaign support
- Business goal and intended audience
- Deliverables and required formats
- Due date and reason for the deadline
- Relevant links, files, or references
- Account, campaign, or project
- Scope status, such as included, needs review, or out of scope
- Approval owner and any required review steps
Some fields can be completed from the message itself. Others should remain questions if the request doesn’t contain the answer. A system can identify that an email says “next Friday,” but it should confirm the exact date if the message was sent near a weekend or if the client’s time zone matters.
A good intake workflow also distinguishes missing information from optional information. If the request has no target audience, that might block strategy work. If it has no preferred font, the designer may be able to proceed. The rules should reflect how your teams actually work, not a generic form template.
When a request is incomplete, send a short follow-up that asks for the specific missing details. Don’t make the requester resubmit the whole brief. Keep the original message and attachments connected to the request so the team can see the source context.
Route work based on rules, not guesswork
Once the brief is structured, the next step is deciding where it goes. Routing can use a combination of account, service line, deliverable type, urgency, and scope status.
For example, a request for an email campaign might go to the account’s marketing team, while a landing page request goes to the web queue. A paid social asset may need a campaign or media lead attached. A request marked as urgent shouldn’t automatically jump the queue. It should be flagged for a person to check the deadline, client commitment, and trade-offs.
Set clear rules for exceptions. A request that appears out of scope should go to the account manager for a decision, not directly to production. A request with no confirmed due date can be assigned a priority review task rather than an invented deadline. If two teams could own the work, route it to a designated triage owner instead of leaving it in a shared inbox.
The same principle applies to internal asks. A team member might request an asset for a proposal or a campaign update. The workflow can capture who needs it, why, and by when, then route it through the right internal review. That keeps internal work visible beside client work without pretending they have the same priority or billing rules.
For a related workflow, see how agencies can automate client approvals. Clear ownership at intake makes it easier to define who needs to approve the work later.
What an intake agent does end to end
In practice, an intake agent can monitor the agreed request channels, identify incoming asks, and create a structured record for each one. The exact setup depends on your tools and permissions, but the workflow should be explicit.
A typical path looks like this:
-
Capture the request. The agent receives a message from an approved inbox, form, or collaboration channel. It records the source, requester, client, timestamp, and attached files or links.
-
Extract the useful details. It identifies the requested work, deliverables, stated deadline, campaign, and other information present in the message. It shouldn’t present a guess as a confirmed requirement.
-
Check the brief. It compares the captured details with the fields required for that type of work. If a key item is missing, it drafts a focused clarification message or sends one if that action has been approved.
-
Apply routing rules. It checks the client, service line, request type, urgency, and scope indicators against the agency’s routing rules. Unclear or high-impact decisions go to a person.
-
Create the task. Once the brief meets the team’s requirements, it creates a task in the project system with the structured details, source context, owner or queue, and appropriate status.
-
Confirm and track. The requester gets a confirmation with a task reference or status link. The team can see whether the request is awaiting information, under review, ready for production, or in progress.
-
Keep a record. The request and its changes remain connected, so an account manager can check what was asked, when the deadline changed, and who approved the work.
The important boundary is that automation can prepare and route work, but the agency decides where a human must approve it. Scope, priority, and client commitments are often commercial decisions. Keep those decisions visible and assign them to someone with the authority to make them.
If you’re working through which steps to automate first, Book a 60-min Omni Audit. We’ll map the current process, identify practical opportunities, and agree what to test first.
Create tasks people can actually work from
A task created from an intake workflow should be useful without requiring the assignee to reconstruct the brief from a chat thread. Include the deliverables, audience, objective, due date, source links, requester, client, and any review requirements that apply.
Use statuses that describe the work, not just who has it. A simple set might include “needs information,” “scope review,” “ready for production,” “in progress,” and “waiting for client.” The right labels depend on your current project system. Avoid adding so many status options that nobody knows which one to choose.
Keep assignment and workload rules realistic. If a designer is already at capacity, assigning every new design task to that person doesn’t solve the problem. Route work to a team queue or capacity review when individual availability isn’t known. The intake process should make demand visible, not create a false impression that a task is covered.
Revision requests are often a second intake problem. They can arrive in comments, email, or a call recap, and the team needs to know which asset and version they refer to. If that’s a recurring issue, connect the request workflow with automating creative revision requests. That gives the agency a clearer record of both new work and changes to existing work.
Measure whether the workflow is paying off
Before changing the process, record a practical baseline. You don’t need a large analytics project. For a few weeks, track how many requests come in, how many arrive incomplete, how long it takes to create a task, and how often a task has to be rerouted or clarified.
Also look at where requests wait. A request might be captured quickly but sit for two days waiting for a scope decision. That’s a different problem from a request getting lost before anyone sees it. Separating those delays helps you fix the right step.
After the workflow is live, compare the same measures. You might see fewer incomplete tasks or less manual copying from messages into the project system. Check whether account managers spend less time chasing missing details and whether the team can find the source context without asking the requester again.
Don’t treat a faster task-creation time as the whole result. If automation creates tasks that teams don’t trust, the agency has simply moved the work into a different queue. Review examples with the people who receive the tasks. Ask whether the brief is accurate, whether the routing makes sense, and whether any decisions are being made without the right person.
Good intake can also support other operational work. Once the agency has clean request and delivery data, it’s easier to connect workload, account health, and reporting. A reporting workflow can help prepare a report and email summary for an account manager to review. A content production workflow can help create a first-pass asset from an approved brief, giving the team something to edit instead of starting from a blank page. Both depend on clear inputs and human review.
Plan around the agency’s real economics
The value of intake automation varies by agency. A firm with a small number of tightly managed accounts may not need to automate every channel. An agency with multiple service lines, busy client teams, and frequent production requests may have more to gain from a shared intake path.
The account scaling ceiling matters here. An account manager’s capacity depends on the service mix and client demands. If every new account adds more manual request handling, hiring can become the only way to keep up. A cleaner intake workflow won’t remove the need for people, but it can reduce coordination work and make workload easier to see before adding capacity.
When estimating the opportunity, use your own numbers. Count the requests received in a typical week. Estimate how many need a follow-up, how long it takes to turn one into a task, and how often work is delayed or redone because the brief was incomplete. Apply a conservative hourly cost that reflects the people doing the work. Keep any expected production savings separate from time saved on administration.
This avoids treating every minute saved as a cash saving. Some recovered time may help the team handle more work without adding headcount. Some may reduce overtime or rework. Some may simply give account managers more room for client planning. Those outcomes matter, but they are not interchangeable when you’re making a financial case.
Start with one service line or client group
Don’t launch a new process across every account on day one. Choose a service line or a small group of clients with enough request volume to test the workflow. Include the people who submit requests, the account managers who review scope, and the production team that receives tasks.
Agree on the required brief fields and the routing rules before connecting channels. Decide which actions the system can take automatically, which messages need review, and which decisions always stay with a person. Then test real examples, including incomplete requests, urgent requests, out-of-scope requests, and requests with attachments or multiple deliverables.
Review the test tasks with the team. If people keep correcting the same field, improve the extraction or change the intake question. If work is routed to the wrong team, clarify the rule. If users ignore the confirmation because it doesn’t answer what they need to know, revise the message.
After the workflow is dependable for that group, extend it to more channels or service lines. Keep ownership clear. Someone should be responsible for reviewing exceptions and updating rules when the agency changes its services or project structure.
Use an Omni Audit to choose the first workflow
An Omni Audit can help you examine how requests move through your agency, where manual handoffs may be slowing the work, and what needs to be true before automation can help. That gives the owner, partner, or GM something concrete to discuss with the team.
For agencies in this vertical, see Omni for marketing and creative agencies. The audit can cover request intake alongside related operations such as reporting, approvals, and content production, so you can decide whether to start with intake or tackle a more costly bottleneck first.
If you’re ready to map the workflow, Book my Omni Audit. You can also review the AI audit for marketing and creative agencies before booking. The goal is to leave with a clear first step, not another generic technology plan.
Your guide is ready
Check your downloads folder. If it did not open automatically, use the button below.
Download the GuideYour guide is ready
Check your downloads folder. If it did not open automatically, use the button below.
Download the GuideTalk it through
Talk it through with Sam
30 minutes on what a Command Centre would look like for your business.
Book a call