Enterprise Service Desk
Raise technical requests, monitor support progress, and connect directly with our engineering team.
SLA Priority Levels
Our commitment to keeping your business-critical workflows online 24/7/365.
Critical
Production Down / Complete System Outage
- ERP System Failure
- CRM Database Offline
- Payment Gateway Loop Failure
High
Major Business Impact / Heavy Degradation
- API Sync Blockages
- Order Ingestion Slowdowns
- Partial Data Access Errors
Medium
Limited Functionality / Specific Workarounds
- Non-Critical Feature Bugs
- Report Compilation Errors
- Minor Splicing Delays
Low
General Inquiries / Enhancement Suggestions
- Minor UI Alignment Tweaks
- Feature Requests
- General Configuration Queries
Supported Architectures
Select your deployment suite to pre-configure and route your ticket directly to the assigned engineering pod.
Select Issue Category
Select the focus area to dynamically configure forms and match severity protocols.
New Support Ticket
Register your technical issue below to queue it in our systems pipeline.
Issue Resolution Lifecycle
Track how your ticket moves from registration to testing and resolution under our engineering pods.
Track Active Support Ticket
Lookup real-time engineer logs, assigned priority queues, and expected SLAs.
Type a valid registration key to load the systems interface.
Enterprise Support Analytics
Real-time telemetry monitor of team throughput, SLA compliance metrics, and issue queue statuses.
Resolution SLA Performance
Support Request Inflow (Past 7 Days)
Knowledge Base & Documentation
Resolve common configuration issues immediately using our self-service guides.
How do I synchronize inventory caches between legacy SAP instances and Arktek ERP?
Arktek ERP relies on dynamic streaming endpoints via the `SAP-Link` connector. To sync legacy databases: First, verify the client credentials in your settings directory. Ensure the background listener `arktek-sap-worker` is active under Kubernetes. Caches sync in real-time, holding average validation times to under 100ms.
What are the security configurations for Pinecone RAG databases during custom AI training?
We deploy RAG engines within containerized VPC networks, setting secure access via encrypted tokens in your environment parameters. No external API queries can bypass the internal OAuth2 authentication firewall. Database indexing is isolated with zero outbound network routing.
Why is my API webhook returning a 403 Forbidden payload limit warning?
A 403 response on API integration channels usually occurs when request volumes exceed the SLA threshold set in your contract limits (e.g. 5000 requests per minute). If your transaction scale has expanded, please raise a ticket to request a quota expansion from our engineering pod.
Need Immediate Assistance?
For absolute production-down critical blocks, skip the queue and contact our engineering hotline directly.