After a Booking Ninjas Support Case is submitted, the case becomes the main record for that issue or request so the team can review the context and follow up in one place.
The exact path depends on the case. Some items can be answered quickly. Others need clarification, investigation, testing, or a separate scope decision.
What Happens During the First Review?
- Review the description. The team checks the issue, affected workflow, examples, and business impact.
- Identify missing context. If the case is too broad or an example is missing, the next useful step may be a question.
- Decide the next action. The case may need an answer, investigation, testing, coordination with another person, or a review of whether the request changes the current setup.
- Keep the record updated. Important findings and follow-up should stay connected to the same case.
Important: a response can acknowledge the case, ask for clarification, or explain the next step. It does not mean the issue has already been fully resolved.
Why Might Booking Ninjas Ask for More Information?
The same symptom can have different causes. The team may need an example record, affected user, time of the issue, screenshot, expected result, or steps that reproduce the problem.
Adding that information to the existing case keeps the history together and helps avoid repeating the same explanation in several channels.
What if the Request Changes the Current Setup?
A support review may show that the live system is working as configured, but the client wants it to behave differently. That is different from correcting unexpected behavior.
A new workflow, integration, data migration, major configuration change, or additional development may need separate review and scope. See What Happens When New Requirements Appear? and What May Require Additional Development?.
How Should Follow-Up and Testing Work?
Keep important information about the tracked issue in the Support Case. WhatsApp or email can still be used for direct communication, but the case should hold the details needed for investigation and decision-making.
If the case results in a change, the affected workflow should be tested before the change is treated as ready. The exact test depends on which users, data, automation, integrations, or reports are affected. See How Changes Are Tested.
When Is the Case Complete?
A case can be treated as complete when the question has been answered, the issue has been resolved, an agreed workaround or decision has been recorded, or the item has clearly moved into another workstream that will be handled separately.
The important point is that the tracked item should end with a clear outcome rather than disappearing into an informal message thread.
Sources and Further Reading
- What Support Is Available After Launch? — explains the Booking Ninjas post-launch support boundary.
- Salesforce Help: Manage and Work with Cases — describes updating case details and communications through resolution.
- Salesforce Help: Set Up and Manage Cases — explains the role of cases as structured records for customer issues.
External sources support general case-management concepts. The exact Booking Ninjas handling path depends on the client, case, and implemented scope.