How Sift speaks

Voice is rules, not a mood: a principle you can write a button from, not an adjective. This is the rulebook every Sift string comes from, whether a person writes it or Claude does. The principles set the register, the dictionary fixes the words, the forbidden list sets the floor, and the microcopy rules cover each element and state. Built from the research, not from taste. On this stage only text changes, never the markup.

Tone orientation

Sift sounds like a trusted analyst colleague who shows their work: plain, exact, and honest about limits. Not a salesperson, so no overclaiming. Not a cheerleader, so no celebration.

Grounded in personas.md O10 ("one bad synthesis experience destroys trust permanently") and the emotion the product designs for, "Confidence and calm instead of overload" (CLAUDE.md).


Principles

Four rules you can write a button from. Each carries a line that keeps it, a line that breaks it, and the source it comes from.

Principle 1
Earn the claim, do not assert it

State plainly what the evidence shows and let the number carry the weight; never claim more certainty than the evidence gives, and say so out loud when it is thin.

Written to the rule
  • "Thin evidence. Six mentions is a weak signal, not a confirmed pattern."
  • "n=42" beside the theme; "low signal" beside "n=4".
Breaks the rule
  • "AI identified this as your top priority."
  • A theme shown the same whether it rests on 4 mentions or 400.
Why. Design Principle 1 "Show your work" and 5 "Traceable or it doesn't exist" (CLAUDE.md); personas.md O10, "a tool that admits 'this is based on 3 data points' earns trust when it says 'this is based on 200'". Where every rival sounds certain ("30% better than live teams", Canny; "Wisdom AI", Enterpret, competitors.md), Sift differentiates by sounding honest.
Principle 2
Speak the customer's words, not the product's

Name themes and problems in the customer's plain language, the way it was actually said; never re-dress feedback in product or marketing vocabulary.

Written to the rule
  • "Onboarding is confusing"
  • "New users cannot tell what to do first."
Breaks the rule
  • "Activation-funnel friction opportunities"
  • "Drive delight in the first-run journey."
Why. The trust chain breaks the moment the language sounds invented: "if the themes sound like they were written by a marketing team, not derived from real tickets, Alex will not trust them" (personas.md, Persona A). It sharpens the best competitor register worth beating, Dovetail's "Build with facts, not vibes": Sift's facts are the customer's own words.
Principle 3
Calm, not loud

Say it once, in a level voice; carry weight with plain statements and hierarchy, never with exclamation, celebration, or alarm.

Written to the rule
  • "Share link ready."
  • "Synthesis failed. Your sources are still connected, so nothing is lost."
Breaks the rule
  • "Success! Your brief is live."
  • "Oops, something went wrong!"
Why. Design Principle 2 "Calm under density ... hierarchy, weight, and whitespace do the work of focus, not color, badges, or alerts" (CLAUDE.md), and the emotion "Confidence and calm instead of overload". The reader works in short focused sessions ("10-15 focused minutes", personas.md O8); loud copy is friction, not delight.
Principle 4
Every state names the next move

Every screen and state tells the reader what to do next; an error, an empty, or a wait names the one action that moves forward, so the reader is never stranded.

Written to the rule
  • "No sources connected yet. Connect a source to see your first synthesis." with a "Connect a source" action.
  • "Synthesis failed ... Try again, or check your sources."
Breaks the rule
  • "Something went wrong." (a full stop with no way out)
  • An empty state that explains the emptiness but offers no action.
Why. Design Principle 4 "One decision at a time ... every view has a clear 'what should I do next' orientation" (CLAUDE.md), realized in the IA as the no-dead-end rule. It also serves activation: "if the PM cannot reach a synthesis output with their own data within 20 minutes, they leave" (personas.md O12).

Dictionary

One concept, one word. The terms are the IA core entities and the research vocabulary, not new inventions. This settles the twelve divergences the Step 1 inventory surfaced; each DIV-n points back to microcopy.md.

Use thisNot thisWhy
feedback; feedback item / itemsignal item, a signal (as a count)Core entity "Feedback item". Keep the countable unit to one word. (DIV-1)
signal (only in "low signal" and "signal rank")signal as a count; "signal volume / usage""signal" carries evidence strength, not raw count. "low signal" is the locked confidence badge, D2. (DIV-1)
source (types: live connection, batch import)integration, connectorCore entity "Source". You connect sources; the Sources screen lists them. (DIV-2)
connect (a source)add a sourceOne verb to bring a source in. (DIV-3)
themecluster, topic, tagCore entity "Theme"; the synthesis output the reader reads.
evidence; feedback item; citationthe three as synonymsChain: theme, to evidence items, to one feedback item; a citation is the numbered pointer.
brief; evidence brief (first mention, public title)report, summary, deckCore entity "Evidence brief". Short form in-app, full form to introduce it. (DIV-10)
build (a brief)create, generate, make a briefOne verb to make a brief. "generate" stays only for the share link. (DIV-5)
priority; Set priority; Recommended priority"rank / ranking" as the nounCore entity "Prioritization". "signal rank" is the sort; "priority" is the decision. (DIV-12)
workspaceaccount (as the team container), org, tenantCore entity "Workspace". A person signs up and gets a workspace. (DIV-7)
confidence: n=X plus low signalscore, rating, "AI confidence %"D2 day-one scope: count plus the badge. No invented score.
scrub / scrubbed (PII)redact, strip, mask, anonymize"PII scrubbed by default" is the locked product phrase (CLAUDE.md). (DIV-6)
Log in / Log out; Sign up; Start free (Home only)Sign in; Sign out for log out; RegisterSessions log in and out; acquisition signs up; the marketing entry is "Start free". (DIV-7)
Create workspace (the sign-up action)Create your accountSign-up creates a workspace, the product's unit. (DIV-7)
Try againRetry, Retry sync, Retry authorizationOne recovery label; the screen makes the object obvious. (DIV-4)
Turn customer feedback into decisions you can defend. (tagline)"Feedback synthesis for product teams"; "Customer feedback, synthesized"One value line for public surfaces, one short descriptor ("Customer feedback synthesis") for footers. (DIV-8)

Person and address

You. The reader is "you", second person and direct: "your feedback", "you can review this in Data and privacy".

Sift. The product is "Sift", third person, for what it does: "Sift clusters your feedback".

We. Only the company and its people, that is support, legal, and planned downtime: "we could not build the picture this time", "we expect to be back shortly". Never "I".

Casing and numbers

Capitalize the nav destinations as proper section names: Synthesis, Sources, Briefs, Account. Lowercase the same words as common nouns: "your synthesis", "a source".

Confidence is lowercase n=42. Thousands take a comma: 3,750, 5,000.

PII is uppercase, as are CSV, OAuth, SSO, GDPR, CCPA, SOC 2, DPA. Product names stay as given: Intercom, Zendesk, Gong, Salesforce. Time reads "2 days ago".


Forbidden

What Sift never writes. Without this list the model default returns with every new prompt: enthusiasm, exclamation marks, emoji, and celebration. Each row gives the fix.

NeverWas, then should beWhy
Stock error cliches"Something went wrong." to "Could not load this page."Vague and evasive; name what failed. Principle 1. (DIV-9)
"Oops" / "Uh-oh" / "Whoops""Oops, something went wrong!" to "Could not load this page."Jokey on a trust surface. Principle 3.
Greetings and celebration"Welcome aboard!" to "Your workspace is ready."Sift states the fact and the next step. Principle 3.
The word "successfully""Saved successfully." to "Saved."If it saved, say so; the word is filler. Principle 3.
Exclamation marks in system copy"Intercom connected!" to "Intercom connected."Level voice. Principle 3.
Emoji in system messages"Import complete." plus a check emoji, to "Import complete."Calm under density; no decoration in copy. Principle 3.
Motivational or marketing tone in-app"Start your journey to better decisions." to "Connect a source to see your first synthesis."In-app copy points at the next step. Principle 4.
Overclaiming the AI"AI identified your top priority." to "Onboarding is confusing. n=42."Let the evidence make the claim. Principle 1.
Hype adjectives (powerful, seamless, effortless)"Powerful, seamless synthesis." to "Feedback clustered into ranked themes, each with the evidence behind it."Specifics earn trust; adjectives ask for it. Principle 1.
"just" / "simply" as minimizers"Just connect a source." to "Connect a source."Minimizers presume it is easy. Principle 3.
Blaming the reader"You entered an invalid email." to "Enter a work email."Say what to fix, not what they did wrong. Principle 4.
Filler "please""Please try again." to "Try again."Plain instruction. Principle 3.

Microcopy

The rule for each kind of element, and the tone for each state. Each rule is checked against the principles and the dictionary above, and each carries one real line from the product.

Button and action
The verb of the action, and you can see the result in it. No bare "OK" or "Submit" where a specific verb and object fit.
Written to the rule: "Connect a source", "Build brief", "Generate share link", "Copy quote". Not: "OK", "Submit", "Go".
Screen heading and subhead
The h1 names the place in dictionary words. The subhead says what you can do here and why, in one plain sentence.
Written to the rule: "Synthesis" plus "Your feedback, clustered into ranked themes. Open one to trace the evidence behind it." Not: "Welcome to your dashboard".
Form field
The label says what to enter, in the reader's words. The placeholder shows the shape, not an instruction. A validation error says the one thing to fix, not what the reader did wrong.
Written to the rule: label "Work email", validation "Enter a work email." Not: "Invalid input", "You entered an invalid email".
Confidence and honesty note
State the strength as a number, and when it is thin, say so plainly right next to it. Principle 1 as microcopy, mandatory under D2.
Written to the rule: "n=6 low signal" plus "Thin evidence. Six mentions is a weak signal, not a confirmed pattern. Treat it as a lead to watch, not a decision."
Empty state
Say why it is empty and give the one action that fills it. An empty is a starting line, not a wall.
Written to the rule: "No sources connected" plus "Connect a source to bring your feedback in ..." and a "Connect a source" action. Not: "No data."
Error state
Say what happened and what to do next. Reassure with a fact (nothing is lost), never a joke or an apology. One recovery action, plus a way back.
Written to the rule: "Synthesis failed. Your sources are still connected, so nothing is lost. Try again, or check your sources." Not: "Something went wrong", "Oops".
Loading state
A wait stays silent (a skeleton) or says exactly what is running. It never fills the silence with chatter.
Written to the rule: "Synthesizing your feedback. Ingesting, scrubbing PII, and clustering into themes." Not: "Hang tight!", "Working some magic".
Success and confirmation
Name the fact and the next step. Do not celebrate, and do not say "successfully".
Written to the rule: "Share link ready." plus "Copy" and "Preview brief". Not: "Success!", "Your brief is live".
Dangerous or irreversible action
Before the action, say what will happen and what cannot be undone. The confirm button names the specific act, not "Yes".
Written to the rule: "Disconnecting stops the live sync and removes the connection ..." plus a "Disconnect Intercom" button. Not: a confirm that reads "OK".
Notice and guard line
When Sift withholds or flags something for honesty, it states the reason and what still holds. The honesty is the point, so the line is plain and specific.
Written to the rule: "The raw quote was scrubbed beyond display to protect personal data ... The theme still stands on its other evidence."

Tone by state

StateTone ruleOne line
Success (base)State the fact, point at the next step. No celebration."Share link ready."
EmptySay why, give the one action."No sources connected" plus "Connect a source".
LoadingSilent skeleton, or name what runs. No chatter."Synthesizing your feedback ..."
ErrorWhat happened, what to do, one reassuring fact. No joke, no apology."Synthesis failed ... Try again".
Low signal / thinAdmit the weakness plainly, keep it open."Thin evidence ... a lead to watch, not a decision."
Redacted / withheldName the reason and what still holds."scrubbed beyond display ... the theme still stands".
DangerousWarn before, name what cannot be undone; confirm verb is the act."Disconnect Intercom".

From the inventory: twelve divergences resolved

The full per-screen text inventory lives in microcopy.md. Its payload, the divergences the one table surfaced and the canon each resolves to:

DIVCanonInstead of
1feedback / feedback item / itemsignal item; signal as a count
2sourceintegration, connection (as the source)
3Connect a sourceAdd source
4Try againRetry / Retry sync / Retry authorization
5build a briefcreate / generate / new brief
6scrub / scrubbedredact / strip / mask
7Log in / Log out; Sign up; Create workspaceSign in; Sign out; Create your account
8Turn customer feedback into decisions you can defend.three different taglines
9Could not load this pageSomething went wrong
10brief (evidence brief at first mention)report / summary
11"nothing to synthesize yet" vs "No sources connected"two near-identical titles
12priority (Set priority / Recommended priority)mixing priority with "rank"