Existing client or supported system
Use the support request path for faults, access changes, maintenance questions and work covered by an active written arrangement. Include the relevant project or system reference if available.
Support for existing work
Give the issue a clear path from impact to resolution.
The Support route is for existing-project issues, access requests, maintenance questions and controlled changes. Send the affected system, observed behaviour, business impact and safe reproduction details. Availability, priority handling, response commitments and included work depend on the applicable written support arrangement; this page does not imply continuous monitoring or 24/7 coverage.
Clearscope and responsibility
Usefulsystems people can operate
Durableownership after launch
Why it matters
Existing client or supported system
Use the support request path for faults, access changes, maintenance questions and work covered by an active written arrangement. Include the relevant project or system reference if available.
CHAPTER 01 / Choose the route
Existing issue or new project?
New feature or material change
Describe the desired outcome and current behaviour. The request may require assessment and a new scope before implementation.
New organisation or project
Use Start a Project so the need can be diagnosed without mixing it into an existing-client support queue.
Security-sensitive concern
Use the designated contact route and share the minimum necessary information. Do not place passwords, secret keys, payment data or sensitive personal information in a general form.
CHAPTER 02 / Describe impact
Priority starts with consequence, not capital letters.
The labels below help describe impact; they do not create a guaranteed response time. Contractual priority definitions and availability take precedence where they exist.
Critical impact
A production service is unavailable or a serious security, safety or data concern is suspected, with no reasonable workaround known. State who is affected and what immediate containment has occurred.
Significant impact
An important function is failing or materially impaired, but part of the service remains available or a temporary workaround exists.
Standard issue
A limited defect, content correction, usability issue, access request or question that does not prevent core operation.
Planned change
A new behaviour, integration, content set or improvement that should enter assessment and scheduling rather than incident handling.
CHAPTER 03 / A useful request
Send evidence that helps reproduce the problem safely.
Where
Name the website, page, workflow or device and provide the relevant URL where appropriate.
What happened
Describe the expected result, the observed result and the steps immediately before it occurred.
Who and when
State the affected user group, first-known time, frequency and whether the issue can still be reproduced.
Safe evidence
Screenshots, exact error text and browser or device details can help. Remove personal, confidential or secret information before attaching anything.
Business effect
Explain what work, customer action or decision is blocked and whether a safe workaround is available.
CHAPTER 04 / What happens next
Triage separates defect, access, content and change.
1. Receipt
A functioning support form should confirm successful delivery and return a reference that can be used in follow-up.
2. Triage
The request is reviewed against its impact, supplied evidence, affected system and applicable support arrangement.
3. Clarification or containment
More information or a safe temporary action may be requested before the underlying cause is confirmed.
4. Route
The item proceeds as support, warranty assessment, account access, content correction, third-party issue or separately scoped change.
5. Record
The resolution, limitation, follow-up or commercial next step should be stated clearly enough for the relevant people to act.
CHAPTER 05 / Before submitting
A few safe checks can reveal the shape of the issue.
Do not make destructive changes or bypass security controls. If the system is safe to use, these observations can help distinguish a local device issue from a wider service problem.
Confirm the exact address
Check that the expected production page or approved application is open.
Record the message
Capture the complete visible error and time before refreshing or repeating the action.
Compare carefully
If permitted, note whether another authorised user or device sees the same behaviour.
Avoid repeated submissions
Do not repeatedly send a payment, form, automation or data-changing action if its outcome is uncertain.
CHAPTER 06 / Access and security
Never solve access by sharing a secret in plain text.
No passwords in forms
A support request should not ask for account passwords, recovery codes, private keys or complete payment credentials.
Verify authority
Access additions, removals and privilege changes may require confirmation from an authorised project contact.
Use limited access
Where temporary technical access is required, its purpose, scope and removal should be considered.
Preserve evidence
For suspected security or data incidents, avoid unnecessary changes that could destroy useful records; use the designated escalation route.
CHAPTER 07 / Coverage and escalation
The agreement defines what the support relationship includes.
Maintenance, monitoring, content updates, third-party administration, enhancements and emergency availability are separate responsibilities unless the written arrangement joins them. If impact changes after submission, update the existing reference rather than opening unrelated duplicates.
Warranty question
Use the warranty guide to distinguish a possible defect from an enhancement, content change or external-service issue.
Cancellation or refund question
Use the refunds and cancellations page for the assessment pathway and contractual context.
General commercial question
Use Contact and include the relevant proposal, invoice or project reference without exposing confidential material unnecessarily.
Continue through the ga applications system.
Each route answers a different operating question while retaining the same standards for evidence, responsibility and a usable next step.
Route 01
About
See how GA Applications approaches websites, business systems, automation and responsible digital design as one connected project.Route 02Process
Follow GA Applications' eight-phase path from diagnosis and scope through design, build, launch, handover and measured improvement.Route 03Pricing
Understand how scope, content, integrations, risk and support shape a GA Applications estimate without misleading one-size-fits-all packages.Route 04Faq
Direct answers about GA Applications services, delivery, pricing, ownership, SEO, AI, support, locations and independent concepts.Route 05Warranty
Understand how a potential defect is distinguished from a change and assessed under the applicable GA Applications agreement and law.Route 06Refunds Cancellations
Understand how a cancellation or refund request is reviewed against completed work, commitments, third-party costs, written terms and law.Route 07Chinkara Maven
Explore Chinkara Maven as GA Applications' guided assistance layer for approved knowledge, clear permissions and human-reviewed action.Questions worth resolving
What to clarify before committing.
Is support available 24/7?
Not by default. Support hours, channels, monitoring and any response commitments are governed by the applicable written arrangement.
What should I include in a support request?
Include the affected system, expected and observed behaviour, impact, timing, safe reproduction steps and sanitised evidence. Do not include passwords or sensitive personal information.
Is a requested change covered as support?
It depends on the applicable scope. A defect in agreed work, routine maintenance item and new feature are different categories and may follow different assessment or commercial paths.
Can I send an attachment?
Only use an attachment control if the support form provides one and accepts the file. Remove secrets and unnecessary personal information first; otherwise describe the evidence and request a safe transfer method.
Existing-system support
Report the impact with safe, reproducible detail.
Use the support route identified in your agreement where one exists. Otherwise contact GA Applications and include the project reference, affected system and business impact.