Short, practical walkthroughs of Composure in use, from setting up your MSP to closing the actions in a Root Cause Analysis. More are on the way, and the free trial includes a step-by-step setup guide.
The setup steps that matter on day one: your branding, your team and their roles, who does what, your customers and contacts, then a test before you go live.
Let your team sign in with their Microsoft accounts, map your Entra groups to Composure roles, and have new starters and leavers kept in step for you.
Connect your Halo PSA, choose which tickets matter, bring your customers and contacts across, and raise an incident straight from a Halo ticket.
Raise an incident, choose the customers and team, then review and send the first update Composure drafts for every contact.
Turn a technical note into the next round of updates, see who's due or overdue, and close the incident with the right final email.
Plan a maintenance window, approve its notices once, and let Composure send them on schedule, including what happens when the work moves.
The two ways to build the review your RCA is written from, which actions reach the customer, and why every action is tracked before the RCA goes.
The Standard PIR process: the engineer's half of the review, what happened, the cause and the evidence, checked before you submit.
On Enterprise's Advanced PIR process: run the review call, upload the Teams transcript, map it against the 20 questions, then draft and sign off the internal PIR.
Check the drafted Root Cause Analysis, work through the independent review, redraft with your answers and send it to the customer.
See every promise from your RCAs through: who's accountable, what's late, moving a date or dropping an action with a reason, and the closure note to the customer.
A tour of the customer portal: live incidents, the updates you've sent, the RCA, progress on your promises and planned maintenance, all under your brand.
Make Composure use your own job titles, so a CSM can be a Service Delivery Manager on every screen and in the customer sign-off, without changing what anyone can do.
Who can do what, a second pair of eyes before an RCA or maintenance notice goes out, and a record on every incident of what was sent and to whom.
Every time a customer hears from you, their Account Manager and CSM get a short briefing: what was said, to whom, and a suggested next step, so nobody's caught out when the phone rings.
Bring a customer's contacts in from Halo PSA or add them by hand, set their job titles and channels, including WhatsApp with their agreement, so every update reaches the right person in the right words.
Composure247