Personality & tone
Personality is not cosmetic.
It is where you define:
- the voice
- the level of directness
- the allowed posture
- the boundaries of the line
For Chatline, personality is operator work, not decoration.
What system instructions are for
Section titled “What system instructions are for”System instructions tell the line:
- who it represents
- what its role is
- how it should answer
- what it should not do
- what should be routed to a human
The best instructions read like a clean operator brief.
A strong baseline structure
Section titled “A strong baseline structure”Write instructions that cover five things:
- identity
- scope
- tone
- refusals
- handoff behavior
Example:
You are the direct line for Northstar Studio.
Your role is to explain the line, answer first questions from the approved source material, and route serious inbound with context.
Be calm, direct, and specific. Do not invent facts, prices, dates, or approvals. If a request needs a human decision, say so clearly and collect the context for follow-up.What tone should do
Section titled “What tone should do”Tone should make the line feel coherent with the represented surface.
It should not make the line sound theatrical or vague.
Useful tone words:
- calm
- direct
- polished
- warm
- clear
- restrained
Less useful tone words:
- magical
- edgy
- viral
- clever
Those usually produce style drift, not better judgment.
What boundaries should do
Section titled “What boundaries should do”A good line does not just “sound right”. It knows where to stop.
Good boundary examples:
- do not promise approvals
- do not invent availability
- do not answer outside the published scope
- do not pretend to be a human manager or agent
- when uncertain, state the limit clearly and route forward
The public docs support configured setup and operator-defined boundaries. They do not establish perfect enforcement, so write the instructions as safeguards, not as mythology.
How to write for public figures and teams
Section titled “How to write for public figures and teams”If the line represents a public-facing person or project, write for:
- reputational clarity
- controlled scope
- clean routing
That usually means:
- shorter sentences
- fewer jokes
- no improvised promises
- visible respect for human approval where needed
A practical testing routine
Section titled “A practical testing routine”Before publishing, test:
- obvious questions
- edge questions
- off-scope questions
- pushy questions
- questions that should be handed to a human
You are checking whether the line stays coherent, not whether it sounds impressive.