Credits Deduction
Prasad S
Deduct credits only when we accept the revisions and suggestions. Deducting credits for lousy suggestions and revisions is not acceptable (and such out is mediocre or bad nearly 70% of the times and we keep losing credits just like that).
Johnathan Lightfoot
So the proposal is: generate the revisions, view the suggestions, screenshot or copy anything useful, then declare “not accepted” and pay nothing?
Brilliant. A fully honor-system billing model for AI compute. What could possibly go wrong?
Credits are not an applause meter. They pay for the model running, the infrastructure, the storage, and the service being available. If the output quality is bad, that’s fair feedback. Gamma should improve that. Or maybe your prompting skills needs some serious work?
But “only charge me when I personally decide I liked it” basically turns the platform into unlimited free trial with extra steps.
I too would like restaurants to only charge me after I decide the meal emotionally fulfilled me, but sadly society remains hostile to innovation.
Nik Payne (Gamma design)
Totally hear you, Prasad S. It’s frustrating to pay credits for suggestions that don’t end up being usable, especially if you’re rejecting most of them. I’ll pass this along to the team.
Quick question so we can scope it right: when you say “accept,” do you mean a specific button/action in the UI, and would you want credits deducted per accepted suggestion only, or only once you accept the final revised version?
Prasad S
Nik Payne (Gamma design) A specific "accept" and "reject" button in the UI will be helpful. The deduction can be for 'per accepted suggestion'. Btw, don't hide the total credits remaining inside the log-in credentials. Make it prominently visible ALWAYS so that we can keep a tab on how much credits we are burning. It's cumbersome to go to log-in credentials at the bottom to check the remaining credits.