Can clients create requests directly?
Request creation in the client view depends on current role and workspace permissions. Read-only access does not offer request creation. Check permissions for your workspace.
HOKUSH / Client request management
Client request management: clarify the request and track the work.
Keep client requests in context with Hokush job cards, responsibilities, target dates and related conversations.
What is client request management?
Client request management is the process of clarifying a request, assigning responsibility, tracking progress and communicating the result. Recording a message is only the start: the team needs to understand what is wanted, who should respond and when the work is expected.
How can you handle a content change request?
Give the request a work context
For example, a client asks to change the text on a campaign visual. Name the change in the job title and clarify the file and text in its description. A permitted client request form or a job card created by the team can be the starting point.
Resolve missing details
Clarify the replacement text, supporting files and deliverables in the related conversation. Keep decisions about the same request together rather than treating every message as a new job.
Assign responsibility and a target date
Assign a relevant team member, choose a target date and update status. A target date alone is not a service-level commitment; agree expectations separately.
Review the result and visibility
Share the deliverable in the client-facing conversation. Keep internal evaluation in the appropriate private area and check fields and files available through external sharing.
A short checklist before opening a request
- Can the requested change be described in one sentence?
- Is the correct file or version identified?
- Is the person expected to reply or approve clear?
- Are deliverables and the target date clear?
- Has client-visible information been checked?
Frequently asked questions
Is this an automated help desk?
This page does not promise automatic email/WhatsApp intake, SLA tracking or AI request routing. The described process uses job cards and follow-up managed by your team.
How is a request different from a revision?
A request describes work to be done. A revision asks for a change to an existing draft or deliverable. Keep its scope and decisions with the existing job when relevant; your team can decide when a separate job is needed.
Can clients see internal notes?
Visibility depends on roles, conversation channels and sharing permissions. Keep shared client conversations separate from internal team discussions and review available fields before sharing a link.