Ten quick reference guides
Short, task-level procedures for the jobs you do most, each one a numbered walkthrough with a screenshot of the screen it describes.
Open the guidesReport a bug, ask for a feature, or reach a human when you cannot get into your workspace at all.
Two routes, and which one you want depends on whether you can reach your workspace. If you can, use the Report button in the top-right toolbar: it is on every screen, it records which screen you were on, and your report gets a ticket number your administrator can work through. If you cannot sign in at all, use the email form further down this page and we will reply to you directly.
Dave has a reporting form built in, so raising something does not mean leaving the product and writing an email from memory.
The Report button sits in the top-right toolbar on every screen in Dave. Opening it captures the screen you were on and hands the form your context, so you can start with what went wrong rather than with where you were.
Two types: Issue or Bug, and Feature Request. Five criticality levels: Trivial, Low, Medium, High and Critical, set by the person who actually hit the problem.
Every report is numbered as it arrives, counting up within your own workspace, so you and your administrator are always talking about the same ticket.
The dialog opens from any screen and records which screen you were on. Only the prompt changes between reporting a fault and asking for something.
Reports land in your own workspace. An administrator opens Admin, then Settings, then User Reports, which sits between the Audit Log and Feature Flags, and works the queue from there.
A report moves through four statuses: Open, then Accepted, then Done, then Closed.
An administrator can filter the queue by status and by type, sort it by any column, and search the summary text.
The queue exports to CSV, and rows are edited inline rather than through a separate form.
Tell us what you were trying to do and what you saw, and we will reply to the address you give us.
If you can reach Dave, use the Report button inside the product instead. It records the screen, the URL path, your viewport, your browser and the timestamp for you, and your report gets a ticket number your administrator can track. This form carries none of that, so it is the slower route for anything that is not an access problem.
Or write to support@hellodave.ai directly.
Short, task-level procedures for the jobs you do most, each one a numbered walkthrough with a screenshot of the screen it describes.
Open the guidesThe five-step lifecycle, from configuring your agents to monitoring a run and reporting on it.
Read How It WorksEverything HelloDave.ai publishes, gathered in one place, plus the discussion boards when they open.
Visit community.hellodave.aiDave carries an in-product help centre covering each area of the product, from the workflow editor, tasks and instances to security, audit logs, and team and billing, plus release notes for every version.
Use the Report button for anything you can reach: it captures the screen, the URL path, your viewport, your browser and the timestamp, and gives the report a ticket number. Email support@hellodave.ai only when you cannot get into your workspace to press it, because that is the one case the in-product route cannot cover.
Your workspace administrator. Reports appear under Admin, then Settings, then User Reports, which sits between the Audit Log and Feature Flags, where they can be filtered by status and type, sorted by column, searched by summary text, edited inline and exported to CSV.
Each report carries a ticket number of its own, counting up within your workspace, and an administrator records an outcome against it: Implemented, Fixed, No Issue Found, Duplicate, Deferred, Won’t Fix, or Cannot Reproduce.
Use contact@hellodave.ai for anything commercial: plans, trials, rollouts and compliance questions. Use support@hellodave.ai, or the form on this page, once you are using Dave and cannot get to the product itself.