Service Request
For planned assistance, configuration changes, access-related work, reviews or other defined technology requests.
Submit a request →Support Center
Practical support when technology needs attention.
Use the right support path for the situation — from a service request or operational issue to a security concern or a question about an existing engagement.
Support approach
For urgent or security-sensitive matters, include the business impact and the best way to reach the responsible contact.Clear ownership · Defined next steps · Useful updates
Choose a path
Start with the type of help you need.
A good support process gets the issue to the right person without making you repeat the same information several times.
Operational Issue
For a system, application, cloud or infrastructure issue affecting normal business operations.
Describe the issue →Security Concern
For a suspected security event, vulnerability, suspicious activity or control concern that needs attention.
Security guidance →Engagement Support
For questions, follow-up actions, deliverables or coordination relating to an active Sivartha engagement.
Contact the team →How support works
Keep the first response useful.
When you contact us, we focus first on understanding the situation, business impact and what has already been tried. From there, the next action can be agreed rather than guessed.
01Capture — what happened, when it started and what is affected.
02Assess — urgency, impact, dependencies and available evidence.
03Act — troubleshoot, coordinate or define the next technical action.
04Close — confirm the outcome and record follow-up actions where needed.
Include these details
- System, application or service affected
- Business impact and number of users affected
- Time the issue was first noticed
- Error message, screenshot or relevant log where appropriate
- Recent change, deployment or maintenance activity
- Your preferred contact method
Security-sensitive matters
Do not put passwords or secrets in a support request.
If you suspect an account compromise, exposed credential, malware event or other security incident, describe the symptoms and business impact without sending passwords, private keys, tokens or other secrets.
Service desk enquiry
Tell us what needs attention.
This form prepares an email enquiry. It does not create a ticketing record until the request is received and acknowledged.
Support boundaries
Clear expectations make support easier.
Planned work
Configuration changes, reviews, migrations and improvement work may need a defined scope and agreed schedule rather than being treated as an incident.
Third-party services
Where an issue sits with a cloud, software or telecom provider, we can help with diagnosis and coordination while the provider's own support process remains part of the resolution path.
Access & evidence
Support may depend on appropriate access, logs, screenshots, architecture information or other evidence. Access should be provided through approved channels.
Security & privacy
Only share information needed to investigate the issue. Never include passwords, MFA codes, private keys or active credentials in an email or form.
Frequently asked questions
Support questions, answered simply.
What should I include in a support request?
Include the affected system, what you expected to happen, what actually happened, when it started, business impact and any useful error message or evidence.
Can I request planned technology work through Support?
Yes. Use the Service Request path for planned work. Larger changes may be handled as a separately scoped engagement.
What if the issue is urgent?
Select the urgent priority and clearly describe the service disruption and business impact. For security-sensitive matters, avoid including secrets and use the security contact path.
Will submitting the form automatically create a ticket?
No. The static website prepares an email enquiry. A request becomes part of the support workflow after it is received and acknowledged by the appropriate team.
Can Sivartha work with our existing IT team?
Yes. Support can be structured alongside internal IT teams, vendors or other technology partners, with responsibilities agreed for the engagement.
Need a broader conversation?