Building a Signal Event in Event Studio

Event Studio is a conversation. You tell Savo what you want to learn and who you want to hear from, and Savo drafts a Signal Event interview, explains the choices it made, and revises it as you push back. There is no form to fill in and no fixed sequence of steps. You are done when the event definition on the right says what you mean.

Starting

From the main navigation, open Event Studio. You will see two ways in.

• Talk it through opens a spoken conversation. Tell Savo what you want to learn and who you want to hear from, and it picks the build up from there.

• Start from scratch opens the same conversation as text. Type your answer and press Send.

Both lead to the same place. During a session you can switch between typing and speaking with the microphone button, and turn Savo's spoken replies on or off with Spoken output.

Sessions are saved as you go. To return to one, open Event Studio and choose it under Resume a session. You can also delete a session from that list; deleting cannot be undone.

The conversation

Savo opens with one question: what do you want to learn, and what will you do with what you hear? A sentence is enough. In one session, "Why do customers not adopt our AI products" was all Savo needed to draft a complete event.

Three things need settling before an event can publish: the business problem, who you want to talk with, and how long each conversation should run and how it should feel. Savo does not ask for these as a questionnaire. It drafts as soon as it has enough, then confirms what it assumed against the draft.

When the first draft is ready, Savo tells you what it decided so you can push back. Expect it to name the kind of event it chose and why, who it aimed the conversation at, how long a session runs, and the topics it covers. It then asks whether that is close or whether you want it narrowed to a particular product, segment, or angle.

Answer in plain language. "Yes" accepts the draft. "Aim it at enterprise admins, not end users" or "Add a topic about pricing" sends Savo back to revise. Every change is made through the conversation.

You can hand Savo material at any point. Use the clip to attach research, a brief, or notes, and Savo grounds the event in what you share.

The button beside the composer changes with the state of the build.

Build asks Savo to draft now with what it has, assuming sensible defaults for anything still open and telling you what it assumed.

Rebuild appears once you have said something new after a draft.

Save to Library appears when the draft is up to date and ready to save.

The Event definition panel

While you talk, the panel on the right fills in. It has two views.

Summary shows the event name, the business problem it addresses, a description of what the conversation will do, and the target length. This is the view most builds need.

Detailed spec shows the complete technical definition: the interview mode, who the event is for, the facilitation guides Savo will follow and what counts as enough on each one, the concepts it listens for, how edge cases are handled, and the research the design draws on. You do not edit this view directly. Ask in the chat to change anything you see here.

Discovery or scored

Savo decides whether your event should measure or explore, and tells you which it picked.

A construct-based event scores participants against Dimensions agreed in advance. Savo chooses this when the answer to your question is a degree of something and you can name the qualities you care about before anyone speaks. Choose it when you need scores you can compare across people or over time.

A discovery event has no Dimensions to score. It explores a set of topics openly and produces themes across conversations, for questions where naming the answers in advance would defeat the purpose. Savo will say so plainly: "I built this as a discovery event, not a scored one." If you disagree, say so and it will rebuild.

An event is one or the other. If your question needs both, Savo will propose splitting it into two events and explain why.

Saving and publishing

When you accept a draft, Savo saves it as the canonical version and validates it. If the timing does not fit (five topics in a fifteen-minute window, say), Savo widens the window itself and tells you in one line so you can undo it. Anything that would change what the event measures, Savo asks about first.

Savo may also offer a research pass before you publish. It drafts from established theory first and can then check the design against current research in your field and add citations to the event's provenance. Take it when the event will go in front of stakeholders; skip it when you want the event live now.

Publishing creates the event in your Signal Event Library, ready to select in the campaign wizard. A published event can be edited later from the Signal Event Library, field by field, in the Event Editor. Returning to the Studio session and changing a published event creates a new version, and publishing that version is a new charge.

Tips

1. Say what you will do with the answers, not only what you want to know. That is what lets Savo choose between a scored and a discovery event.

2. Push back on the first draft. Savo's opening choices are made so you have something concrete to react to.

3. Attach what you already have. A prior survey, a strategy note, or a competitor analysis changes the draft more than a longer description does.