How can we help you today?
Answers about working with ElvixTech, from starting a project to support after launch, and a clear way to reach a person when you need one.
Popular:Start a projectReport a problemWho owns the code
- 26
- Answers
- 6
- Topics
- 1
- Min to read the longest
Browse by topic
Getting help takes four steps
You are never stuck in a queue of bots. Every path ends with a person.
- 01
Look it up
Search above or browse a topic. Questions about starting, how projects run, support and ownership are answered here.
Browse topics → - 02
Ask us
Use the contact form and pick the category that fits. For a problem with something we built, choose “Support for an existing project”.
Contact support → - 03
We reply
A person on our team reads your message and replies to the email address you give, with an answer, a few questions, or a time for a call.
- 04
We follow through
For a product we built, that means bug fixes, patches and enhancement sprints, depending on your support tier.
About support →
5 answers
Getting started
Starting a project, what to tell us first, and how quickly work can begin.
4 answers
Services and timelines
What we build, which package fits your stage, and how long projects usually take.
5 answers
Working with us
Engagement models, how a project runs and how we deliver.
3 answers
Support after launch
What support covers and how to report a problem properly.
4 answers
Security, legal and ownership
NDAs, who owns the work, security practice and your data.
5 answers
Technology
The stack we use, app store publishing, and working with your systems.
Still need help?
Write to us and a person will reply to the email address you give us. For a problem with something we built, choose “Support for an existing project”. The button below does that for you.
- Emailhello@elvixtech.com
- Phone+91 99791 52048
- WhatsAppMessage us
- LinkedIn@elvix-tech-1b6123405
- Instagram@elvixtech
Working hours: Monday – Saturday, 9:00 AM – 6:00 PM IST
Before you write to us
If you are reporting a problem, these details let us start on it straight away.
- 1The name of the product or project, and whether the problem is in production or a test environment
- 2What you expected to happen and what happened instead
- 3When it started and how often it happens
- 4The steps to reproduce it, if you know them
- 5Error messages, logs or screenshots
- 6How much it affects your users or your business