← HRX / Use cases12345Talk to us →
CereBree · HRX

Questions no single system can answer.

Every case below needs customer, service and people context at once. That is where HRX starts, and where a ticket system, a CRM or an HR tool on its own stops.

Try Cognie →How Cognie decides →
Show cases for
01

Which customer relationships are at risk because of the current service disruption?

NeedsuCRMuSMSuRMS

The situation

A shared service fails at 9:10. Twelve customers depend on it, eight internal and four external. Two of the external ones have contractual commitments that expire within the next 90 minutes.

What you see today

The service desk sees an incident. Sales sees nothing until a customer calls. Nobody sees the two contracts.

What HRX connects

The service and its consumers (uSMS), the contracts and commitments behind them (uCRM), and the experts who are free right now (uRMS).

What Cognie recommends

Protect the two priority relationships first: assemble the three available experts, inform the two customer owners before the customers call, start the recovery workflow.

The outcome

Your account managers call the customer, not the other way round. The commitment holds, or the customer hears about it from you first.

Try this question with Cognie →
02

Who can resolve this critical incident?

NeedsuCRMuSMSuRMS

The situation

A critical incident needs a specific skill. Eight people in the organisation have it. Three are available now. One of them resolved a similar case last quarter.

What you see today

The desk assigns to the usual team and hopes. Skills live in HR, availability in calendars, history in closed tickets.

What HRX connects

The incident and its owner (uSMS), skills and availability (uRMS), and which customers are waiting for the fix (uCRM).

What Cognie recommends

Assign to the service owner, add the two further experts who are free, and tell the four customer owners who is working on it.

The outcome

The right three people start now instead of eight names in an e-mail. Resolution time drops, and the customers are informed while it happens.

Try this question with Cognie →
03

Which customers are most affected by recurring service issues?

NeedsuCRMuSMSuRMS

The situation

Five incidents in 90 days trace back to two services. Six customers were hit more than once. Two of them have renewals in the next two quarters.

What you see today

Each incident was closed on time. On its own, every one looks fine. The pattern is invisible, and so is the renewal risk.

What HRX connects

Incident history per service (uSMS), the customers and renewals behind it (uCRM), and the team absorbing the rework (uRMS).

What Cognie recommends

Open one problem review for both services, brief the owners of the two renewal accounts, and free capacity in the affected team.

The outcome

You fix the cause before the renewal conversation, and you walk into that conversation knowing what the customer experienced.

Try this question with Cognie →
04

What skills do we need for this new opportunity?

NeedsuCRMuSMSuRMS

The situation

A new opportunity needs five skills across three services. Three are covered by people with free capacity. Two exist only in people who are fully committed to existing customers.

What you see today

Sales says yes based on the org chart. Delivery finds out after signature that the two key people are booked until spring.

What HRX connects

The opportunity and its scope (uCRM), skills and real capacity including existing commitments (uRMS), and which of the three services is new to your catalogue (uSMS).

What Cognie recommends

Reserve the three available people, decide per gap between training and a partner, and agree a realistic start with the customer owner.

The outcome

You know the delivery risk before you sign, and the start date you promise is one you can keep.

Try this question with Cognie →
05

Who owns the affected service, and who depends on it?

NeedsuCRMuSMSuRMS

The situation

One service, owned by one team, delivered by two others. 140 employees use it every day. Four external customers depend on it through contracted services.

What you see today

The same service is a catalogue entry in one system, a team assignment in another and a contract line in a third. Nobody sees all three.

What HRX connects

Ownership and fulfilment (uSMS), the people who consume it (uRMS), and the external customers behind the contracts (uCRM).

What Cognie recommends

Confirm the owner as the single point of coordination, give both fulfilling teams the list of consumers and customers, and agree who informs the four external customers.

The outcome

When the service fails, everyone already knows who decides, who does the work and who feels it. That is the difference between a plan and a scramble.

Try this question with Cognie →

Your case is not here?

These five are the ones we hear most often. If your question connects customers, services and people in a different way, that is exactly what a 30-minute conversation is for.

Talk to us →Open the glossary