We have always had a minimum credit policy for handling support tickets. This is because even for simple questions we need to:
- refresh our knowledge of our customer's website
- properly take in the customer scenario(s)
- discuss scenario(s) with our customer, often slightly beyond the scope of the ticket itself
- often, open up access to the customer website to make changes
- process the ticket properly and professionally
However, it is very understandable that customers can worry that, for very simple questions, the minimum credits of a ticket could be excessive. We also do prefer our customers to put unrelated issues into separate tickets, so costs could mount up.
In the past we have tended to play fast and loose with our own rules. If a ticket really was processed in just a few minutes we have tended to just charge fewer than the normal minimum. This has been done at our discretion, for when 1-5 above haven't really applied. We have also sometimes advised customers post a list of questions together in the same ticket, so long as the questions weren't individually complicated.
From now on the policy will be slightly adjusted. We will continue to reserve the right to adjust our policies in our customer's favour (at our discretion), but we will also formalise this rule:
If a customer wishes to ensure we do batch processing, it would still be necessary to submit all questions in a list within a single post of a single ticket. We would not have any objection to handling this kind of ticket this so long as individual questions within the list aren't particularly complex (e.g. mini projects within their own right).
We always do the best to work the support system in the favour of our customers, while ensuring we don't go too far and make a loss on the system. It has a much lower hourly rate than our agency service, but the automation and pre-payment allows us to achieve that.