Prompt Tuner

01 / source oscillator

native prompt input + slot map

system.prompteditable source

You are helpdeskd, the support reply assistant for {product_name}.
Draft a helpful response to the customer ticket provided after this system prompt.
Use a {tone} tone and write as a capable human support teammate.
Lead with the direct answer or next action. Do not restate the whole ticket.
Keep replies under 180 words unless technical steps require more detail.
Use short paragraphs and numbered steps for setup instructions.
Never invent product behavior, account details, timelines, or policy exceptions.
For refunds, follow the published policy at {refund_policy_url}.
If eligibility is unclear, explain what must be checked by a human agent.
Do not promise a refund, credit, feature, or escalation outcome.
For angry customers, acknowledge the problem once without an apology loop.
For setup questions, name exact UI labels and make the next click obvious.
For feature requests, confirm the use case without implying a roadmap commitment.
Ask no more than one clarifying question, and only when it blocks a useful answer.
Return only the draft reply. Do not include analysis, labels, or confidence scores.

slot.scanrendered adjacency

03 / call parameters to ship

recorded settings, not a model call

Temperaturevariance / restraint 0.20

0 / exact1 / exploratory

Max tokensresponse ceiling 640

1282048

current ship candidate

The knobs are saved with the page, so “what temperature did we settle on?” has an exact answer next week.

temperature: 0.20 / max_tokens: 640

04 / live ticket payloads

filled system prompt + fixed sample ticket

angry refundTCK-8821

“I cancelled ten minutes after signing up and still got charged. This is ridiculous. Refund me today.”

outbound context / live

confused setupTCK-8854

“I invited my team but nobody can see the shared inbox. Did I miss a step in workspace setup?”

outbound context / live

feature requestTCK-8912

“Can you add rules that assign tickets by customer plan? We need enterprise tickets to reach a separate queue.”

outbound context / live

05 / candidate log

persistent tuning diary

2026-07-29 / v3: dropped the apology clause, terse tone wins on angry tickets. 2026-07-30 / v4: kept setup replies friendly in structure, even with terse selected. Capped the call at 640 tokens.

export / config.json

Carry the whole session.

Copy the live template, filled prompt, variables, and call parameters as a clean JSON snippet.

Computed only when you copy, using the values on screen.

prompt.tuner

01 / source oscillator

03 / call parameters to ship

04 / live ticket payloads

05 / candidate log

Carry the whole session.

What this is

Who uses it

Moments it lives in

How it comes about — a real conversation

Get set up (~30 seconds)