Route every client request into assigned work.
The Wranker Agency Requests Feature replaces scattered client asks with one queue for intake, SLA triage, ownership, approvals, threads, exports and Convert to Task workflows.
Route every client request into assigned work
Intake, SLA triage, owner assignment, approvals, comments and task conversion in one agency-scoped queue.
Client asked for a sharper monthly PDF summary before the scheduled send.
Requests should not depend on whoever remembers the thread.
SEO agency work slows down when client asks are treated like messages instead of operational records. Wranker Agency Requests gives each ask a status, owner, SLA and next action.
Client asks live everywhere
Email, chat, calls, docs and portal notes all become separate request trails.
SLA risk is invisible
The queue only looks calm until overdue work becomes a client escalation.
Ownership is unclear
Requests get discussed without being assigned to a person, project or task.
Approvals lack proof
Teams cannot quickly show who approved, requested changes or converted the request.
One queue for intake, SLA triage, assignment, approval, conversion and exportable history.
A request desk built for SEO delivery teams.
Figures are structural module counts from the requested product design. Replace with verified customer benchmarks when production telemetry is available.
Default request triage chips planned for the Agency Requests page: Open, Overdue, Due soon, Waiting approval and Unassigned.
Board workflow columns for daily operations: New, In Progress, Waiting Approval and Done.
Right-rail cards for operational focus: Queue health, Approvals pending and My workload.
Closed loop from client ask to assigned owner, approval, linked task and exportable audit trail.
Capture, triage, assign, approve and convert.
The core Agency Requests loop is simple enough for daily work and structured enough for agency-grade reporting, permissions and audit trails.
Capture
Bring client asks, collaboration offers, internal requests and project-share requests into one agency-scoped queue instead of losing them in email, calls or chat.
Triage
Sort by status, SLA, client, assignee and priority so overdue, due-soon, waiting approval and unassigned requests move to the front.
Assign
Accept, decline, reroute, comment, assign an internal owner and choose project access without opening three separate admin screens.
Approve
Use Details and Thread views to approve, request changes, mark in progress or close requests with the context attached.
Convert
Turn accepted requests into tasks, project workflows, linked Drive assets or report sections so nothing stops as a note.
Capture incoming and outgoing requests before they scatter.
Agency Requests gives every ask a record: client, requester, status, priority, assignee, SLA, linked work and thread history. It works for internal asks, client asks, project-share offers and collaboration requests.
Know which requests need action first.
The main queue is built for daily triage. Teams can filter by client, status, SLA, assignee and priority, then use queue health cards to find what is overdue, due soon or unassigned.
Use list view for SLA control and board view for movement.
List view is designed for high-volume triage, sorting, columns, bulk actions and export. Board view gives small teams a visual workflow lane for New, In Progress, Waiting Approval and Done.
Open the full context without leaving the queue.
A Request Details drawer keeps summary, requester, description, attachments, assignment, linked tasks, approvals and thread history together. Teams can approve, request changes, comment and copy links from one place.
Client approved the SEO direction but needs the final intro reviewed before the scheduled PDF delivery.
RequestedMaya · 10:12
Ready for reviewPriya · 10:31
Please approve the rewritten intro before the report goes out.
Updated copy is linked. Waiting on final client approval.
Turn requests into assigned work with the context attached.
The request becomes useful when it creates delivery work. Convert to Task can prefill the task title, project, assignee and due date, copy request context and always link back to the request.
Client approved the SEO direction but needs the final intro rewritten before the scheduled report delivery.
Rewrite intro, keep the approved SEO direction, and confirm with client before PDF export.
Requests are the bridge between client intent and delivery work.
Agency Requests is not a separate inbox. It connects intake with Clients Hub, task execution, Drive files, role permissions, audit logs and report exports.
Clients Hub
Client request contextClient filters, client workspace request tabs, contacts, account notes and client-specific open request counts.
Campaign Activity Taskboard
Execution workflowConvert request to task, task ownership, due dates, linked task chips and task status follow-through.
Agency Drive
Evidence and filesAttachments, linked Drive items, request files, handoff documents and client-visible asset controls.
Team & Roles Management
Role-gated accessRequest permissions for view, create, accept, decline, reroute, approve, convert and export actions.
User Activity Tracking
Audit trailStatus change events, assignee diffs, approval history, exports, comments and request conversion telemetry.
Report Builder
Client reportingRequest summaries, SLA snapshots, completed request lists, PDF/CSV exports and client-facing status reporting.
A request workflow for every operating model.
Use the same request system whether you manage a few retainers, an in-house backlog or a multi-client agency portfolio.
Keep client asks visible before they become interruptions.
Capture small requests, access asks, reporting changes and content edits in one queue that can turn into task work.
Route requests to owners before delivery slows down.
Give SEO, content, analytics and account teams a shared intake system for approvals, assignments and project handoffs.
Run a request desk across every client portfolio.
Turn incoming collaboration requests, client tickets and internal asks into clean agency operations across Clients Hub, Activities, Drive and Reports.
“The team stopped asking where client requests lived. They opened the queue, saw SLA risk, assigned the owner and converted the request into delivery work.”
Use production telemetry to replace these placeholders with measured assignment speed, SLA response rate and task conversion rate.
Stop rebuilding the request story by hand.
Agency Requests keeps intake, triage, ownership, approval and delivery conversion in the same workflow.
See which client requests are open, overdue and ready to become work.
Start with a free audit, then see how Agency Requests can connect client intake, approvals, tasks, Drive assets and reports inside Wranker.
Connect request intake to the rest of the agency system.
Agency Requests works best when it connects to clients, tasks, roles, Drive, audit and reports.
Use the parent agency command center for portfolio KPIs, request widgets, users, projects, activity and audit visibility.
Open client-specific request queues, account context, contacts, client notes and workspace history.
Convert accepted requests into assigned SEO, content, reporting and technical tasks with owners and dates.
Control who can view, create, accept, decline, reroute, approve, convert and export agency requests.
Attach request files, linked Drive items, handoff docs, briefs and approval artifacts to the right client folder.
Audit request status changes, assignments, approvals, conversions, comments, exports and link-copy events.
Add request status, SLA summaries, approval history and task conversions into client-ready reports.
Use scheduled reporting views to show open requests, completed requests and what moved into delivery.
Questions agencies ask before centralising requests.
Direct answers for SEO teams evaluating the Wranker Agency Requests Feature.
What is the Wranker Agency Requests Feature?+
The Wranker Agency Requests Feature is an agency operations workspace for capturing, triaging, assigning, approving and converting client or collaboration requests. It combines a request queue, SLA states, assignee ownership, Details and Thread drawers, approvals and Convert to Task workflows.
Who should use Agency Requests?+
Agency Requests is built for SEO agencies, in-house SEO teams, solo SEOs, content teams and local marketers that need a reliable way to manage client asks, project-share requests, approval requests and internal handoffs without losing context.
What types of requests can Wranker manage?+
Wranker is designed around request types such as access, content, reporting, technical and general asks. The Agency Requests workflow also supports incoming and outgoing collaboration requests, project-share requests, approval requests and requests that need to become tasks or project workflows.
Does Agency Requests include SLA tracking?+
Yes. Requests can show SLA states such as Overdue, Due soon, On track and None. Queue health cards and KPI chips help teams filter overdue, due-soon and unassigned work before clients have to chase status.
Can requests become tasks in Wranker?+
Yes. A request can be converted into a task with a prefilled task title, optional project selector, assignee, due date, copied context and a required link back to the original request. This connects Agency Requests to the Campaign Activity Taskboard.
Can agencies approve or request changes from the request drawer?+
Yes. The Details drawer can show approval state, approval history, Approve and Request changes actions. Request changes can add a thread comment and move the request back into In Progress.
Does Agency Requests support both list and board views?+
Yes. List view is the default for SLA triage, filters, bulk operations and exports. Board view is planned as an optional workflow view with columns for New, In Progress, Waiting Approval and Done.
How does role gating work for requests?+
Viewer users can view requests, open details and copy links. Editors can assign, update status and convert requests to tasks where policy allows. Admins and Owners can run full request actions including bulk operations and admin-only deletion where enabled.
Can I export Agency Requests?+
Yes. CSV and PDF exports can respect current filters, sort, visible columns and selected rows. Exports can include watermark context such as agency, exported by, timestamp and filter summary.
How does Agency Requests connect to reporting and AI search workflows?+
Agency Requests supports AI-era operations by keeping client asks, approval context and task conversions structured. Request outcomes can feed reports, tasks and client updates, making it easier for answer engines and stakeholders to understand what the agency did and why it mattered.
Stop chasing requests. Start routing work.
Use Wranker to capture client asks, see SLA risk, assign owners, approve changes and convert requests into accountable work.