Client Success

CSM Responsibilities & Expectations

Platform: Client Success
Owner: CSM
Assignee: Kyle
Supports: Operations, SEO Specialist, GBP Specialist, Website Specialist, LSA Specialist

CSM Responsibilities & Expectations

Last Updated: June 2026 Version: 1.0 Owner: CSM

This is the high-level role view for the Client Success Manager seat. Use this as the pinned job description, expectation reference, and onboarding standard for anyone owning CSM responsibilities at Tekton.

What

The Client Success Manager owns the client relationship after the sale. This role is responsible for making sure clients feel heard, informed, guided, and followed up with.

The CSM is not expected to personally know the answer to every SEO, website, GBP, LSA, billing, ads, or technical question on the spot. Tekton has specialists for that.

The CSM is expected to own getting the right answer back to the client as quickly as possible.

Routing a question to a specialist does not transfer ownership of the client response. If a client asks an SEO question and the CSM messages the SEO lead, the CSM still owns the client getting an answer. “Waiting on SEO” is not an acceptable reason for a delayed client update.

The CSM must acknowledge the client, route the question, track the answer, follow up internally, escalate when needed, and update the client by the promised time.

Specialists are expected to respond promptly too, but the CSM owns the client relationship. If the internal response is delayed, the CSM escalates. The client should never be left waiting because an internal teammate has not answered yet.

Client communication is not a side task. It is a primary responsibility of the role.

The standard is simple: no active client should be left wondering whether Tekton saw their message.

Who owns it

Primary owner: CSM Backup owner: Operations Lead or Nick when the CSM is unavailable Specialist support: SEO, GBP, Website, LSA, Ads, or Operations specialists provide answers and execution support through TaskTracker or the approved internal channel.

The CSM remains the client-facing owner unless Nick explicitly assigns the conversation elsewhere.

Core responsibility

The CSM’s job is to protect client trust.

That means:

Responding to client messages quickly.
Making clients feel like there is a real person watching their account.
Translating internal work into simple client updates.
Catching client confusion before it becomes frustration.
Escalating blockers before they become missed commitments.
Keeping TaskTracker, GHL, Discord, and client-facing follow-ups aligned.
Making sure no client relationship goes silent.

The CSM is the connective tissue between the client and the delivery team.

Communication standards

1-hour acknowledgment rule

Every client message must receive an initial acknowledgment within 1 business hour during normal business hours.

This does not mean every issue must be fully solved within one hour. It means the client must know we saw it and know what happens next.

Acceptable acknowledgment examples:

Got it, I’m checking on this and will update you by 2:30.

Thanks for sending this over. I’m going to confirm with the team and circle back today.

I see this. I don’t want to guess, so I’m checking the account and will send you a real answer by tomorrow morning.

Unacceptable patterns:

Seeing the message and planning to respond later without tracking it.
Waiting until the full answer is ready before saying anything.
Assuming the client knows we are working on it.
Letting a message sit because the answer depends on another teammate.
Leaving Nick or the client to discover an unanswered message.

Business-hour scope

The 1-hour acknowledgment rule applies during normal Tekton business hours.

If a client messages after hours, acknowledge it by the next business morning unless it is urgent enough to escalate immediately.

Full answer standard

If the CSM cannot answer fully within the first response, the CSM must give the client a specific next update time.

Good:

I’m checking with Jakob on this. I’ll update you by 3 PM today.

Bad:

I’ll look into it.

Good:

We need to verify this inside GHL before I give you an answer. I’ll send the update tomorrow morning.

Bad:

Let me check.

A vague promise is not a next step. A specific update time is a next step.

Daily required habits

Morning sweep

Before starting other work, the CSM checks all client communication channels and identifies:

New client messages.
Open client questions.
Messages waiting on internal answers.
Clients who need an update today.
Any message that has not been acknowledged.

Midday sweep

The CSM checks again during the middle of the day so client responses do not sit unnoticed.

End-of-day sweep

Before ending work, the CSM confirms one of two things in the assigned Discord channel or operating thread:

All client messages are cleared.

Or:

Open client items: [client], [what they need], [who owns the answer], [next update time].

This is not optional. The end-of-day sweep is how Tekton prevents silent client drift.

Message handling workflow

Every client message gets one of three actions within one business hour:

Answer it fully if the answer is known and safe to send.
Acknowledge it with a specific update time if more work or confirmation is needed.
Escalate it if the CSM is blocked, unsure, or the issue has client-risk.

No client message should sit unacknowledged.

If the message needs specialist input

The CSM should:

Acknowledge the client.
Create or update the TaskTracker task if execution is needed.
Tag the correct specialist internally.
Give the client a realistic update time.
Follow up by that update time, even if the answer is still incomplete.

Example client reply:

Got it. I’m checking this with our SEO team so I don’t give you a half-answer. I’ll update you by tomorrow morning either way.

Example internal task note:

Client asked why rankings dropped for [keyword/location]. Need SEO review and client-safe explanation. Client promised update by tomorrow morning.

If the message is urgent

Urgent items must be escalated the same day.

Urgent examples:

Client says leads stopped.
Client says the website is down or broken.
Client is upset, threatening cancellation, or losing trust.
Billing, payment, or contract confusion.
Google Business Profile suspension or major visibility issue.
LSA, Ads, GHL, or phone-tracking issue affecting active lead flow.
A client asks the same question more than once without a real answer.

Escalation means telling Nick or the correct owner directly with enough context to act.

Bad escalation:

Client is asking about leads.

Good escalation:

P1: [Client] says calls dropped this week. I acknowledged them and promised an update by 3 PM. Need LSA/GHL check: tracking number, recent lead volume, missed calls, campaign status.

Client-facing tone

The CSM should sound calm, clear, and accountable.

Use:

Plain English.
Specific next steps.
Short updates.
Honest timelines.
Ownership language.

Avoid:

Overexplaining internal complexity.
Blaming specialists, tools, Google, GHL, or the client.
Saying “I’ll look into it” without a next update time.
Making promises before the work is verified.
Letting uncertainty turn into silence.

Good CSM tone:

I see what you mean. I’m going to check the tracking and the recent lead activity before I give you an answer. I’ll update you by 3 today.

Poor CSM tone:

I’m not sure, I’ll have to ask the team.

Good CSM tone:

We found the issue. The form is working, but the notification was not firing correctly. We’re fixing that now and I’ll confirm once it has been tested.

Poor CSM tone:

It should be fixed now.

Client ownership areas

The CSM is not just an inbox responder. The CSM owns the client relationship after the sale and makes sure clients always know where things stand.

Sales-to-CSM handoff

Before the first client touch after a sale, the CSM should know:

package purchased and active scope
client goals, target services, and target markets
any promises, deadlines, or sensitive context from sales
required access still missing
first next step the client should expect

The standard is simple: the client should never feel like they paid and then had to re-explain the deal to Tekton.

Client health and retention risk

The CSM owns spotting relationship risk early. Warning signs include:

client confusion about what Tekton is doing
frustration about lead flow, lead quality, rankings, or communication
repeated urgent requests
missed reports, missed calls, or stale follow-ups
cancellation, pause, refund, or “what are we paying for?” language
work blocked by access or client response for more than a few business days

The CSM does not need to solve every issue alone, but must surface risk quickly, document it, and escalate when needed.

Scope, billing, and change-request control

The CSM protects the package boundary. When a client asks for work outside the normal plan, the CSM should:

acknowledge the ask
clarify whether it is included, a paid add-on, or needs Nick/Ops approval
route production work through TaskTracker
avoid promising free work, timelines, refunds, discounts, or package changes without approval

Access and credential ownership

The CSM owns collecting client-side access and keeping work unblocked. This includes GBP, GA4/GSC, domain/DNS, website/CMS, Meta, GHL, Google Workspace, and any third-party tool needed for delivery.

The CSM should ask clearly, follow up until received, make sure access is stored in the correct system, and escalate if missing access blocks fulfillment.

Approval and launch communication

The CSM owns the client-facing loop around previews, approvals, launch notices, and completion messages. Specialists own technical sign-off. Nick/Ops approves high-risk live actions where required.

The CSM should not announce a website, GBP change, GHL flow, LSA change, or other visible change as finished until the responsible specialist has verified it.

Lead quality feedback loop

Tekton sells more leads, more estimates, and more consistent work. The CSM owns getting real-world feedback from the client, not just forwarding reports.

The CSM should ask whether leads were real, booked, quoted, spam, out of area, wrong service, or low quality. Patterns should be documented and routed to the LSA, SEO, GHL, GBP, or website owner.

Client record hygiene

The CSM keeps the client-facing truth current across GHL, TaskTracker, Discord, and reporting notes. Call notes, blockers, next update dates, open requests, report links, and satisfaction/risk signals should be findable by the team.

Internal ownership rules

The CSM owns the client conversation. Specialists own their technical lanes.

CSM owns

Client inbox monitoring.
Client acknowledgment and follow-up.
Monthly reporting delivery.
Monthly client call scheduling and follow-through.
Client questions and concerns.
Client-safe summaries of work completed.
TaskTracker follow-up when client asks require execution.
Escalation when client trust is at risk.

Specialists own

SEO analysis and implementation.
GBP optimization and citation work.
Website changes and QA.
LSA and ads execution.
GHL technical fixes.
Data pulls and specialist recommendations.

The CSM does not need to be the expert in every lane. The CSM does need to keep the client informed while the expert works.

Required systems

TaskTracker

TaskTracker is the source of truth for client execution work.

The CSM must create or update a task when a client message requires:

A deliverable.
A specialist review.
A website change.
A GBP change.
A GHL fix.
A report.
A follow-up that cannot be completed immediately.

A task should include:

Client name.
Client request.
Internal owner.
Client promise or update time.
Definition of done.
Relevant links or screenshots.

GoHighLevel

GHL is the client communication record when the conversation happens by SMS, email, call, or client inbox.

The CSM must make sure important touches are logged or visible in GHL.

Discord

Discord is for internal coordination and accountability.

The CSM’s Discord channel should have this document pinned or attached so expectations are visible.

Tekton Wiki

This page is the role expectation document. If the standard changes, update this page instead of relying on scattered verbal reminders.

Performance expectations

Non-negotiables

Client messages acknowledged within 1 business hour.
No untracked client follow-ups.
No end-of-day client inbox left unswept.
No vague client promises without a next update time.
No silent blockers.
No missed client updates discovered by Nick after the fact.
Client concerns escalated before they become churn risk.

Quality bar

The CSM is meeting expectations when:

Clients know what is happening.
Nick does not have to chase basic follow-up.
Open client items are visible before they become problems.
Specialists receive clear internal requests with client context.
Monthly reports and communication rhythm happen consistently.
Clients feel like Tekton is paying attention.

The CSM is below expectations when:

Client messages sit unanswered.
Nick finds missed messages first.
A client has to ask twice for the same thing.
Internal blockers are used as a reason for client silence.
Updates are vague, late, or not sent.
Follow-ups live in memory instead of TaskTracker.

Definition of done

This role is being performed correctly when:

All client messages are acknowledged within one business hour during business hours.
Every open client item has an owner, next step, and update time.
End-of-day client communication checks are posted consistently.
Client tasks are tracked in TaskTracker when execution is required.
GHL reflects important calls, SMS, emails, and notes.
Specialists have enough context to answer or execute without guessing.
Nick can look at the CSM channel and know whether client communication is under control.

If those conditions are not true, the CSM system is not working yet.