A little context helps
Make your message easier to understand.
You do not need technical language to ask for support. Explain your goal, describe what you tried and tell us what appeared on the screen. The guidance below helps you include useful details while keeping private information out of your message.
Choose the right reason
Select the contact option that best matches your request, then begin with a short sentence explaining what you need. General questions, account problems, project inquiries and feedback benefit from different background details.
If several issues are unrelated, describe them separately. For a project inquiry, explain the objective, intended audience and expected deliverable. Mention any important budget or timeline constraints as requirements to discuss, rather than assuming they have already been accepted. Sending an inquiry does not confirm a quotation, delivery date or project agreement.
Getting help with an AI tool
Identify whether you used AI Web Builder, AI Consultant or Business Planner. Include the page address and explain what you wanted the tool to do. Mention whether the problem occurs with every request or only a particular input.
Copy the visible error message and include a task or project reference if one is available. A short example can be useful, but remove confidential information. Distinguish a connection problem from an inaccurate response or an unfinished result. These symptoms can have different causes, so the exact behaviour matters.
Account access and verification
Check that you are signing in with the email address associated with your account. If you cannot remember the password, use the available password reset option. Check your inbox and spam folder for verification or reset messages before requesting another email.
If the problem continues, explain which step fails: submitting your email, receiving the message, opening a link or setting a new password. Never send your password, reset link, session cookies or authentication secrets. Account access questions may require verification before any account changes can be considered.
Profile and email changes
Your account settings provide the profile and security controls supported by the application. When changing an email address, follow any verification instructions displayed. Note which field you tried to update and the exact validation message if the change fails.
You may identify the affected account by email, but avoid adding unrelated identity documents or personal records. A support message alone does not authorize an account transfer or disclosure of another user’s information. Describe the requested correction clearly and provide only the information needed to investigate it.
Writing a useful bug report
Separate what you expected from what actually happened. For example, explain that you clicked a PDF export button and received an empty file. List the steps needed to reproduce the issue and mention approximately when it occurred.
Include your browser name and device type. For layout problems, mention screen orientation, browser zoom and which control becomes difficult to use. This form accepts written descriptions; do not paste large encoded files, executable content or private request headers. If support requests a screenshot through an appropriate channel, remove sensitive information before sharing it.
Saved projects and downloads
Tell us whether the issue concerns a saved business plan, an AI conversation, generated website code or a downloaded resource. Check that you are using the account that created the work, then look in the relevant project or conversation history.
For a missing download, check your browser’s download list and the device folder used for saving files. Include the project name and creation date when known. A visible preview is not the same as a completed export. Keep independent copies of important files rather than assuming a temporary download link will remain available indefinitely.
AI credits and interrupted tasks
AI Web Builder, AI Consultant and Business Planner use the shared daily website credit allowance. Check the balance and reset information displayed in your account. Provider limits and website credits are separate, so an available balance does not guarantee immediate provider capacity.
If a task pauses or fails, include its status and reference in your message. Explain whether a credit was deducted, restored or appears incorrect. Avoid repeatedly submitting the same request while investigating an existing task. Support can review the recorded activity, but completion times and uninterrupted service are not guaranteed.
Resources, payments and access
For questions about source code, themes or a paid resource, include the listing name and explain the stage where the problem occurred. It matters whether the issue happened before payment, during the checkout workflow or when accessing a download.
Provide a relevant order or transaction reference when available. Do not send full card numbers, banking passwords, one-time codes or unredacted financial records. Purchase and access questions may require review of the existing transaction information. A contact submission does not guarantee a particular refund decision, replacement or response time.
Privacy and account deletion
Start an account deletion request through the supported dashboard controls. Requests can be approved sooner by an administrator or processed automatically after seven days through the scheduled deletion workflow. Automatic processing depends on the relevant backend services running successfully.
Contact support if the displayed status remains unresolved. Include the request date and account email, without repeating sensitive information. Backups, provider copies and minimum transaction or security records can have different cleanup requirements. Read the Privacy Policy for the stated handling of account data and deletion.
Feedback and accessibility
Suggestions are most useful when they describe a real task. Explain what you want to achieve, which step causes difficulty and how the existing options fall short. Report confusing labels, unreadable text, keyboard navigation issues or controls that do not fit your screen.
You can also flag inaccurate public content. Include the page address, relevant passage and a supporting reference where available. Specific examples make feedback easier to assess. Submitting a suggestion does not mean that a feature has been accepted or will be released on a particular date.
Before you send
A clear message is a useful starting point.
Check that your email address is correct and your message includes a clear question or desired outcome. If you have already contacted support about the same issue, mention the earlier submission and add the new information instead of repeatedly sending the same details.
After submitting, look for the confirmation displayed by the form. If validation fails, correct the highlighted fields. A successful submission confirms that the form accepted your message; it does not confirm that the issue is resolved. Our practical guides may help you continue with other tasks while your request is reviewed.