Where to check usage#
Before trying again, record the remaining allowance, reset time and product responsible for usage. Do not expect a short question and a long video to consume the same amount.
A legacy account may have a different view. Match the interface to your plan; this chapter does not turn historical message counts into universal current limits.
Credit, caps and extra charges#
- Check whether the included allowance is exhausted or a financial cap has been reached.
- If the task can wait, note the reset shown in your account.
- If you need to continue, compare the extra cost with the value of finishing the task.
- Before enabling recurring top-ups, set your own budget and review the available cap.
For an unexpected charge, download the receipt. Distinguish subscriptions, credit top-ups and separate API usage. Do not automatically attribute a large charge to a model error.
A short diagnostic workflow#
| What you see | First useful check |
|---|---|
| Payment prompt despite a subscription | Compare your signed-in account with the purchase receipt. |
| Missing feature | Record platform, plan, region and app version; compare with the guide’s scope. |
| Attachment will not load | Try one small file of the same type without sensitive content. |
| Earlier instructions are ignored | Summarise the relevant context and ask for one clear task. |
| The whole service is unresponsive | Check service status and try one simple new request. |
Change one variable at a time. Replacing the file, browser, account and prompt together will obscure the cause. Save unsent text before clearing local data.
Long conversations and incorrect answers#
Usage and quality are separate issues. A shorter request can be clearer, but does not guarantee accuracy. If topics become mixed, make a working summary and start a new conversation with it. Check that important earlier details survived.
Prepare a handover for continuing this task: goal, confirmed facts, decisions, open questions and required sources. Add no new claims. Mark everything that still needs verification.
Before using the summary, compare numbers, names and constraints with the original. Starting a new chat is a workflow choice, not a rule for every correction.
Prepare a useful support report#
Record the exact time and time zone, platform, version, plan, error text and shortest reproducible sequence. For billing, include the receipt number. Remove private content from screenshots.
Problem: [what fails] Where: [web/iOS/Android/X/API, version] When: [date, time, zone] Expected: [result] Actual: [exact error] Reproduction: [short steps] Already checked: [account, usage, service status]
For attachments, continue to Files; for payments, see Plans. This template prepares a report; it does not send anything for you.