Prompt Studio lets you create one-click prompts that help you and your team get consistent, high-quality answers from Databook. You choose whether each prompt is just for you or for everyone in your organization.
Who can create prompts
Builders, Strategists and Organization Admins can create prompts in Prompt Studio.
Role | Can make a prompt visible to |
User | No access to Prompt Studio |
Builder | Only me |
Strategist | Only me, or Everyone in my organization |
Organization Admin | Only me, or Everyone in my organization |
For more on roles, see User roles in Databook.
How to create or edit a prompt
Go to Studio > Prompts in the left-hand navigation.
Select New Prompt to create one from scratch, or choose an existing prompt to edit.
Fill out the fields:
Display name (optional): a short label, up to 120 characters, that helps people identify the prompt in the Prompt Library. If you leave it blank, the Prompt Library shows the start of the prompt text instead.
Prompt: the instruction Databook will receive. Prompts must contain at least one variable and be less than 10,000 characters. Variables let each person personalize the prompt before running it, for example by choosing which account or industry to research.
Category (optional): group related prompts together, or create a new category using Manage categories.
Visibility: choose who the prompt appears for in the Prompt Library, Only me or Everyone in my organization.
Select Save. A new prompt stays inactive until it's been saved.
Test the prompt by selecting a value for each variable it contains.
Use the toggle in the top right of the screen to activate or deactivate the prompt.
Choosing who sees a prompt
Visibility | Who sees the prompt in the Prompt Library | Available to |
Only me | Only you. Your colleagues don't see anything new. | Builders, Strategists, Organization Admins |
Everyone in my organization | Everyone in your organization | Strategists, Organization Admins |
For example, you might write a prompt tuned to how you run discovery calls and keep it for yourself. When a prompt proves useful for the wider team, a Strategist or Organization Admin can make one available to everyone.
Available variables
Add a variable using the Insert menu below the prompt text box.
Variable | What people select when they run the prompt |
Account | A company from your list of accounts |
Industry | An industry |
Sub-industry | A sub-industry |
Professional | A contact |
Use case | A use case from your organization's list |
Solution | A solution from your organization's list |
A prompt can include more than one variable. If it does, people see a separate field for each one and need to make a selection for all of them before they can run the prompt.
Example: an industry insights prompt
Using the sub-industry and use case variables together, you could build a prompt like:
Research industry priorities and trends in the [sub-industry] and help me position [use case] for companies in this industry.
This lets you research any sub-industry and get positioning help in a single step, without needing to pick a specific company first.
How a prompt is used
Once a prompt is active, it appears in the Prompt Library for the people set under Visibility. To use it:
Select the prompt. It's shown by its display name if one is set, or by the start of the prompt text otherwise.
Fill in a value for each variable the prompt contains.
Select Submit.
Receive a tailored response from Databook right away.
Good to know
A prompt's Visibility decides who can see and use it once it's active. Only Strategists and Organization Admins can make a prompt visible to everyone in the organization.
A prompt can currently only be edited by the person who created it. If a Builder's prompt should be available to everyone, your Organization Admin can give them the Strategist role so they can change its visibility. The prompt stays available to everyone even if their role is changed back afterwards.
You can edit a prompt at any time to refine its wording, update its display name, or add variables.
Prompts are meant to guide your team, not restrict them. Aim for clarity rather than complex setups.


