Resolve / FAQ

Resolve FAQ

Is it right for us

Can Resolve cut through alert noise and get our incidents resolved?

Yes. Your team works from one ranked incident, not a flood of alerts. Resolve folds alerts, tickets, logs and traces into one incident, removes duplicates and routes it to the right owner with context. Where your policy allows, it runs approved runbook steps and resolves the incident. Then it drafts the postmortem.

Is Resolve for teams that spend more time sorting alerts than fixing problems?

Yes. Instead of sorting noise, your people get one ranked incident to work from. Resolve is built for teams that run IT service, operations and engineering work.

Can Resolve triage software defects and bug reports, not just IT incidents?

Yes. Resolve covers defect and incident triage. It takes in bug reports alongside tickets, alerts, logs and traces, removes repeat bugs and tickets, and routes each one to the right person, queue and runbook.

How it works

Will Resolve follow our own rules and escalation paths?

Yes. Your rules run first. Resolve applies your severity rules, service levels, escalation matrix and on-call schedule as policy, and reasoning handles only the new cases. Sensitive actions go through approval gates, decisions are logged in an audit trail, and it is set up around your own runbooks.

Can Resolve point our responders to a likely root cause?

Yes. Your responders start with a lead. Resolve builds root-cause hypotheses across telemetry, code changes, deploys, infrastructure and past incidents. Each ranked incident shows its suspected root cause and similar past incidents.

Can Resolve draft our customer replies and status-page updates?

Yes. Your updates are drafted for you. Resolve drafts customer replies, internal updates, status-page posts and incident communications in your voice.

Can our on-call engineers pick up a page with the context already there?

Yes. Resolve writes on-call hand-off briefs, so no one starts a page cold. It routes each incident to the right person, queue and runbook, with full context attached.

Your systems and data

Will Resolve work with the IT and engineering tools we already use?

Yes. Resolve works across the tools your team already uses: IT service management, observability and engineering. It takes in tickets, alerts, logs and customer messages through Conduit, Mantle's connectivity layer. We connect the specific tools you use during setup.

Can Resolve use our incident history to spot repeats?

Yes. Your history works for you. Repeat tickets, bugs and alerts are deduplicated against a knowledge graph that evolves over time. Root-cause hypotheses also draw on your past incidents.

Getting started

Can we try Resolve first on our noisiest queue?

Yes. Bring your noisiest queue and we'll scope a pilot from there. Use the form on our contact page, and our team will be in touch.

Can a pilot run on our own rules, not a generic setup?

Yes. Resolve is customized to your runbooks, severity rules and escalation matrix, and your rules run first. Bring your noisiest queue, and we'll scope the pilot from there. Use the form on our contact page, and our team will be in touch.

Pricing and support

Can we get a price for Resolve that fits our scope?

Yes. Pricing depends on scope. Use the contact form and our team will be in touch.

After go-live, will Resolve keep our runbooks and postmortems up to date?

Yes. Resolve updates your runbooks and search index after each incident and drafts the postmortem, with the timeline, contributing factors and action items. When the same cause repeats, it becomes a Problem record and Resolve flags a candidate code or infrastructure fix.

Bring your noisiest queue. We'll scope the pilot.

mantlenow.com/products/resolve   Outcomes, accelerated.