Share a request with HR
Choose who answers HR requests, review what you share before it is sent, and work the queue in Needs you.
Employees, HR responders and workspace administrators
Read as MarkdownAll guides as textAgent documentation index
Have your agent do thisPaste the prompt into Claude Code, Cursor or another agent. It follows this guide over MCP and asks before it changes anything others will see.Show the promptHide the prompt
Help me with "Share a request with HR" in my Shuffl workspace. 1. Read the guide: https://shuffl-rebuild.vercel.app/docs/markdown/hr-requests 2. Add Shuffl's MCP server: https://shuffl-rebuild.vercel.app/api/mcp Claude Code: claude mcp add --transport http shuffl https://shuffl-rebuild.vercel.app/api/mcp When the browser opens, choose my workspace and allow the access the guide needs. 3. Work through the steps in order: Administrator: choose responders; Administrator: categories and response target; Employee: review before sharing. Do what you can over MCP and tell me which steps only I can do in the browser or in Slack. Show me what you will change and who it affects, and wait for my yes before publishing, inviting or sending anything.
App links open your signed-in workspace. Check the selected workspace before making changes.
Administrator: choose responders
- In Manage, open People, choose a person and turn on HR responder under Roles. Owners start as responders; administrators are not unless you add them. Settings → Roles lists everyone who holds the role and the HR team name employees see, such as People Operations.
- A responder needs an enabled account of their own. If nobody eligible appears, enable the person in People first.
- Responders get a Slack direct message for each new request, or an email if their Slack account is not linked. Settings → Notifications sets which.
New responders get new requests only. Existing requests keep the responders the employee approved. Removing someone takes effect at once.
Administrator: categories and response target
- In Manage, open Requests → Settings. The note above the list says whether Mello built it from Knowledge or it is the starting list (Pay, Leave, Benefits, Letters, Personal details and Employee relations).
- Rename, add or remove categories if you want to. Keep the list short.
- Choose an owner for each one, or leave it with anyone on the HR team.
- Turn on Only named people can open these requests for sensitive topics, and tick who can.
- Set the response target: how soon HR should first reply, in business days. Weekends don’t count.
Mello builds the categories from your published Knowledge, so they match what your documents cover, and updates them when you publish more. Until you publish documents, a starting list is used. Once you edit the list yourself, Mello leaves it alone; Rebuild from Knowledge replaces it with Mello’s again.
Mello puts every new request in one category and tells that category’s owner first. Responders can move a request to another category from the request itself.
A sensitive category, such as complaints or medical leave, opens only for the people you name. Other responders cannot list or open those requests, even with a direct link. The person who asked always sees their own request.


Employee: review before sharing
- Ask Mello in Chat or in a Slack direct message. When a person needs to help, Mello prepares a short message and names the responders who would receive it.
- Read the prepared message. Choose Edit message to change it or explain the correction to Mello. Include only what you want HR to see.
- Choose Share with HR on the web or Send to HR in Slack once the message and recipients look right. Nothing is sent before that.
- Replies arrive in the same chat or Slack thread. Your HR requests in Chat lists everything you have open; each request has Still need help and Resolved.
HR receives the reviewed request, not your whole conversation. If HR is not set up, contact your HR team the usual way.
Responder: own and answer a request
Responders see open questions under Needs you and on the Home tab of the Shuffl app in Slack. Open a request to see the private HR workspace in Chat: the employee’s reviewed message, who owns it and the thread so far. Take ownership tells other responders you have it; Release to HR team hands it back.
Draft a reply with Mello, read it, then choose Send reply; the employee gets it in their original conversation. If the reply contains guidance others would need, Mello proposes it as Knowledge with the case details left out.
Mark resolved asks how it was answered: pick the published Knowledge article that answers it, choose Needs an article, or No article needed. Needs an article starts a Knowledge draft from your last reply, which a verifier still approves before anyone can read it.
Reopen question brings a request back. Slack and the web share the same request, so a reply sent from either shows in both.


See how requests are going
Requests → Insights, for administrators, shows how many requests came in, the time to first reply and to resolve, the share answered within your response target, and how many are waiting on HR.
By category lists the busiest categories first, with their first reply time, share within target and how many need an article. Response target by month shows the trend. Review the top categories each quarter and write the articles they need.
It also counts Knowledge drafts approved and waiting for review. The weekly HR digest carries the totals to administrators and responders.
Product help is a separate conversation
Help & feedback → Contact Shuffl is for product questions, not your organization’s HR requests. These guides do not cover your employer’s policies or give personal HR advice.