manage-trust-communications — Claude Code command
manage-trust-communications generates communication scenarios for rate changes, service incidents, or regulatory updates: audience-specific messaging, FAQ packs, approval workflows, and trust monitoring with escalation triggers.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/manage-trust-communications.mdWhat manage-trust-communications does
This command helps financial institutions prepare coordinated messaging during critical events. You specify the scenario (rate increase, service outage, policy change), target audience (retail, SMB, enterprise, investors, partners), and distribution channels (email, in-app, push, support, field, PR). The command builds a messaging architecture that satisfies legal disclosures and risk requirements.
The workflow chains context gathering, message drafting with disclosures and calls-to-action, approval routing through legal and risk teams, distribution planning across channels with sequencing and owners, and sentiment tracking with escalation triggers. Output includes a communications brief with messaging and disclosures, support FAQ and escalation scripts, and a trust KPI tracker with sentiment metrics and follow-up tasks.
Internally, the command invokes specialist agents (messaging author, compliance validator) and skills for regulatory formatting and monitoring setup. Set an SLA (24h, 48h, 72h, or custom) and severity level (info, warning, critical) to adjust pace and emphasis.
What it helps with
- draft coordinated messaging for a financial incident or policy change
- assemble FAQ and support scripts with escalation guidance
- route messages through legal and executive approval
- distribute communication across channels by audience and sequence
- track sentiment and trigger follow-up actions on trust decline
Example prompts for the agent
- /financial-services:manage-trust-communications --scenario "Fee increase" --audience retail --channels email,support --sla 24h
- /financial-services:manage-trust-communications --scenario "Scheduled maintenance window" --audience enterprise --channels in-app,email,field --severity warning
- /financial-services:manage-trust-communications --scenario "Privacy policy update" --audience investor,partner --channels email,PR --sla 72h --severity info
How to install manage-trust-communications
Manually: put the files in place
.claude/commands/manage-trust-communications.mdCall it with /manage-trust-communications. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/manage-trust-communications.mdCall it with /prompts:manage-trust-communications. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/manage-trust-communications.prompt.mdManually: put the files in place
.gemini/commands/manage-trust-communications.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about manage-trust-communications
How do I install manage-trust-communications in Claude Code?
Create the file .claude/commands/manage-trust-communications.md in your project root and add the command definition. Then invoke it with /financial-services:manage-trust-communications and the required parameters.
What does manage-trust-communications do?
It generates crisis communication workflows for financial institutions: audience-tailored messages, FAQ and support scripts, approval routing through legal and risk teams, channel distribution plans, and trust monitoring with sentiment tracking and escalation rules.
What parameters does the command accept?
Key parameters: scenario (event type: rate change, outage, compliance update), audience (retail, smb, enterprise, investor, partner), channels (email, in-app, push, support, field, PR), sla (24h, 48h, 72h, or custom), and severity (info, warning, critical).
Source text
manage-trust-communications.md · Apache-2.0
--- name: manage-trust-communications description: Produces messaging, FAQs, and escalation workflow for financial incident or policy change communications. usage: /financial-services:manage-trust-communications --scenario "Rate Increase" --audience retail --channels email,in-app,support --sla 48h --- # Command: manage-trust-communications ## Inputs - **scenario** – trigger description (rate change, outage, compliance update, incident). - **audience** – retail | smb | enterprise | investor | partner. - **channels** – email, in-app, push, support, field, PR (comma-separated). - **sla** – response timeframe (24h, 48h, 72h, custom). - **severity** – info | warning | critical. ## Workflow 1. **Context Gathering** – capture scenario details, impacted products, regulators, and stakeholders. 2. **Message Architecture** – craft headline, supporting details, disclosures, and CTAs per audience. 3. **Approval Workflow** – route to legal, risk, and exec sponsors with tasks/SLA tracking. 4. **Distribution Plan** – map channels, sequencing, assets, and owner handoffs. 5. **Monitoring & Follow-up** – define sentiment KPIs, escalation triggers, and post-mortem tasks. ## Outputs - Communications brief with messaging, disclosures, and channel plan. - FAQ + support script pack with escalation guidance. - Trust KPI tracker with sentiment metrics and follow-up actions. ## Agent/Skill Invocations - `trust-communications-lead` – authors messaging + coordinates distribution. - `trust-compliance-director` – validates disclosures + regulator requirements. - `regulator-briefing-playbook` skill – formats updates for legal/regulatory stakeholders. - `customer-trust-dashboard` skill – establishes monitoring + reporting structure. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents