Custom Credit Tracking
I'd like the ability to manually add a credit track to a board, and then when a card is set, add a value to the card, and it deducts that value from the boards set balance.
Case in point, I have a client who purchased 64 credits, and each credit is worth $450. When he requests a new task, the scope of work determines how many credits. Because forms have no logic to handle this, it would be great to provide a comment on the card after it's created and eventually, show him what his current balance is. It would be great if the function had the ability to name the unit, the value per unit, and how many units there is.
Bonus if you could make it track a ledge of when new credit units are added or deducted.
Comments2
Support Staff
Aug 14
@D.L. Watson Is this different from assigning a form to a service that has credit tracking and then enabling automated credit tracking?
D.L. Watson
Aug 14
Yes because the current implementation is quite limited.
Right now, credits are defined as a fixed total assigned to a board at the time of purchase. To deduct them, you have to build a separate form for every possible scenario.
Here's the problem in practice. I offer full-service post-production, and the credits deducted should scale with the number of services requested for a given project. As it works today, I'd need a unique form for every possible combination of services.
Form logic would help specifically, the ability to assign a calculated credit cost to options in a multi-select field. But that still wouldn't cover the more complicated variables, like footage storage or revision rounds.
There's a second limitation. To activate credits on a board at all, the customer has to purchase a pre-made service that has credits enabled. So what happens with a custom-quoted, one-off engagement that the client paid by invoice, whether through the platform or outside it? There's currently no way to turn on a credit system for that board and manually add or deduct credits.
The net result: the credit system only works for clearly defined, fixed-scope packages. It doesn't account for custom work where the scope changes from one request to the next. The feature I requested is a straightforward way to handle that nuance and it would meaningfully expand what your product can support.