Prompts

A prompt is a saved question. When you find a query worth keeping — “flag my at-risk accounts approaching renewal,” “build a QBR prep brief for this customer” — you save it as a prompt, and from then on anyone on your team can run it without retyping or remembering how you phrased it. The wording, the structure, and any formatting instructions travel with the prompt, so the answer comes back the same way every time.

Prompts solve a specific problem: good questions take iteration to get right, and the version that finally works tends to live in one person’s head. Saving it moves that knowledge into the workspace where the rest of the team can use it. Manage all of them under Settings → Prompts, where you can browse the built-in catalog, see what your teammates have authored, and create your own.

Running a prompt

The fastest way to run a prompt is from chat. Type / in the chat box and a menu of available prompts appears; pick one and its text drops into the input, ready to send. You can also browse the catalog under Settings → Prompts, open any prompt to read what it does, and click through to chat with it loaded.

If a prompt has variables — a specific customer or contact it needs to run against — chat asks you to fill them before it will send. A prompt that targets “this customer” can’t run until you’ve named the customer, so the send button stays disabled until every required variable has a value.

Bookmark the prompts you reach for most. They collect into your Saved Prompts section at the top of the catalog, separate from the full list, so your everyday queries stay one click away.

The built-in catalog

Every workspace ships with a catalog of prompts Sonora authored, organized into five categories:

• Customer Intelligence — health briefs, account-issue diagnosis, and sentiment-decline flags.
• Customer Lifecycle — renewal forecasting, at-risk renewal flagging, churn-save planning, onboarding status checks, and expansion-opportunity discovery.
• Meeting & Communication — QBR prep, escalation briefs, customer-meeting prep, and post-call summaries.
• Strategy & Planning — voice-of-customer reports, feature-request ranking, issue-trend analysis, success plans, and MEDDPICC scoring.
• Decks — QBR deck generation.

These cover the questions customer success and account teams ask most, and they double as worked examples of how a well-structured prompt reads. You can’t edit a built-in prompt directly, but you can duplicate any of them into a copy you own and adjust from there — a fast way to author your own without starting from a blank page.

Authoring a custom prompt

Anyone with prompt-management permission can create one. From Settings → Prompts, click Add prompt and give it a title, a category, and an optional one-line description so teammates browsing the catalog know what it’s for.

The heart of the prompt is its text — the question itself, written the way you’d type it into chat. You can also add separate instructions: longer guidance on how the answer should be structured, formatted, or scoped, sent to Sonora along with the question. Keeping the two apart lets the prompt text stay short and natural while the formatting rules ride along behind it.

Variables

A variable is a placeholder in the prompt text that gets filled in when the prompt runs. Write one with double braces — {{customer}} — and whoever runs the prompt picks the actual customer at that moment. A prompt like Build a QBR prep brief for {{customer}} is reusable across your whole book of business: the structure is fixed, the target is chosen per run.

Three variables are available, matching the entities Sonora knows about:

Variable	Fills in
{{customer}}	An account from your workspace
{{contact}}	A person at an account
{{product}}	A product or module

Insert them with the variable picker above the prompt text, or type the braces directly. Any variable in the prompt text is treated as required — chat won’t send the prompt until it’s filled — and only these three are supported. Other placeholders are rejected when you save.

Visibility and sharing

A prompt you create is shared with your whole workspace the moment you save it. There’s no separate publish step. The catalog’s filters reflect this: My Prompts shows what you authored, Organization Prompts shows what your teammates authored, and Sonora Prompts shows the built-in catalog. Search by title, description, or author to find a specific one.

This is the point of prompts. The renewal review one CSM perfected, the QBR brief format your team standardized on — they live in the workspace, not in a single person’s chat history, and everyone runs the same version.

Prompts in other Sonora surfaces

Prompts aren’t limited to the Sonora chat box. Through Sonora’s Model Context Protocol server, every prompt in your workspace — both your team’s and the built-in catalog — shows up inside MCP-compatible clients like Claude Desktop and Cursor. The prompt’s variables become arguments your client fills in, so the same saved question runs from your editor or terminal.

Built-in catalog prompts carry a system__ prefix in MCP so they don’t collide with a team prompt of the same name. See the Model Context Protocol documentation for connecting a client.