Help · Guides · OperatorChat

OperatorChat — design a chat persona that actually sounds like you.

App: /apps/operatorchat/ Cost: 3 credits per persona Time: 7 min · ships .md persona export

Most chatbots fail on tone. They're either too corporate (kills warmth) or too friendly (kills authority). OperatorChat ships a complete persona pack — system prompt + voice notes + 5 sample exchanges — so you can drop it into any chat platform and it sounds intentional from message one.

1

Open OperatorChat

Go to /apps/operatorchat/. Sign in at /portal/ if needed.

3 credits per persona. Plus's 75/month = 25 personas. For most brands you'll design 1–2 personas total (one customer-facing, maybe one internal) so this is a low-volume, high-stakes tool.

2

Brief the persona: brand + role + scope

The form takes:

Tip — write the "never says" list. The cheapest way to make a chat persona feel intentional is to name what it WON'T say. "Never says 'absolutely,' 'I'd love to help,' or 'just to clarify'" instantly removes 80% of generic-chatbot energy.
3

Read the system prompt + voice notes block

You get back:

The system prompt is structured: role definition → tone rules → "never says" list → scope boundaries → escalation triggers → format constraints.

4

Inspect the 5 sample exchanges

OperatorChat doesn't just give you the prompt — it shows you 5 example user-message-and-persona-reply pairs covering different conversation types:

Read all 5 before deploying. If any reply feels off, refine your brief and regenerate. Cheaper to iterate on the persona than to ship a bad one and lose customer trust.

5

Push the prompt further in PromptGen (optional)

If your chat platform has constraints (token limits, output-format requirements, function-calling), hit the Refine in PromptGen button. It pre-loads the persona system prompt + lets you add platform-specific tuning.

OperatorChat vs PromptGenWhen to use which
OperatorChatDesigning the persona itself — tone, scope, behavior. Optimized for ongoing conversations.
PromptGenOne-shot tasks, transforms, classifiers. Optimized for "input → output" not "back-and-forth."
6

Export and deploy

Hit Export as Markdown for the full persona pack as one .md file. Drop it into:

When OperatorChat is the wrong tool

What's next? Most brands deploy one persona to production and iterate it weekly for 2–3 weeks based on real conversation logs. Save your initial .md export, then save each iteration as operatorchat-v2.md, v3.md — so you can A/B versions and trace why responses changed. After ~30 days of real chat data, the persona is calibrated and you can leave it.