“Nothing works” is an understandable feeling and a very broad technical assignment. A specialist does not yet know whether the whole portal fails to open or one button fails in one record. A useful description narrows the search before anyone connects to investigate.
This applies to Bitrix24, a website and other business systems. You do not need to become a developer: show an observable sequence.
Describe one action
An illustrative example: an employee opens a specific task, adds a file and presses send. An error message appears instead of an attachment. That can be checked; “files are broken” does not provide the same information.
Write short steps from an open page to the failure. Include the relevant section address and the employee’s role. Do not put passwords, access keys or customers’ personal details into a group conversation.
If repeating the action could send an email, create an order or charge money, do not repeat it merely to record a video. First agree a safe check with the responsible specialist.
Separate expectation from fact
State separately what should have happened under the agreed workflow and what actually happened. Copy the error text accurately if it contains no secrets.
A screenshot helps when it shows the relevant place and message. Before sharing, exclude unnecessary tabs and hide information not needed for diagnosis. Exporting the entire customer database is usually not a description of one error.
Do not present a hypothesis as an established cause. “It started after a setting changed” is an observation; “the update definitely broke everything” is still a theory.
Include timing and scope
Record the date and time with the time zone. For a team in Kazakhstan, that helps when working with support and partners in other regions.
Clarify who encounters it: one employee or several, one record or many, the web version or mobile app. Include the device, browser or application version when helpful for reproduction.
For Bitrix24, use the official checklist of information for support. For general unavailability, also check the official service status. Do not make risky configuration changes based on random search advice.
Keep one path for follow-up
Name someone who gathers clarifications and updates the team. Otherwise several employees may send different descriptions and receive incompatible recommendations.
After a fix, repeat the agreed safe scenario. Check that the intended action succeeded, rather than merely that the message disappeared. Record what was checked and any remaining limits.
QQDev provides Bitrix24 implementation services. The implementation page is a place to discuss a problem in a configured workflow and an appropriate next step. Bring anonymised steps and the expected outcome: that is more useful than ten messages saying “please check urgently”.