Client communication

The person you want in Slack
at 3pm on a deadline.

Written proof — organized by what it shows about how I work, not which tool I typed it into.

Privacy-first. All client names, company names, emails, and sensitive details are anonymised before publishing. The communication style is real. The identifying info is not.

01 Clear client updates 02 Problem solving 03 Task ownership 04 Calm in the chaos 05 What happened after
01

Clear client updates

Proactive communication before a client has to ask. Status, changes, context — delivered clearly.

Sent a Loom to answer a question — noticed a separate form bug in the process

Proves: Proactive attention to detail, goes beyond the ask

Sent the meeting recording unprompted after resolving a site video issue

Proves: Follow-through, client care, clear documentation

Client needed site help — done in two days, no unnecessary back-and-forth

Proves: Responsiveness, clean delivery

Funnel wasn't ready for ads yet — said so clearly, re-attached the instructions

Proves: Expectation management, multi-party coordination

Funnel mockup delivered with the client's earlier feedback already built in

Proves: Proactive delivery, multi-stakeholder coordination

Was out of office — replied clearly with two options, client booked a call the same evening

Proves: Responsiveness, professional handling

Multi-party go-live coordination — confirmed launch-ready and answered every open question with documentation

Proves: Multi-stakeholder clarity, launch coordination

Delivered all funnel markup links — then explained the full VSL process without being asked

Proves: Proactive communication, client education

02

Problem solving

Something broke, threw an error, or didn't make sense. Here's what happened instead of silence.

Email + Loom

Google Calendar stuck spinning in GHL — diagnosed it, sent a Loom walkthrough

Proves: Technical depth, visual communication over confusing text

Kajabi/HighLevel Contact ID mismatch in Zapier — caught it, fixed it, explained exactly why

Proves: Cross-platform knowledge, precise diagnosis

Zapier threw an error. Diagnosed it as a false positive before anyone panicked.

Proves: Technical clarity, reassuring communication

Client was sending members to the wrong link — identified the correct portal and documented it with a screenshot

Proves: Platform knowledge, fast clear diagnosis

Order form error reported — fixed smart list access immediately, flagged the coupon issue as a separate problem

Proves: Methodical problem-solving, clear triage

03

Task ownership

I owned the next step, moved things forward, and didn't wait to be asked twice.

Domain transfer was dragging. Bought it myself and handled the move.

Proves: Initiative, going well beyond the brief

Answered a GHL support question — then threw something in they didn't ask for

Proves: Thoroughness, client satisfaction

Funnel was ready. Introduced the client to a media buyer to move to the next phase.

Proves: Strategic thinking, end-to-end ownership

Three team members needed analytics and pixel access — all added same day, no follow-up needed

Proves: Responsiveness, task ownership

Two separate tasks: video embedded into the funnel, team member access granted. Both done.

Proves: Efficiency, no unnecessary back-and-forth

Client asked for a URL change — duplicated the original first so the default funnel stayed completely intact

Proves: Careful execution, initiative

Full GHL account transfer — funnels moved, domain re-attached, products recreated, back-end notes included

Proves: Technical depth, clean client handover

Structured client onboarding email with three tailored intake form links, clearly labelled by service type

Proves: Organised onboarding, professional client intake

Tools shown

Email · Loom

Every message is real. Sent in real client projects.

Clients

Fully anonymised

Full unredacted versions available to verified employers on request.

What this proves

I communicate. Actually.

Not once a week. Not under pressure. Always.

04

Calm in the chaos

Urgent requests. Difficult clients. High-pressure moments. Here's what staying useful actually looks like.

Subject line said "ASAP." Reply identified the exact DNS record causing the outage.

Proves: Technical knowledge, composure under urgency

Client demanded a full refund. Cited the contract, explained the work done, kept the door open.

Proves: Professionalism, conflict resolution, clear professional writing

05

What happened after

This arrived unprompted, two weeks after the funnel launched.

"The amount of inquiries that we've gotten in the last two weeks has been 5 times more than we've ever had."

Sent unprompted, two weeks after launch. The VSL hadn't even gone live yet.

Proves: The work delivers. Not just the process.

Let's connect.

I like to talk about marketing, ops and especially Claude.

Send me a DM on Facebook

Prefer email? jovan@jovanstojanov.com