what it catches
what is said, what is missing, and what the client is leaning toward.
the page is built for the moment when a client sends a message that sounds cooperative but still leaves the next step blurry.
practitioner front door
client intake gets the first read.
when a client sends a screenshot, a messy intake email, or a mixed-signal thread, the first job is not drafting. it is reading carefully enough to know what the next session should actually address.
this page is the narrow route for coaches, mediators, trainers, recruiters, hr consultants, and communication specialists who need a structured read before they reply, schedule, or hand the case back to the client.
screenshots
intake emails
mixed-signal threads
free front door into tells
why this page exists
the wrong first screen is a conversion leak.
if the intake note is hiding the real issue, the next reply and next session both get harder.
what it is not
not a blank chat box, not a generic summary, not a feeling replacement.
generic ai can help you draft. tells is narrower: it helps you read one message and decide whether the real issue needs a deeper paid read.
best fit
coaches, mediators, trainers, recruiters, hr consultants.
anyone whose work starts with a message, screenshot, or thread and ends in a human decision instead of a generic rewrite.
paid step
move into tells when the same person keeps becoming the problem.
the free route is for one message. the paid route is for a recurring person, a loaded thread, or a pattern that keeps coming back between sessions.
faq
three questions this page should answer fast.
should i use client intake for one client message?
yes, when you need to read a single screenshot, email, or thread before the next reply or session. use the wider tools only if the pattern keeps repeating.
what if the client wants a draft, not a read?
that is usually the wrong first click. read the message first, then decide whether you need to draft, escalate, or hold.
where should practitioner traffic go next?
send it to the practitioner page if the workflow is client-facing. send it to the signal toolkit if the user wants the narrow free routes first.