Incident Updates is a Clone skill that gives your clone a reference for escalating critical SaaS support issues and writing customer updates during incidents, following clear communication standards. Support agent, customer success and engineer clones use it to keep customers informed while a fix is underway. It needs no app connection.
Draft the next customer update. Dashboards are slow, cause found, fix rolling out.
Here is the update in the standard format: what happened, who is affected, what we are doing and when to expect the next update.
No forms, no workflow builder. Ask your clone the way you'd ask a teammate.
Tell your clone the symptoms, impact and current status of the incident.
It drafts the message using your incident format, with a clear next-update time.
Ask for each new update as the incident moves forward, through to resolution.
Skills belong to roles. These clones put Incident Updates to work as part of their job.
It is using AI to write the updates customers see during a service incident. With Clone, your clone drafts status updates that follow your standards and helps escalate critical issues the right way.
No. Incident Updates works without a connection. Share the latest facts and the clone drafts the update.
Support agent, customer success manager and engineer clones use it whenever an incident affects customers.
What is happening, who is affected, what the team is doing, any workaround and when the next update will come. The clone checks each draft for all five.
Updated October 2026