CW-087 · What Cwork's support covers, written down
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Create the support page under docs/, then read the installation guide and README.md and README.th.md to find where it should be linked. Cover the stated support boundaries, channel, hours, response time, absence coverage, and live-data session practices in Thai and English; mark liability wording as awaiting qualified review. Done when the installation guide links the page and, after owner confirmation in the PO room, both READMEs do too, with the owner-confirmed service details.
Written by the indexing model from the issue text.
Description
P1 · business · docs · S · before the first invoice; part of CW-077, not queued
The "what support means" point of CW-077, as its own ticket, the counterpart
of SuruchBoss/PaynEat#168. One person answers support online, beside a day
job, so its cost has to be held by a written scope rather than by locking
features or the installer away.
Scope
- One page, Thai and English: what support covers (Cwork itself: install
questions, errors, payroll results), what it does not (the customer's
server, network, Docker host or Windows, data entry, payroll advice), the
channel, the hours and the response time, and who answers when the owner is
away. - How a session works when live data could be seen (CW-077's remote access
point): the customer present, no copies taken, logs and the support bundle
(CW-080) asked for instead of database dumps. - The liability wording is a draft for a qualified reviewer, not final text.
Acceptance
- The page is linked from the installation guide and, once the owner has
confirmed it in the PO room like any change to the Editions section, from
the README; the owner has confirmed the channel, hours and response time. - The liability wording is marked as awaiting review until someone qualified
has read it.
Files docs/ (new page), README.md, README.th.md
Generated by Claude Code
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 6
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SuruchBoss/Cwork
-
documentation good first issue P3 phase-E
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
SuruchBoss/Cwork#50 ·
-
good first issue mobile P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SuruchBoss/Cwork#11 ·
-
P2
Difficulty 5/5 Over a week Newbie friendliness 25/100
SuruchBoss/Cwork#89 ·
-
P1
Difficulty 5/5 Over a week Newbie friendliness 25/100
SuruchBoss/Cwork#88 ·
-
P1
Difficulty 3/5 1-2 days Newbie friendliness 50/100
SuruchBoss/Cwork#78 ·
All issues in SuruchBoss/Cwork
Similar issues
-
area:deploy task
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
wilanis/wilanis-js#1017 ·
Maintainers usually reply within 1 day
-
documentation v2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
modelcontextprotocol/servers#5133 ·
Maintainers usually reply within 1 day
-
budget bug feature frontend good-issue medium needs-review OSCI'26 payments
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
SatyamPandey-07/WorkSphere#5990 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lugassawan/swe-workbench#799 ·
Maintainers usually reply within 1 day
-
bug good first issue javascript
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yukikotani231/sqlsift#326 ·
Maintainers usually reply within 1 day