Find answers fast or talk to a DO ALL specialist.
Ask for the guidance relevant to your application, role and deployment.
Ask the team →Describe the process you are trying to complete and where you need help.
Ask the team →Use your agreed incident channel for outages, or ask the team for the appropriate status information.
Ask the team →Confirm the right support channel and include the affected process, timing and business impact.
Ask the team →Discuss role-based onboarding, refresher sessions and administrator learning needs.
Ask the team →Confirm your contracted coverage, contacts and escalation process before an urgent issue occurs.
Ask the team →This page explains how to seek DO ALL assistance and what to clarify when evaluating customer support software. Help desk software, a ticketing system and a full service desk are related concepts, not interchangeable promises of included functionality.
A support ticket system records an issue, owner, priority and resolution. Complaint management software may require additional review and escalation. Confirm intake channels, service targets and closure evidence; the public enquiry form is not a ticket-tracking portal.
Service desk management can include incidents, service requests and change responsibilities. Scope supported systems, coverage, escalation and ownership with the support team. Customer support software should not promise response times that are absent from the agreement.
A customer portal can expose authorised case status and self-service requests. Knowledge base software needs approved articles, review dates and access control. Discuss these requirements during discovery; this website currently offers guidance and contact routes rather than an authenticated customer portal.
Give the support team enough information to assess business impact and reproduce the issue without exposing sensitive data.
Include the affected module, approximate time, steps taken, expected result and the actual message shown.
Explain who is affected and whether work can continue. Share redacted screenshots or record references through the agreed channel.
Keep related updates together, nominate a contact for testing and confirm the business workflow after a fix or workaround.
Use the approved recovery process for your application or contact your authorised administrator. Never send your current password through a website enquiry.
Ask your authorised administrator to use the user-management process for your deployment. Confirm the appropriate role and access approval before inviting someone.
Describe the desired workflow, business impact and current workaround through your agreed support channel or the contact form. Scope and delivery timing are assessed separately.
Provide the affected process, impact, time, reproduction steps and any visible error. Include a contact who can help validate the result.
Keep updates on the same thread or ticket where possible. Duplicate reports can split context and make coordinated investigation harder.
Use the escalation route in your support agreement and state the impact clearly. A general website enquiry is not a substitute for a contracted emergency channel.
Describe the desired workflow, users affected and current workaround. Separate enhancement requests from incidents so each can be assessed appropriately.
No authenticated ticket portal is provided here. Use the published contact routes for assistance and agree case tracking, channels and service targets with the team.
Test intake, categorisation, assignment, escalation, customer visibility, resolution and reopening. Include an uncertain knowledge-base answer and verify that access rules prevent one customer from viewing another customer case.
Book a personalised demo and see how DO ALL unifies your teams, data and decisions.
