Account reviews, renewal risk, meeting prep and the support queue. A success team reads the signals every week, stays quiet about healthy accounts, and hands your CSMs the move to make on the rest.
Free and open source. macOS, Windows and Ubuntu.
An example view. The teams are real, from the library. None of them is running yet.
Teams
Prep eats the week. Pulling usage, tickets and billing into one picture before every call.
The renewal surprise. The champion left in March. You found out at the renewal call in June.
The same questions, again. Half the queue is questions your docs already answer.
Hand this off first: renewal watch
“Every Monday at 8, review the accounts renewing in the next 90 days. Tell me only the ones that need me, why, and draft a check-in for each. Send nothing.”
Still yours: the call, and what you say on it. A first message to a customer stops for you, even on Full access.
The jobs to hand off first. Each one ends with a draft or a question for you.
From Murage’s team library. Look inside any team before you import it, then export it once and share it with your staff.
Customer Success Org
Review account health, identify customers needing attention, and prepare renewal priorities and support follow-ups.
Support Stack
Prepare ticket triage, onboarding guidance, retention follow-ups, and reusable responses in your brand voice.
Reply Desk
Sort the queue, prepare replies in your voice, and flag promising sales conversations for follow-up.
Review Engine
Prepare response drafts and review-request messages, then turn recurring feedback into a prioritized improvement digest.
Pricing Tribunal
Challenge discount pressure, churn risk, and perceived value, then get a revised offer with the trade-offs explained.
Email & Lifecycle Crew
Draft lifecycle email flows and a broadcast calendar grounded in audience needs and performance evidence.
Why it fits this work
The weekly renewal review names only the accounts that need a CSM, with the evidence and a drafted check-in, and says nothing about the rest.
Claude Code, Codex, Hermes and more, each bot on the engine that suits its job. Keep the one you use; Murage puts them on one team, you can switch any bot’s engine later, and the app is free.
Check-ins, replies and QBR outlines are drafted for you. Messaging a customer for the first time stops and asks, even on Full access.
Schedules run while Murage is open, and a run up to 12 hours late still happens. Always-on hosting is coming with Murage Cloud, which isn’t open yet.
Murage is free and open source. Your bots run on the AI plan you already pay for, and a busy team uses its allowance faster. Connected apps and voice use optional Flux Router credits or your own keys.
No. It reads the data you already have, from connected apps or exports, and does the prep and drafting on top.
CRMs, sheets and inboxes in the connected-apps catalog, with Flux Router credits or your own connected-apps key. Helpdesks only if they are in that catalog. Exports always work.
Yes, each person on their own computer. Build the team once, export it, and every CSM imports the same bots, skills and routines. Logins never travel with it. Each person can message their Chief from Slack, Discord or Telegram, and bots can post drafts to your team’s Slack channels through connected apps, with your approval and up to five labeled accounts per app. Shared, always-on workspaces come with Murage Cloud, which isn’t open yet.
Download the free app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
