Compose — a chat, not a form.

Ask for a post the way you'd ask a colleague who already knows your business. Your brand, your voice and your language come along automatically — and a thread belongs to one brand, permanently.

4 min read Compose Updated Jul 2026

Compose is where you write. You ask for a post the way you'd ask a colleague who already knows your business — “write a LinkedIn post about the boiler service offer, but less salesy” — and it comes back in your brand's voice. It is a conversation, not a form with twelve fields.

Why a chat and not a form

A form makes you decide everything up front: platform, tone, length, angle, call to action. You almost never know all of that before you see a first draft. A chat lets you start vague and get specific.

So Compose keeps the thread. You send a request, read what comes back, and reply with what's wrong with it — “shorter”, “drop the emoji”, “lead with the price”. Every message in a thread is a fresh generation, and every one carries your brand with it.

What gets attached to your request automatically, without you asking:

  • Your brand — name, website, industry, what you're about, and your palette and fonts
  • Your trained voice — the fingerprint we built from your writing samples, plus your banned and preferred words
  • Your content language — set per brand, so the output arrives in the language you sell in

That's the whole point of the product being a chat: you supply the idea, we supply everything we already know about you.

The three panes

1

The sidebar — history and presets

Two tabs. History lists your threads for the brand you're on, newest first, with pinned ones held at the top. Presets is the prompt library — ours, yours, and anything a teammate has shared. There's a search box above both, and a pinned-only filter on History. The whole sidebar collapses with the panel button in the header if you want the width back.

2

The thread

Your messages on the right, ScoutRival's on the left. Under every reply there's a row of actions: Copy, Save (keeps it as a draft), Rewrite (re-runs it through your brand voice), and Make graphic (turns the post into an image prompt).

3

The composer

The card at the bottom. The text box, and a rail of chips below it: the brand chip, the paperclip for attachments, the Text / Image toggle, and — in image mode — the aspect-ratio picker. Save prompt stores whatever you've typed as a reusable preset.

One brand per thread — a hard lock

A conversation belongs to exactly one brand, permanently. This isn't a soft preference we nudge you about; the server rejects a message whose brand doesn't match the thread it's being added to.

// SWITCHING BRAND STARTS A NEW THREAD

Change the brand on the composer's brand chip while a thread has messages in it and you'll get a confirmation dialog. Confirming switches your active brand everywhere in ScoutRival and drops you into a fresh, empty thread. Your old conversation isn't deleted — it's still there, under its own brand. You just can't continue it as a different brand.

The same lock explains the sidebar: you only ever see threads for the brand you're currently on. If a conversation seems to have vanished, check the brand chip first. It's almost always that.

Text mode and image mode

The toggle in the composer decides what you get back.

Sending, and the keyboard shortcut

  • Cmd+Enter (Mac) or Ctrl+Enter (Windows) sends. A plain Enter gives you a new line — you're writing a brief, not a chat message, and briefs have paragraphs.
  • The Send button does the same thing. It reads “Generate” in image mode.
  • You can't send while a reply is in flight. The button locks until it lands.
  • Failed generations don't cost you anything, and your prompt is put straight back in the box so you can edit and retry.

Where to go next

Still stuck?
Contact support

Related

Compose
Writing a post
Compose
Image mode