One owner approves the message
Client success owns trigger, channel, compliance review, delivery state, and portal-safe wording.
Incident communication
Automation Pause Incident Communication Guide
Automation Pause Incident Communication Guide for managing ZartsAlgo SMS, email, portal, approval, incident, report digest, and outreach communication workflows at larger client volume.
Communication contract
What this message path must protect.
Use this guide before connecting SMS, email, portal updates, report digests, client approvals, incident notices, or outreach campaigns.
Name the communication risk
The main risk is allowing failed delivery, missing replies, or opt-outs to go unnoticed.
Keep internal notes separate
AI drafts, raw provider payloads, private customer details, and incident evidence stay internal until a safe summary is approved.
Track every message event
At higher volume, every send, failure, reply, approval, pause, and opt-out needs a source, owner, timestamp, and recovery rule.
Baseline controls
Checks that apply to every communication workflow.
- Confirm trigger, channel, recipient, consent, owner, and source before sending.
- Use approved templates for SMS, email, review requests, incident notices, and report digests.
- Keep portal-visible wording short, factual, sourced, and free of raw payloads.
- Attach every message to lead, client, project, report, incident, or approval record.
- Track delivery state, reply state, failure reason, opt-out state, and next action.
- Pause automated sending when provider freshness, privacy, or compliance is uncertain.
- Use internal drafts for AI summaries until a review step marks them safe.
- Record owner approval before publishing client updates or ROI proof in the portal.
- Retest desktop, mobile, admin, portal, and message copy after workflow changes.
- Document rollback and escalation paths for every automated communication.
Topic checks
Specific checks for this message path.
- Publish portal updates only after owner approval and privacy review.
- Log delivery state, reply state, failure reason, and next action.
- Pause automation when provider data, revenue proof, or incident facts are not verified.
- Attach communication records to lead, client, project, report, approval, or incident records.
- Use client-safe language for incident, stale-data, and ROI caveat messages.
- Preserve internal drafts and raw payloads outside portal-visible summaries.
- Retest admin, portal, mobile, and message copy after changes.
- Record escalation owner and rollback path for automated sequences.
- Measure response time, approval time, report view, review request outcome, and booked result.
Checkpoints
Turn the guide into a review checklist.
Each checkpoint can become a template rule, approval gate, delivery check, incident step, or portal-safe publishing rule.
Communication checkpoint
Publish portal updates only after owner approval and privacy review.
Communication checkpoint
Log delivery state, reply state, failure reason, and next action.
Communication checkpoint
Pause automation when provider data, revenue proof, or incident facts are not verified.
Communication checkpoint
Attach communication records to lead, client, project, report, approval, or incident records.
Communication checkpoint
Use client-safe language for incident, stale-data, and ROI caveat messages.
Communication checkpoint
Preserve internal drafts and raw payloads outside portal-visible summaries.
Communication checkpoint
Retest admin, portal, mobile, and message copy after changes.
Communication checkpoint
Record escalation owner and rollback path for automated sequences.
Communication checkpoint
Measure response time, approval time, report view, review request outcome, and booked result.
Data hooks
Tables and runtime sources to connect later.
Public pages stay static; live message state should be handled by admin, portal, queues, and prepared database reads.
tasks
Connect this runtime source only through admin, queue, provider, or portal-safe summarized views.
leads
Connect this runtime source only through admin, queue, provider, or portal-safe summarized views.
clients
Connect this runtime source only through admin, queue, provider, or portal-safe summarized views.
projects
Connect this runtime source only through admin, queue, provider, or portal-safe summarized views.
reports
Connect this runtime source only through admin, queue, provider, or portal-safe summarized views.
report_periods
Connect this runtime source only through admin, queue, provider, or portal-safe summarized views.
report_notes
Connect this runtime source only through admin, queue, provider, or portal-safe summarized views.
incidents
Connect this runtime source only through admin, queue, provider, or portal-safe summarized views.
Outputs
Make communication measurable and recoverable.
Useful communication operations show what was sent, what happened next, and what became client-safe proof.
Delivery status
This output should preserve owner, source, channel, timestamp, client-safe status, and follow-up rule.
Reply capture
This output should preserve owner, source, channel, timestamp, client-safe status, and follow-up rule.
Owner task
This output should preserve owner, source, channel, timestamp, client-safe status, and follow-up rule.
Approval state
This output should preserve owner, source, channel, timestamp, client-safe status, and follow-up rule.
Portal-safe update
This output should preserve owner, source, channel, timestamp, client-safe status, and follow-up rule.
Incident note
This output should preserve owner, source, channel, timestamp, client-safe status, and follow-up rule.
Report digest
This output should preserve owner, source, channel, timestamp, client-safe status, and follow-up rule.
Booked outcome
This output should preserve owner, source, channel, timestamp, client-safe status, and follow-up rule.