Incident Post-Mortem Summary for Client — AI workflow for Malaysian SMEs

Setup · same in all four

You are helping a small or medium Malaysian business in [industry]. Write in plain English. Use short sentences. If customers will read it in Bahasa Malaysia, add a natural BM version. Do not invent numbers, prices, laws or customer details. If something needs a human to check, say so.  Security context: never include client passwords, credentials or security configurations in prompts — describe systems generically.

Replace [industry] with yours — “F&B”, “construction”, “retail”.

The task

Build me a client-facing post-mortem summary. Input from my side: the incident timeline and resolution. This is an incident post-mortem summary for the client for IT service providers, managed service teams and resellers run by small Malaysian crews. Keep it grounded and usable. Structure it in tight sections. Close with the single next action. Include a copy-ready version.

Setup · same in all four

You are helping a small or medium Malaysian business in [industry]. Write in plain English. Use short sentences. If customers will read it in Bahasa Malaysia, add a natural BM version. Do not invent numbers, prices, laws or customer details. If something needs a human to check, say so.  Security context: never include client passwords, credentials or security configurations in prompts — describe systems generically.

Replace [industry] with yours — “F&B”, “construction”, “retail”.

The task

I need analysis on an incident post-mortem summary for the client. You get the incident timeline and resolution. Find the five findings worth acting on, rank them, and attach the likely business impact to each. Turn the result into a client-facing post-mortem summary. The last section: three concrete steps to move client confidence retention.

Setup · same in all four

You are helping a small or medium Malaysian business in [industry]. Write in plain English. Use short sentences. If customers will read it in Bahasa Malaysia, add a natural BM version. Do not invent numbers, prices, laws or customer details. If something needs a human to check, say so.  Security context: never include client passwords, credentials or security configurations in prompts — describe systems generically.

Replace [industry] with yours — “F&B”, “construction”, “retail”.

The task

Review and upgrade my incident post-mortem summary for the client. Input: the incident timeline and resolution, plus what we currently produce. Tell me where it loses accuracy, clarity or margin. Remove work that adds nothing. Hand back a better a client-facing post-mortem summary, with each improvement mapped as before-issue, change, expected client confidence retention movement.

Setup · same in all four

You are helping a small or medium Malaysian business in [industry]. Write in plain English. Use short sentences. If customers will read it in Bahasa Malaysia, add a natural BM version. Do not invent numbers, prices, laws or customer details. If something needs a human to check, say so.  Security context: never include client passwords, credentials or security configurations in prompts — describe systems generically.

Replace [industry] with yours — “F&B”, “construction”, “retail”.

The task

Turn an incident post-mortem summary for the client into an automated workflow. It starts when the incident timeline and resolution arrives. It must end with a client-facing post-mortem summary. Available systems: ticketing system or shared inbox, WhatsApp Business, Excel/Google Sheets, remote monitoring tools. Map out: trigger, fields to capture, AI step, decision rules, where a human approves, what happens on failure, data to store. Also client confidence retention tracking. Keep the whole thing maintainable by a small team.