Customer support

Already working with us? Raise a ticket below and you will get a ticket ID straight away, on screen and by email. If production or dispatch is stopped, call support as well.

Support line

+91 73494 16661

Call for anything that is stopping production. Please raise a ticket too, so the issue is tracked and nothing is lost between calls.

Not a support question?

For new projects, quotes or extending your system, contact sales: bdo@ajinkyatechnologies.in, +91 70101 10805.

Raise a ticket

What to include

These details let the first engineer who reads your ticket start work without coming back to you.

The product or system and the site or plant it runs at
What you expected to happen and what happened instead
The screen, module, device or report involved
Any error message, word for word
When it started, and whether anything changed just before
How many users, lines or shifts are affected

What happens next

1. You raise a ticket. The form logs it and you get a ticket ID on screen and by email.
2. An engineer picks it up. Critical tickets are flagged as urgent to the support team. We reply by email or phone, as you choose.
3. We work it to a fix. Reply to the confirmation email to add screenshots or details. Quote the ticket ID on calls so nothing gets lost.

Choosing a severity

Critical:: production, dispatch or a safety function is stopped. Call as well.
High:: a key function fails and there is no workaround.
Medium:: something is wrong but work can carry on.
Low:: a question, a report tweak or a change request.

Customer support

Already working with us? Raise a ticket below and you will get a ticket ID straight away, on screen and by email. If production or dispatch is stopped, call support as well.

Support line

+91 73494 16661

Call for anything that is stopping production. Please raise a ticket too, so the issue is tracked and nothing is lost between calls.

Not a support question?

For new projects, quotes or extending your system, contact sales: bdo@ajinkyatechnologies.in, +91 70101 10805.

Raise a ticket

What to include

These details let the first engineer who reads your ticket start work without coming back to you.

The product or system and the site or plant it runs at
What you expected to happen and what happened instead
The screen, module, device or report involved
Any error message, word for word
When it started, and whether anything changed just before
How many users, lines or shifts are affected

What happens next

1. You raise a ticket. The form logs it and you get a ticket ID on screen and by email.
2. An engineer picks it up. Critical tickets are flagged as urgent to the support team. We reply by email or phone, as you choose.
3. We work it to a fix. Reply to the confirmation email to add screenshots or details. Quote the ticket ID on calls so nothing gets lost.

Choosing a severity

Critical:: production, dispatch or a safety function is stopped. Call as well.
High:: a key function fails and there is no workaround.
Medium:: something is wrong but work can carry on.
Low:: a question, a report tweak or a change request.

Customer support

Support line

Not a support question?

Raise a ticket

We value your privacy

Customer support

Support line

Not a support question?

Raise a ticket

We value your privacy