The short answer
Whizi support is one email address, [email protected]. The support page at whizi.io/support puts that address next to written guidance, and inside the app the route is Settings, then Support & legal, then Contact support, which opens the same page. The support page states that the inbox is monitored in English and that Whizi typically responds within two business days.
On the website there are four routes, and they are not interchangeable:
| Route | Where it is | What it is for |
|---|---|---|
| [email protected] | Anything. This is the address the Terms and the Privacy Policy both name | |
| Support page | whizi.io/support, linked from the site footer and from Settings under Support & legal | Written guidance on sign-in, subscriptions, deletion and AI output, with the same address at the top |
| Send feedback | Settings, under Support & legal, above Contact support | A bug report or a feature request, sent from inside the product with your setup attached |
| Report this chat | The Report control on a public /share link | Content on a conversation someone shared with you, reportable without an account |
For problematic model output the support page asks for one specific thing: email [email protected] with the subject line "AI output report", and include the model used, the approximate date and time, what was problematic, and a screenshot or the relevant excerpt if it is safe to share.
What to put in the first message
Nothing about a chat is attached to an email you write, so the reply is only as good as what you paste in. Include these five things.
The exact error text, character for character. Paste it exactly. A paraphrase loses the string that identifies it.
Any number you can see. Some strings render a live value into a placeholder. Account deletion failed ({status}). carries a real HTTP status where {status} sits, but it reaches only the browser console and network tab: the Settings screen shows Your account could not be deleted. Please try again, or contact support. instead. Quote whichever one you have, with the number intact if there is one.
The error code, if you can see one. Most errors from the current backend come back as JSON with a code beside the message, so the code sits in a browser network trace even when the screen shows only the sentence. Some older routes return the sentence alone, and a few messages are generated in the browser and have no code at all.
The model you had selected, and the approximate time. Both narrow the search on the server side, and the support page already asks for them on an AI output report.
Write from the address on the account. The support page asks for this twice, once for sign-in problems and again for deletion requests, and adds the device type, operating system and a short description of what happened for the sign-in case. The Privacy Policy is blunter about why: Whizi may need to verify your identity before completing a rights request.
Which error strings are worth pasting
These are the strings the docs already route to support, because nothing on your side clears them. Each row links the page that owns the full explanation.
| String | What it is | Owned by |
|---|---|---|
Something went wrong. Please retry. | HTTP 500 internal_error, the catch-all for any unhandled backend error. It identifies no cause, so retry once and then send it in | message not sending |
User not found. | The account record behind your session is gone. There is no self-serve repair | login and account access |
Account deletion failed ({status}). and Export request failed ({status}). | The raw errors behind the Settings toasts, with the HTTP status filled in | login and account access |
Generation is paused on this account after repeated requests that Whizi cannot fulfil. It reopens automatically. Contact support from Settings if you think this is wrong. | HTTP 429 content_policy_locked, a lockout earned by repeatedly tripping the generation screener | rate limits |
Failed to create Stripe checkout session. | The checkout call failed and the backend supplied no message of its own | payment declined |
Media could not be stored. and Stored media metadata was invalid. | The storage write returned no object, or the stored row could not be read back | file upload failed |
Realtime voice is not configured yet. Please try again later. | HTTP 503, returned when the voice provider key is not set on the server | voice mode not working |
The image content policy refusals carry the instruction inside the string, each ending "If you think this was a mistake, contact support from Settings." They are listed with their codes on image generation failed. A share link blocked at creation time says the same thing, in the message This conversation cannot be shared publicly. Contact support from Settings if you think this is wrong. returned as HTTP 400 content_policy_share_blocked.
The in-app feedback form, and how it differs
Settings has a Send feedback row above Contact support, with the subtitle "Tell us what broke, or what you wish Whizi did." It opens a form, not an email client, and it is a different queue from support: product feedback on one side, account and billing problems on the other.
What the form does: three kinds to choose from, labelled "Something broke", "I have an idea" and "Something else"; a message box that accepts up to 4,000 characters and truncates anything past that; and an optional email field for a reply, separate from the account address on purpose.
What rides along without you typing it, quoted from the line under the box: "Sent with your browser, window size, language, and selected model so we can reproduce it. Nothing from your chats is attached."
The route accepts 6 submissions per minute per user, and going past that returns the message "That is a few in a row. Give it a minute, then send this again." If the feedback route is unavailable the form says so and offers the other door: "Feedback is not available right now. The support page still works."
What support is the only route to
Some requests have no self-serve equivalent anywhere in the product.
| Request | Why support | Detail |
|---|---|---|
| Changing the email address on an account | There is no setting for it | switch account email |
| A credit balance that looks wrong rather than spent | The usage rows behind a balance are kept for 400 days, but no screen in the product shows them | out of credits |
| A charge whose amount looks wrong | The Terms give one address for it | invoices and receipts |
| Anything resembling a team or multi-seat arrangement | No team plan exists to self-serve | team accounts |
| A content policy lockout you believe is wrong | It reopens automatically, but no duration is published | rate limits |
User not found. when you did not delete anything | There is no self-serve repair | login and account access |
What support has not promised
No refund is promised anywhere in the Terms. The Cancellation clause names [email protected] for anyone unsatisfied, and cancellation takes effect at the end of the current paid term. What that route does and does not promise is set out on refunds.
No turnaround is published for a rights request. The Privacy Policy says you may have rights to access, correct, delete, or receive a copy of personal information, and that Whizi may need to verify your identity first. It attaches no number of days to any of it.
No phone number and no live chat appear on the support page, in the Terms, or in the Privacy Policy. Those three between them publish an email address, the support page URL, the account deletion page, and a postal address: Whizi, 238 Featherstone Crescent, Kitchener, Ontario N2R 1Z3, Canada. There is no ticket portal to log into and no chat widget.
Support cannot undo an account deletion. Deletion is permanent, and what it removes is listed on what Whizi does with your data.
What never to send
The support page carries this as a red panel: "Never email us your password, full payment-card details, authentication codes, or sensitive prompts and files. Whizi support will never ask for your password."
The same page adds one rule specific to AI output reports: remove personal, confidential, or regulated information before sending the report, and if the output suggests an immediate danger, contact the appropriate local emergency service rather than support.
- The support address is [email protected], named in the Terms and the Privacy Policy
- The support page is whizi.io/support, reachable from the footer and from Settings
- The inbox is monitored in English, with a stated typical reply within two business days
- Paste the error string verbatim, including any number rendered into a placeholder
- Write from the email address on the account, since identity may need verifying
- Send feedback in Settings is a separate queue, capped at 6 submissions per minute
- Never send a password, full card details, authentication codes, or sensitive files
Frequently asked questions
What is the Whizi support email address?
[email protected]. It is the address on the support page, the address the Terms name in the Cancellation clause for anyone unsatisfied, and the address the Privacy Policy names for privacy questions, rights requests and support. There is no second address.
How long does Whizi support take to reply?
Two business days is the only turnaround published anywhere. Requests governed by the Privacy Policy, such as access, correction or deletion of personal information, carry no published timeframe at all, and Whizi may need to verify your identity before completing one.
Does Whizi have live chat or a phone number?
No. The routes published on the website are the email address, the support page at whizi.io/support, the Send feedback form in Settings, and the Report control on a conversation someone shared with you. Section 28 of the Terms adds a postal address in Kitchener, Ontario.
Should I use Send feedback or email support?
Send feedback for "this broke" and "please add this", because it attaches your browser, window size, language and selected model so the report can be reproduced without a reply. Email support for anything tied to your account, your subscription or a charge, because those need the address on the account and often need identity verification. If the feedback form fails it says so and links the support page.
Can support change the email address on my account?
Yes, and support is the only published route to it, because no setting in Whizi changes the sign-in address. The Privacy Policy frames it as a correction request, which means identity verification may be required and no turnaround is published. The full answer is on switch account email.
Can I report a shared conversation without a Whizi account?
Yes. A public share link carries a "Report this chat" control that needs no sign-in, because whoever was sent the link is the person who needs to be able to flag it. It asks for one of seven reasons, from offensive or hateful through to something else, plus an optional note of up to 2,000 characters.