How Hebno handles a request

Every message you send is routed to one of four paths: answer, research, revise or image. You do not pick a mode. Hebno reads the request and your open work, then chooses the lightest path that produces a reliable result.

​

The four paths

Hebno also infers the kind of deliverable from your words. Ask for “a deck” and it builds PowerPoint, “a memo” produces a Word document, “a model” produces an Excel workbook. You do not need to name a format. If you ask for something outside those formats, Hebno offers the closest one. An answer can escalate. If Hebno starts answering and finds the request needs evidence from your connected systems or the web, the turn moves to a research run.

​

Go deeper

Select Go deeper under any answer to turn it into research. Hebno writes a new brief from the question and the answer so far and starts a run. If the answer was about an existing deck or document, Go deeper revises that deliverable instead. Use it when an answer is useful but you need it backed by files, records and public sources before it goes to a client.

​

Scoping questions

Before a research run starts, you may see a Before I start card. It appears only when a different choice would change the deliverable, shows never more than two questions, and each has two to four options. Some allow several picks (“choose any that apply”), and Something else lets you type your own. Select Start research to run with your choices, or Skip to let Hebno use its own judgement. The run records which you did: “You scoped this run before it started” or “Skipped, so the run used its own judgement.” Long, detailed requests skip the questions because they already include the scope.

​

Follow-ups edit in place

Once a deliverable exists, a follow-up changes it. Ask for “a tighter executive summary” or “add the pricing table” and Hebno edits the named sections of the same document, deck or workbook. Plain edits never start a research run, and they do not create a second copy. When a request could mean either, a Before I continue card shows: “Should this update file name or start new work?” Choose Update, or start a new deck, document, workbook, email or chat. The recommended option is marked Recommended. To re-check an edited deliverable against its sources, select Verify against sources. See Sources and evidence.

​

Writes and confirmation

When a request implies a change outside the chat (log time, create a task, update a deal, send an email, send an invitation, save to a folder), Hebno shows a confirmation card. Nothing is written until you confirm. Email and invitations use Send. See How Hebno works.

​

Stop and queue

Select Stop response while Hebno works. If you type while a response is streaming, the send button becomes Queue message, and queued prompts appear under Queued messages until they run. Remove one with Remove queued message. What a stopped run already did is retained, and you can ask Hebno to continue from there.

​

Tips for better routing

• Name the client, system or file when it matters: “in HubSpot”, “the SharePoint deck from March”.
• Say who the reader is and what they will do with it.
• Attach or link the material you want used. Hebno searches connected systems itself, but a named record narrows the search.
• Ask for the deliverable in one message, then refine in follow-ups.

​

Next steps