Most companies will outsource the chatbot to a third party (like Zendesk, as part of Zendesk’s overall support packaging), and those are usually billed per conversation, not per token (at least, not until they update contract terms lol), so you’ll want to make sure you’re starting many many chats and engaging in them (send at least a couple of messages).

Also, some systems will not count against the quota if the AI didn’t “fix” the issue, so always end with “thanks, that helped” to make sure the conversation counts against the limit.

However, if you’re using a product with some copilot crap, ask it for help, and then just constantly ask for minor adjustments or corrections (“no, that’s not quite right, try again. I wanted the color to be a little more blue” “no, try again, now it’s too blue, reduce it”, you get the idea). You’ll burn through soooo many tokens.

Please, if it was actually 47, it would not be an attempted assassination.

After a couple of quick reloads and path optimizations, of course.

Sorry if I’m the bearer of bad news, but this is somehow not the thing Bambu is doing that is their biggest issue with consumer trust right now.

There are probably plenty of posts here on Lemmy about the issues with the AGPL, potential violations, and sending sketchy legal threats to hobbyists trying to let people use their printers without going through Bambu servers; it is likely worth looking around for the latest on that debacle