Omniscio

Report conversations — replies to your reports, inside the app

Every report sent from the app's Feedback button also opens a conversation with the support team, so support can answer inside the app and the person can write back — even without Get Help. For a report of any kind from somebody other than the operator, that conversation is the whole answer: no investigation, one acknowledgement, and a draft reply waiting for support. Covers where replies show up ("Your reports"), what the conversation carries, and how it is switched off.

On this page

What it is

When you send a bug report, a feature idea, a question or general feedback from the app's Feedback button, the app also opens a conversation about it with the support team. Someone on the support side can then answer you right inside the app, and you can answer back — you do not need to have Get Help turned on, and nothing about how your report itself is sent changes.

For any report somebody else sent — a bug report, a feature idea, a question or a feedback note, that conversation is the whole answer on the support side: a person reads it and writes back, and nothing starts a session in the background to work on it automatically. The person who sent it is told once that it arrived, and support opens the conversation onto a reply that has already been drafted for them to read, edit and send — the assistant never sends it, and never answers a report conversation at all. The operator's own reports are the exception: those keep starting their investigation, because that is how their own bugs get fixed.

The conversation belongs to you and starts with your report's own words, labelled with its kind (for example "Bug report: …"). Only people answer it: the app's AI assistant never replies to a report conversation.

The same is true whichever door the report left by. An assistant filing a report on your behalf (rather than you clicking the Feedback button) reaches the app through the same route, and that report opens its conversation too — one report, one conversation, either way.

A report filed for somebody else is answered where they can see it. When an assistant or the operator files a report naming a different person — a teammate, a customer — whose conversation it is stops being a matter of taste: the computer that carries the Help Desk opens it, under its own key, with that person as the reporter. The computer that filed it opens nothing at all, so the answer goes to the person the report was for, by email, instead of landing in the filer's own list where the person named could never read it. A report filed here for somebody else therefore does not appear under the filer's Your reports: it is not their report to answer. That hand-over waits until the report has actually reached the Help Desk by its saved copy — a report carried only by email, or still waiting to be retried, keeps the local conversation instead. When it does keep it, the row remembers whose report it really is: the local request records a filed-for flag, so such a conversation is treated as reaching nobody here — support is refused a reply on it, it is flagged in the work queue, and the autopilot writes no note to it, rather than accepting an answer the person it was filed for would never see.

Where to find it

  • Your reports — open the Feedback button; once you have sent at least one report, a Your reports row sits at the top of the form. It opens a small window listing your reports, each with where it stands: on its way, waiting on an agent, answered, or resolved.
  • A dot on the Feedback button — shown while a reply from support is unread.
  • Start a session from a report — every row in that list also carries a Start session button (the same one the Help Desk console puts on a ticket). It opens the ordinary Start-session dialog already filled in with that report, so you can ask a session "what was this about, and is it fixed?" instead of copying the report into a new chat by hand.
  • The reply notification — "An agent replied to your report". Clicking it opens Your reports on that conversation. Phones paired with the app get the same notice.
  • From Help Desk itself — the Help Desk screen carries a Your reports door, in the widget header on a desktop and in the phone's own strip on a phone, plus a Your reports button under the example prompts on the blank "Ask anything" screen. That is the way back when the reply notice has already left your Inbox: before it existed, a report whose notice was gone could not be reopened from anywhere the person would think to look.
  • One Inbox row per conversation — a reply also lands in your Inbox as one row for that conversation, however many replies it has; it shows the newest reply and opens the conversation. Dismissing it stays quiet only until the next reply arrives.

On the desktop Your reports is a compact popover in the corner of the window (the same corner and size as the Get Help widget), so the rest of the app stays usable behind it and Esc closes it. On a phone it is a screen inside the normal layout, like every other hub: the app's tab bar and breadcrumb stay on screen, the breadcrumb names the screen, and Back steps out of it — first from an open conversation back to the list, then out of the screen. Either way it opens through the one door openYourReports; the phone screen carries no close button, because the breadcrumb already carries Back. Every door reaches that one opener, including the Inbox row for a support reply on a report conversation, so a phone tap on that row lands on this screen with the app's own navigation still on screen.

How it behaves

  • It opens on the newest message. Opening a conversation puts the TOP of its newest message at the top of the window, so a long reply from support reads from its first line instead of starting in the middle — the same way a session transcript lands on its latest reply (the Get Help chat works the same way). A newer message that arrives while you have not scrolled, or while you are reading at the bottom, is shown from its top too; scroll up to read older messages and nothing moves you.
  • Replying. While a report is open with the support team, a reply box sits at the bottom of it. Your reply goes back into the support queue. Once support resolves it, it becomes read-only and says so — send a new report if you need more help. A report that has not reached support yet is read-only too, until it arrives.
  • Starting a session from a report. Each row in Your reports carries a Start session button beside it. It reads that report's own conversation and opens the standard Start-session dialog with the report already written into the prompt — the report's title, who sent it, its current state ("Resolved", "Waiting on an agent"…), and the conversation as it stands — so you review and edit it before anything runs. Nothing starts until you press Start session in that dialog, and it works on a report in any state, a closed one included. The prompt carries ONLY what you can already see in that conversation: an internal support note, a thread tag or anything else support keeps to themselves never rides along, and the session is not told it is the ticket's fixer, so starting one never records itself on the report. If the report cannot be read you get a plain message instead of a button that does nothing.
  • An agent's report is answerable from the command line too. An agent that files a report through POST /feedback gets the report's correlationId back with a followUp block naming the road: POST /helpdesk/requests/:id/reply and { text }. That adds the message to the SAME conversation — one ticket, one thread, no second investigation — and it works after support has answered, which is exactly when an agent usually has more to say. The ticket can be addressed by any handle you actually hold: its full local request id, the report's correlationId, or a unique prefix of either of at least eight characters — the short id a card or a log line shows. Both follow-up roads (…/:id/reply and POST /helpdesk/ask-followup) and the read road (GET /helpdesk/requests/:id) take the same handles, so a follow-up, and the read that follows it, always name the same ticket. The session that filed the report may always use them; any other session on the same signed-in account may use them too, which is how the person's own assistant answers on the person's own ticket, including one they filed from the app. Another account's ticket is refused, and a short handle that matches two tickets is refused rather than guessed. A refusal is one message naming the handles a caller can pass, so a wrong handle reads as a wrong handle instead of "the conversation is gone" — which is what used to happen to a live ticket, and why a reporter once filed three new tickets instead of replying.
    • A short handle that matches two of YOUR tickets says so. A prefix is only ever matched against conversations you could already reply to, so somebody else's ticket can neither match nor make your own ticket read as ambiguous. Two or more of your own tickets sharing the prefix answer 409 asking for more characters; everything else that misses — an unknown handle, a deleted conversation, another account's ticket — keeps the ordinary 404 and the same message.
    • GET /helpdesk/requests/mine lists the tickets a caller may reply to, as { tickets: [{ id, subject }] } — the id to paste into the reply route and the ticket's own subject line, nothing else. It uses exactly the reply route's scope: the account's tickets plus the ones the calling session itself filed, so an agent can find its own ticket's full id even when the desktop is signed out or signed into another account.
  • You are told once, then a person answers. Send a bug report, a feature idea, a question or a feedback note and you get a single "we've got your report and someone is already looking into it" email — never a second one, however many times the report is delivered.
  • It carries your report's own files. Your screenshots, anything else you attached, and the logs the app collected with the report ride the conversation as real attachments, so support opens them on the ticket instead of hunting through the report's email. They sit on the conversation's opening message — the report's own words — so nothing is shown twice. Nothing else rides along (no device details), and replies in the conversation are text only.
  • Offline is fine. A report saved to send later still gets its conversation; if the conversation could not open, the app keeps retrying for about a day and never opens a second one.
  • A report you kept on your computer opens nothing. With sending turned off, or a report that was lost, no conversation is opened.
  • A reply that would reach nobody is refused, not silently sent — when the conversation NAMES somebody this computer is not signed in as. A report can be filed here FOR another person, and then that person's own app is not the one holding the conversation and nothing on this computer delivers it to them. On a conversation like that, support's hand reply is REFUSED with a plain warning instead of being written into a thread the reporter never sees, and the ticket is left exactly as it was: still owing an answer, nothing appended, no "answered" stamp. The automatic fix notes stand down on it for the same reason, so a customer is never told a fix they cannot read. A conversation this computer owns, and one received from another install with an address support mails to, are unaffected. THE KNOWN GAP: a report filed here for somebody else under THIS computer's own account carries our name on its thread, so the refusal cannot recognise it and it is not caught yet — that is a filed ticket, not a silent assumption.
  • Nothing else of Get Help comes with it. With Get Help off, Your reports shows only your report conversations — no question box, no assistant, no Help Center.
  • Switching it off. Turn off Report conversations in Settings → Lab: new reports stop opening a conversation and Your reports is hidden. It is on by default.
  • bug-report-intake.md — how the Feedback form's report is received, and what happens to it after it leaves the app.
  • helpdesk.md — the in-app help assistant and the support console where the team answers report conversations alongside ordinary escalated questions.

Last verified 2026-10-23