Email jared@answer.cloud for Answer Cloud support. Include the intended site and the result you expected so the team can investigate the correct workspace and publishing path. Privacy requests can be sent to privacy@answer.cloud.
Include a useful issue report#
A concise report should contain:
- The affected public URL and site slug.
- The organization/workspace name and ID, if available.
- Whether the issue affects staging, production, or both.
- The date and approximate time, including timezone.
- What you did, what you expected, and what happened.
- Exact non-sensitive error codes and status values.
- Recent relevant changes and whether the problem is repeatable.
For a deployment, add its numeric deploy ID and sequence, final status, and warnings. For CMS content, add the collection key and entry ID, whether changes are drafted or published, and the affected URL. For a report question, include its report ID, domain, run date, and the finding you want reviewed.
For an agent connection issue, identify the client and whether browser sign-in completed. Describe the organization inventory result without copying tokens. For missing analytics, include the site and reporting date range, collection method, and a representative event/request time.
Keep diagnostics safe#
Remove credentials, signed upload URLs, account claim links, verification codes, and unrelated customer data from screenshots and logs. A response can contain private conversation text even when it excludes dedicated contact fields. Send the minimum evidence needed to reproduce the issue.
Use a short non-sensitive chat question when demonstrating answer quality. Record the expected factual answer and cited URL. A screenshot of an empty launcher does not demonstrate a generation failure; identify whether the launcher, retrieval request, or answer request failed.
Preserve the work while waiting#
Keep the editable Astro source, site identity, and current deployment details. If the first-launch credential expires or account setup is incomplete, preserve the existing reservation and follow launch recovery. Avoid creating replacement accounts, sites, or keys to work around quotas or uncertainty.
For an unknown form outcome, check the site's inbox before resubmitting; a network error can occur after the submission was saved. A successful capture queues notification delivery, so report inbox capture and email delivery separately.
Choose the relevant guide#
Start with deployment failures, content rendering, chat/forms/search, or DNS and certificates when they match the issue. Include the checks already completed in your report.
Response times depend on your support arrangement. This contact page does not create an emergency channel or a guaranteed response deadline; confirm any agreed Enterprise support terms with the team.