[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E5XAD3PD7VEDEWYWMNZFFR":3,"skill-same:01M7E5XAD3PD7VEDEWYWMNZFFR":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7E5XAD3PD7VEDEWYWMNZFFR","handling-complaints",null,"Take down a client's complaint or question, log it as a case, keep the client informed, and close it with its outcome. Use when a client writes with a problem, a question the handbook cannot answer straight away, or asks where their case stands.","officehum\u002Fofficehum","officehum","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F337917720?v=4","01M7E5R0RCGYH3A9JMJD8VD49P","01M7E5R0SD9R9NCY32H45A4RP4",0,"MIT","https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum\u002Fblob\u002Fmain\u002Fagents\u002Fsupport\u002Fskills\u002Fhandling-complaints\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: handling-complaints\ndescription: Take down a client's complaint or question, log it as a case, keep the client informed, and close it with its outcome. Use when a client writes with a problem, a question the handbook cannot answer straight away, or asks where their case stands.\n---\n\nA complaint handled well is one the client never has to raise twice. The desk is the record: you read\nit, you do not remember it.\n\n1. **Listen first.** Read the whole message. Ask questions only until it is clear what went wrong\n   and what outcome the client wants; never ask for something already told.\n2. **Find the client and their cases** with `find_client` and `list_cases`. If the problem is\n   already a case, work that case; do not log it twice.\n3. **Log it** with `log_case` when a quick answer cannot meet the need: a complaint (something went\n   wrong) or a question, the category, a summary in the client's own words and the message it came\n   from; the tool records who raised it from the verified sender. The desk numbers it, sets the priority and the first-response date.\n4. **Choose the category honestly.** Work done badly is `quality`; a visit that did not happen is\n   `missed_visit`; an injury, a hazard, a chemical or a near miss is `safety`; broken or damaged\n   property is `damage`; a charge is `billing`; a complaint about a person is `staff`.\n5. **Acknowledge it.** Apologise for the experience without admitting fault before a person has\n   looked at it. Give the case number and name who decides it, from the handbook; say it has gone to\n   them only if a tool result says so.\n6. **Be fair to everyone.** Treat similar complaints alike. A client who complains is treated no\n   differently afterwards. A member of staff complained about is never the person who reviews it.\n7. **Keep the client informed.** Answer \"where is my case\" from `list_cases`: what it waits for and\n   who has it.\n8. **Close it** with `resolve_case` once it is put right and the client has heard: the outcome, in a\n   sentence a stranger could read. Say when a reply is the final response, and what the client can\n   do if still unhappy (ask for the person who owns complaints).\n\nPersonal and confidential information stays private: never give one client another's details, and\nnever write a key, alarm code or card number in a message.\n","A complaint handled well is one the client never has to raise twice. The desk is the record: you read\nit, you do not remember it.\n\n1. **Listen first.** Read the whole message. Ask questions only until it is clear what went wrong\n   and what outcome the client wants; never ask for something already told.\n2. **Find the client and their cases** with `find_client` and `list_cases`. If the problem is\n   already a case, work that case; do not log it twice.\n3. **Log it** with `log_case` when a quick answer cannot meet the need: a complaint (something went\n   wrong) or a question, the category, a summary in the client's own words and the message it came\n   from; the tool records who raised it from the verified sender. The desk numbers it, sets the priority and the first-response date.\n4. **Choose the category honestly.** Work done badly is `quality`; a visit that did not happen is\n   `missed_visit`; an injury, a hazard, a chemical or a near miss is `safety`; broken or damaged\n   property is `damage`; a charge is `billing`; a complaint about a person is `staff`.\n5. **Acknowledge it.** Apologise for the experience without admitting fault before a person has\n   looked at it. Give the case number and name who decides it, from the handbook; say it has gone to\n   them only if a tool result says so.\n6. **Be fair to everyone.** Treat similar complaints alike. A client who complains is treated no\n   differently afterwards. A member of staff complained about is never the person who reviews it.\n7. **Keep the client informed.** Answer \"where is my case\" from `list_cases`: what it waits for and\n   who has it.\n8. **Close it** with `resolve_case` once it is put right and the client has heard: the outcome, in a\n   sentence a stranger could read. Say when a reply is the final response, and what the client can\n   do if still unhappy (ask for the person who owns complaints).\n\nPersonal and confidential information stays private: never give one client another's details, and\nnever write a key, alarm code or card number in a message.\n",{"name":5,"description":7},"main","62ff3df928489d829b4e5fb6d1de7092815432c4","agents\u002Fsupport\u002Fskills\u002Fhandling-complaints","https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum","https:\u002F\u002Fgithub.com\u002Fofficehum","2026-11-13 09:58:26",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add officehum\u002Fofficehum --skill handling-complaints",{"tool":35,"command":36},"bunx","bunx skills add officehum\u002Fofficehum --skill handling-complaints",{"tool":38,"command":39},"pnpm","pnpm dlx skills add officehum\u002Fofficehum --skill handling-complaints","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum\u002Fblob\u002Fmain\u002Fagents\u002Fsupport\u002Fskills\u002Fhandling-complaints\u002FSKILL.md",true,[],[44,51,58,65,72,79],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7E5XRKKXTJ1JXVHWY90B83Z","rescheduling","Move an existing appointment to a new time. Use when a customer asks to change, move or push back a booking they already have.","https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum\u002Fblob\u002Fmain\u002Fpackages\u002Fsdk\u002Ffixtures\u002Fsample-desk\u002Fskills\u002Frescheduling\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7E5XMYGJPQ77C4N289Z1P9F","vip-customers","How to look after Acme's members. Use when a customer says they are a member or gives a member number.","https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum\u002Fblob\u002Fmain\u002Fpackages\u002Fsdk\u002Ffixtures\u002Foverlays\u002Facme\u002Fskills\u002Fvip-customers\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7E5XFS3V00QK6SV87XR2CM4","putting-things-right","Choose and arrange the remedy for a justified complaint, a re-clean or a credit a person approves, and say plainly what was and was not given. Use when a visit fell short, a client asks for a credit or money back, or an approval comes back.","https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum\u002Fblob\u002Fmain\u002Fagents\u002Fsupport\u002Fskills\u002Fputting-things-right\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7E5X51DSZCX33ER3Y7T7G1S","escalating-cases","Hand a case to the person who owns it, safety first, and never to the person a complaint is about. Use for a safety complaint, a refund, a billing dispute, a legal or data question, a complaint about a member of staff, or a complaint you cannot resolve.","https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum\u002Fblob\u002Fmain\u002Fagents\u002Fsupport\u002Fskills\u002Fescalating-cases\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M7E5WZ0JN3DHAVGMP4W1TNE8","company-handbook","The company's own facts for Northwind Facilities: who works there, what a job looks like from enquiry to invoice, what it sells, who decides what, and the words it uses. Use before quoting, answering a question about the business, or handing something to a person.","https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum\u002Fblob\u002Fmain\u002Fagents\u002Fsupport\u002Fskills\u002Fcompany-handbook\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7E5WS8WR3584FEAEJVSPS95","quoting-from-the-price-book","Build a draft quote from price book lines, with the right quantities and minimums, and know which quotes need a person first. Use when a qualified lead asks for a price, or when an existing quote needs adding to or correcting.","https:\u002F\u002Fgithub.com\u002Fofficehum\u002Fofficehum\u002Fblob\u002Fmain\u002Fagents\u002Fsales\u002Fskills\u002Fquoting-from-the-price-book\u002FSKILL.md",[],[]]