Set hub and screen context
Tell ShowPilot what each hub is for and what each screen shows, so the tours it writes and presents land the right point for the right buyer.
Your company context tells ShowPilot what's true everywhere. Hub context tells it what one set of tours is for: who's watching, what should happen next, and what must never come up. Screen context keeps the agent accurate about the one screen a buyer is looking at.
This article covers the hub Context tab and correcting what ShowPilot knows about a screen.
Where do hub and screen context fit?
Each tour reads every level, from your workspace down to the screen in view.
| Level | Where | What goes there |
|---|---|---|
| Workspace | Settings → Context | Your product, how you sell, your voice, your tour audiences. See Describe your company. |
| Hub | A hub's Context tab | What this hub's captures show, who it's for, what it should achieve, what it must never say. |
| Screen | Edit context on a screen | What's on that one screen. |
You're in the right place when the tour copy is right for your company but wrong for this buyer, or the agent says something about a screen that isn't there.
How do you set context for a hub?
Open the hub's Context tab
Open a hub from Tours → Hubs and select its Context tab. Changes save as you type.
Check what ShowPilot drafted
When a hub has no context yet, ShowPilot reads its captures and drafts the Knows group for you: what the captures show, and Proof worth landing, the claims the tours should back up on screen. The group says how many captures the draft came from.
Correct anything that's wrong. Your edits always win, and Re-draft runs the draft again. ShowPilot only fills a field that's empty, so a re-draft never overwrites your text.
Say who it's for
In the For group, select the tour audiences in play for this hub, or leave them all off to allow every audience. Edit the audiences opens Settings → Context.
If the hub is for one company, describe it in The account: who they are, what they said on the call, what they need to see. ShowPilot never drafts this field.
Set the aim
In Aims, write the outcome the hub is after and the ask, such as getting a technical evaluator confident enough to book a security review. Write it as a goal. The agent decides how to reach it.
Set the boundaries
In Never, list anything the agent must never surface, claim or discuss, such as roadmap dates, or pricing that should go to your team. This outranks everything else the agent knows.
What does each hub group do?
| Group | What goes there | What it changes |
|---|---|---|
| Knows | What the hub's captures show, and Proof worth landing | What the tours explain. Proof is only claimed where a screen shows it. |
| For | Which tour audiences are in play, and The account | Who the copy is written for. The account notes steer the agent but never appear to viewers. |
| Aims | The outcome and the ask | The agent's goal when it presents the hub's tours. |
| Never | Topics and claims that are off limits | Hard boundaries for tour writing and for the agent, in text and voice. |
How do you see everything a hub's tours read?
The panel on the right of the Context tab, What the agent already knows, shows each level with the values you've saved:
| Row | What it shows |
|---|---|
| Workspace | Your company context from Settings → Context. |
| Audiences | The tour audiences selected in For. |
| This hub | What you've set on this tab. |
| The tours' arcs | Each tour in the hub and how many story beats it has. |
| The screens | How many of the hub's captures the agent can see. |
| The craft skill | Whether your workspace uses the shipped tour-writing skill or its own edited version. |
Use it to avoid repeating a fact that's already set at another level.
How do you tell the agent what's on a screen?
ShowPilot describes each screen when you capture it, using your Product context for vocabulary. The tour writer reads that description, and so does the agent while the screen is on view, so correct it when it's wrong. The same description serves every tour built from that screen.
Open a screen with Edit context, from a tour's storyboard in the builder or from a hub's Captures tab. Change Name, What's on this screen or App state, or select Autofill with AI to draft them again. See Organize your captures.
Test it
Your hub context is working when:
- You reload the hub's Context tab and the This hub row in What the agent already knows shows your Aims and Never.
- You open a tour in the hub, select Script, open Audiences and select Rewrite ✦.
- The new copy is written for the audience you picked and stays clear of everything in Never.
Troubleshooting
| Issue | What to check |
|---|---|
| The Knows group is empty | ShowPilot drafts it only for a hub with no context. Select Re-draft, or type it yourself. |
| The draft misses some screens | The draft reads screens that have a description. The screens row shows how many the agent can see; the rest are described as they finish processing. |
| The agent mentions something it shouldn't | Add it to Never. It outranks everything else the agent knows. |
| The agent is wrong about one screen | Open that screen with Edit context and correct What's on this screen. |
| Tour copy didn't change after you edited the hub | Tours keep their copy until rewritten. Select Rewrite ✦ in the builder. |
Frequently asked questions
Will viewers see my account notes?
No. The account notes steer the agent but never appear to viewers.
What if ShowPilot's hub draft is wrong?
Edit it. Your edits always win, and Re-draft runs the draft again for any field you've left empty.
How do I stop the agent from mentioning something?
Add it to the hub's Never group. It outranks everything else the agent knows.
Do I need to write the agent's lines for the hub?
No. Aims is a goal. The agent chooses its own words to reach it.