Ask Ella to submit a form
Describe what happened in a sentence and Ella fills in the record and submits it — no tapping through fields.
Describe it like you would to a colleague
The tour opens with a plain description typed into Ella's chat — what happened, where, and anything already known about it. No template to find first and no field order to follow: you report it the way you would say it out loud.
She fills in what she can, and asks for the rest
Ella matches the description to the right template and populates every field she can work out from what you said. Where a required answer is genuinely missing, she asks for it directly, one short question at a time, instead of guessing or leaving it blank.
- Matches the template — Works out which form the report actually belongs to.
- Fills what's clear — Populates every field the description already answers.
- Asks for what's missing — Requests only the required answers she genuinely can't infer.
Review before it submits
Nothing lands in Submissions unseen. The completed draft is shown back to you first — edit a field, correct a detail, add something you forgot — and only your confirmation sends it in, exactly as if you had filled in the form yourself.
Why it matters
Reporting drop-off usually happens because the form feels like a chore in the middle of real work. Letting people report in their own words, while the record still lands in the same structured fields everyone else's does, keeps the data clean without adding friction — and the review step means nothing gets logged without a person confirming it is accurate.
Ready to build your own?
Start free and ship your first app in minutes — or have us set it up with you.
More resources