Asking well

Write useful prompts for chat, tasks, and calls.

Asking overview

Asking well is how you tell Heyno what you want to know, make, or do. A prompt can be a question, an instruction, or a goal. You don’t need special commands.

A short prompt is often enough. For larger or more important tasks, include the parts that matter:

• Goal: what should Heyno do?
• Context: what information or sources will help?
• Output: what format, length, or level of detail do you need?
• Boundaries: what must stay unchanged, and what should Heyno check with you before it acts?

Use only the parts that help. You don’t need to fill in every item or follow a set format.

Describe the result you need

Start with the result, not a list of steps. Include the audience or format when those details change what Heyno should produce: “a one-page summary a client can scan,” or “a reply in my voice.”

Describe a process only when the process itself matters. Otherwise, leave Heyno room to gather context and choose an approach.

Add useful context

Share the information that could change the result. Add only the sources that matter, and say what Heyno should take from each one.

• Attach documents, spreadsheets, or PDFs when you want Heyno to summarize, compare, transform, or build a file for review.
• Add a screenshot or image when the task depends on visual context, and point out the part that matters.
• Ask Heyno to use web search when the answer depends on current information, and ask for sources when you need to check it.

Use connected sources

When Heyno has a connector, name where it should look and what it should find. You don’t need to describe every search. Availability can depend on your plan and workspace settings.

Connect your tools

Connectors link Heyno to Notion, Google Drive, email, and calendar. Type @ and the tool name to point Heyno at a specific one.

Let Heyno remember

Put preferences that should apply everywhere into Heyno’s memory: your tone, your pricing, your key people. Learn more about memory.

Set boundaries that prevent real problems

Boundaries are the few instructions Heyno needs to avoid creating extra work or taking an action you didn’t intend. Add one when changing the wrong thing would be costly:

• “Keep the approved dates and figures unchanged.”
• “Use only the sources I gave you. Flag anything missing instead of guessing.”
• “Prepare the message as a draft. Don’t send it.”

Focus on the one or two boundaries that matter most. High-stakes actions always pause for your approval.

Make the result ready to use

Tell Heyno how you plan to use the result so it picks the right length, detail, and structure.

• “Make this a one-page summary the owner can scan before the visit.”
• “Turn these notes into a follow-up email with decisions, owners, and dates.”
• “Build a table of quoted versus actual and highlight any gap over 10%.”

For important work, ask Heyno for a final check: confirming every action item has an owner, or flagging anything it couldn’t verify.

Improve the result with follow-up

Your first prompt doesn’t need to be perfect. Review the result, then ask for the specific change you want: add a source, correct the direction, ask for another option, or change the level of detail without starting over.