loftCRM
Step 1 of 4 · 1 min

What goes here

What you will learn

  • What belongs in operational issues
  • The issue board
  • Reporting an issue
  • Working an issue to resolution

What you need

  • A customer operations or network operations sign-in

An operational issue is an internal problem for one of your teams: a possible duplicate customer, a failed integration message, a broken process. Customer faults are cases; service disruptions are outages.

Step 2 of 4 · 2 min

The board

Services → Operational issues.

your-workspace/#/issues
Operational issues.
Operational issues.

Issues are grouped by state: New, Triage, Investigating, Awaiting fix, Verifying, Resolved. Each card shows the record it concerns, the assignee, the due date and the severity.

Filter by queue (service delivery, network operations, integration operations, finance operations, customer support, account management, data stewardship), by severity, or to issues assigned to you. Switch between Board and List.

Step 3 of 4 · 2 min

An issue

Open an issue from the board.

your-workspace/#/issues
An issue.
An issue.

The issue shows its state, severity, queue, assignee, when it was opened and when it is due, what it is waiting for, and the next action, for example Compare and choose surviving record. Linked records, tasks and history are kept on the issue, and Open audit trail lists every change.

Move the issue through its states as the work progresses, and record the resolution when it is fixed.

Step 4 of 4 · 2 min

Report an issue

Report issue:

your-workspace/#/issues
Report an operational issue.
Report an operational issue.
  1. Title.
  2. Kind and Source (an integration, a quality check, or manual).
  3. Severity.
  4. Linked customer case, if a customer is affected.

The form shows which team the issue goes to. Open and route issue creates it in that team's queue.