What you will learn This is a chapter for doing, not reading. Follow the three below exactly.
Entering a workspace drops you into a chat box. Type this:
Now a request that needs a tool.
HyperTeamsCalculate how many days are left in this quarter as of today.Or, if a web tool is enabled:
Look for the tool call shown above the answer.
That is the answer's basis from the threads chapter. It is the point of difference from a consumer AI service.
If you see no tool, no tools are enabled yet. Covered in turning tools on and off.
Pick whichever is closest to your situation.
The last line matters. Because filling in a blank is the natural continuation, you have to block it explicitly.
Keep talking.
| Complaint | Say this |
|---|---|
| Too long | "Cut it in half" |
| Wrong format | "Make it a table" |
| Doesn't fit us | "We're (situation), so that won't work. Again" |
| No basis given | "Give me the source for each item" |
You have the basics. The next step is reducing repetition.
If you keep making the same kind of request, rather than rewriting the instruction every time, turn it into an agent.
Threads live inside the workspace, so teammates can see them.
The principles from things to watch out for matter more in a team environment.
1. Why should you check that tool calls are displayed?
Because it shows the answer's basis. Knowing which tool a value came from makes verification possible, and when something is wrong you can see which step was wrong.
2. Why add "do not guess" when asking for a table?
Because filling in a blank is the natural continuation, so it invents something. You have to block it explicitly.
3. What if you keep making the same kind of request?
That is a signal to build an agent. Put the instruction inside it and you stop rewriting it every time.
Now for agents → What agents are
Hello. I'm a (write your role here, e.g. marketing manager).Tell me 5 things I could do in this workspace.Find how the phrase "AI Transformation" is being used recentlyand summarise in 3 lines. Include sources.┌─ Tool call ──────────┐│ web_search("...") ││ → result │└──────────────────────┘Turn the meeting notes below into a table.Columns: Topic / Decision / Owner / Deadline.Do not guess at anything not present in the source.(paste the notes)Draft an email for the situation below, in five sentences or fewer.To: (e.g. a supplier contact)Situation: (e.g. I sent a quote last week and haven't had a reply)Research (topic).- Always attach a source (URL and date checked)- Leave anything unconfirmable as "unconfirmed"□ do not put customer personal data in conversations□ do not put passwords or API keys in□ split workspaces for sensitive subjects