A useful Booking Ninjas Support Case explains what happened, where it happened, what you expected, and how the issue affects the business.
You do not need to diagnose the technical cause. Clear operational details are more useful than guessing what is wrong behind the screen.
What Should You Include?
- A clear summary. State the issue or request in one sentence.
- The affected workflow or area. Explain where in Booking Ninjas the issue happens.
- Expected and actual results. Say what you expected and what happened instead.
- Steps or examples. Include the actions that led to the issue when you can reproduce it.
- Affected users or records. Give enough context to identify a useful example without exposing private credentials.
- Screenshots or supporting evidence. Add them when they make the issue easier to understand.
- Business impact. Explain what work is blocked, who is affected, and whether a workaround exists.
Example: “Front-desk users cannot confirm a reservation after the deposit is recorded” is more useful than “Booking is broken.”
How Should You Describe Impact and Urgency?
Describe what the issue is doing to the operation instead of only writing “urgent.” For example: no users can complete bookings, one team is blocked, one customer record is affected, or the issue can be worked around temporarily.
Service-management guidance commonly separates impact from urgency. Impact describes how much of the business is affected, while urgency describes how quickly the effect matters. Giving both kinds of context helps the support team understand the situation without relying on a vague priority label.
What Should You Avoid?
- Passwords or private credentials. Do not place them in a case description or screenshot.
- Several unrelated problems in one case. Separate topics are easier to track separately.
- Only a screenshot with no explanation. Add the expected result and the action that led to the problem.
- Only the word “urgent.” Explain the real business effect and whether a workaround exists.
What if You Already Sent a Direct Message?
If you already contacted Booking Ninjas through WhatsApp or email and the issue needs investigation or formal follow-up, open a Support Case and place the important context there.
You can still use direct messages for coordination, but the case should become the main record for the tracked issue. If a case already exists, refer to it instead of creating a separate message history.
What Happens After You Submit?
The team reviews the case and may ask for more information before it can be understood or tested. Read What Happens After You Submit a Support Case? for the next part of the process.
Sources and Further Reading
- How Changes Are Tested — explains why clear scenarios and expected results matter when a change needs testing.
- Salesforce Help: Case Management Best Practice Guide — explains the value of capturing relevant case details and keeping a structured case process.
- Atlassian: How Impact and Urgency Are Used to Calculate Priority — explains the general distinction between business impact, urgency, and priority.
External sources support general service-management practices. Booking Ninjas may use different internal fields or workflows for its Support Cases.