Home / Guides / AI prompts and routines

A customer success weekly report your manager will actually read

By Draft First. Updated October 2026

Weekly reports tend to grow until nobody reads them. Ten bullets about meetings held and tickets closed tell your manager you were busy, not what they need to know. A good weekly update fits on a phone screen and answers three questions: what went well, what's at risk, and what do you need.

The format

• Wins (one or two): renewals, saves, a happy customer, a fix shipped.
• Risks (one or two): accounts slipping, with what you're doing about it.
• Asks: a decision, an intro, help from another team. Or "none".
• Numbers: the three or four your team is measured on, against target.

Five bullets, plus numbers. If it's longer, the important line gets lost.

A sample

Week of Oct 12
Win: Larkspur escalation closed; Tom Ng emailed thanks. Renewal on track.
Risk: Halden usage down 24%, CFO silent 5 days. Call booked Tue.
Risk: Coastline signer changed; meeting new COO Nov 2.
Ask: need a fix date for exports (affects 14 accounts) by Friday.
Numbers: backlog 38 (target under 45) | first response 1.6h (under 2h)
         renewals this month 6 of 7 signed

Tips

• Lead with the ask if it's urgent.
• Skip adjectives about effort. "Worked hard on" adds nothing.
• Same format every week, so your manager knows where to look.
• Keep a running notes doc during the week. Three words a day is enough to remember Friday.

Drafting it with AI

Friday afternoon is the worst time to reconstruct your week from memory. An agent can do the reconstructing:

Every Friday at 2pm, draft my weekly update from [CRM changes, closed
tickets, calendar, my notes doc]: up to 2 wins, up to 2 risks with my
next step, asks (or "none"), and these numbers vs target: [metrics].
Five bullets max plus numbers. No adjectives about effort. Source every
number. Draft only, I'll edit and send.

This is the Friday Update to Your Manager play in The CS Agent Playbook. If you manage people, the same habit helps with 1:1 prep.

Questions

What should a CSM weekly report include?

Wins, risks with next steps, asks for help, and the few numbers your team is measured on.

How long should a weekly update be?

About five bullets plus key numbers. Short enough to read on a phone.

Can AI write my weekly report?

It can draft it from your CRM, tickets and notes. Edit it before you send, especially the risks and asks.