Corrections, bug reports and suggestions — and what to include so we can act on them
| Operator | LI JIANLIN |
| 3562027578@qq.com | |
| Office | Room 204, No. 8 Jurenfang, Dezheng Zhong Road, Yuexiu District, Guangzhou, China |
| Hours | Monday to Friday, 09:00–18:00 (Beijing time, UTC+8) |
| Response time | 1–3 working days |
Email is the only channel; there is no phone support. Put the category in the subject line — correction, bug, feature request, partnership or security — and it reaches the right person faster.
Corrections to the conversion tables are the most useful thing you can send, and the fastest to act on. Include:
Verified corrections are normally applied within three working days. Reports without a source take longer because we have to find the source ourselves, and we will not change a published figure on an unsourced claim.
Include your browser and version, your operating system, the steps that produce the problem, and what you expected instead. A calculation that looks wrong is much easier to diagnose if you paste the exact courses, credits and grades you entered — those numbers are not sensitive and are not stored on our side, so we cannot see them unless you send them.
Describe the situation you are trying to handle rather than the interface you imagine — 'I need to model next semester before registration' is more actionable than 'add a button'. Requests are reviewed in batches; the ones that come up repeatedly get built first.
Mark the subject line 'security'. We acknowledge within 48 hours and will keep you updated through the fix. Please do not publish details of an unpatched issue.
Content collaboration, technical integration and educational-research enquiries are welcome. Send a short outline of what you have in mind; generic marketing solicitations will not get a reply.