Talk to the team that built it
No ticket queue between you and an engineer. Tell us what broke and we will tell you who is on it and when to expect a fix, whether you are live on production or still deciding what to build.
Support Hours
Teams in India and the US: we overlap with most working hours across IST, GMT, and PST.
Ways to Reach Us
Priority & Response Times
Every request is triaged into one of four levels. The times below are our target for a first human response, not for a resolution. We will tell you what we know and what happens next.
Production is down or unusable for all users, data is at risk, or there is an active security incident.
4 business hoursA major feature is broken or badly degraded for many users, but a workaround exists.
1 business dayA minor bug, a cosmetic defect, or a question about how existing functionality works.
2 business daysEnhancement requests, documentation updates, and general technical advice.
5 business daysWhat Support Covers
Included
- Defects in delivered work, free of charge, for 30 days after each milestone is delivered.
- Questions about how the systems we built for you work.
- Production incidents on infrastructure we maintain under an active retainer.
- Security patches and dependency updates on maintained projects.
- Handover help: access, credentials, documentation, and deployment walkthroughs.
Quoted separately
- New features, scope changes, and redesigns: these are quoted as a change request.
- Outages at third-party providers such as AWS, Stripe, or payment gateways.
- Defects introduced by another team editing the codebase after handover.
- Infrastructure and licence costs, which providers bill to you directly.
- Projects Panicle Tech did not build, until a code and infrastructure audit is complete.
Before You Write In
Six details that turn a two-day back-and-forth into a same-day fix. Send what you have. Do not wait until the list is complete.
What you expected to happen, and what happened instead.
The exact URL, screen, or API endpoint where it happened.
A timestamp with timezone, plus request IDs or log output if you have them.
Steps to reproduce: the shorter the list, the faster the fix.
Environment: production or staging, and the browser or device where relevant.
Roughly how many users are affected, so we can set the right priority.
Common Questions
01How do I report an urgent production issue?
02Is support included after my project is delivered?
03What does a maintenance retainer cover?
04Do you support projects you did not build?
05Can you sign an NDA before we share details?
06Do these response times apply to my contract?
07How do I request a new feature instead of a fix?
Still stuck?
Send us what you have. Even a screenshot and a rough description is enough to start. We will come back with the next step, not a ticket number.
Support is provided under our Terms & Conditions and Privacy Policy. Where a signed Statement of Work or service agreement sets different terms, that agreement takes precedence.