Technical incident
Something stopped working, became unavailable, slowed down or started producing errors.
Report an incident →
SUPPORT
Tell us what changed
Tell us what changed
Help us restore the flow
Report an incident, request a service change or ask for help with an application, integration, platform or cloud environment supported by Toqsoft.
For a new project or solution enquiry, please use Contact or Consultation.
HOW CAN WE HELP?
Choose the support path that best matches your situation.
The form below can route each request by type once backend support handling is connected.
Service request
Request a configuration change, approved update, data task or routine technical action.
Request a service →Access & account help
Ask for help with authorised access, roles, sign-in or user provisioning.
Request access help →Data & integration
Report failed synchronisation, delayed messages, API errors or inconsistent operational data.
Report a data issue →Security concern
Report suspicious behaviour or a potential security issue through the approved secure channel.
Read safe-reporting guidance →Existing-client escalation
Escalate a material business-impacting issue using your contract’s named contacts and process.
View escalation guidance →
BEFORE YOU SUBMIT
Good evidence shortens the path to diagnosis.
Share what is safe and relevant. A concise timeline is usually more useful than a long general description.
01What happened?Expected behaviour, actual behaviour and any visible error.
02Who is affected?One user, a team, a location, customers or the full service.
03When did it begin?Date, time, time zone and whether it is continuous or intermittent.
04What changed?Recent release, configuration, access, network, device or data change.
05Can it be repeated?Safe steps, screen name, reference ID and sanitised screenshot details.
06What is the impact?Blocked work, workaround availability and time-sensitive obligations.
SUPPORT REQUEST
Give the support team a clear starting point.
Submit the details below to create a support reference and route your request for initial triage.
Protect sensitive information
Never enter passwords, one-time codes, API keys, tokens, private keys, payment-card details or unredacted personal data in this form.
WHAT HAPPENS NEXT
A visible path from acknowledgement to closure.
Exact commitments depend on the applicable agreement and will be confirmed before launch.
Acknowledge
Confirm receipt and provide a ticket or reference number.
Triage
Validate scope, business impact, severity and responsible team.
Respond
Investigate, request safe evidence and communicate the next action.
Resolve
Restore service or complete the request, verify and document closure.
Support policy placeholders
Service hours: [TO BE CONFIRMED]
Response targets by severity: [TO BE CONFIRMED]
Emergency escalation channel: [TO BE CONFIRMED]
Warranty and support-plan coverage: [TO BE CONFIRMED]
THE RIGHT CHANNEL