Obelisk
EN
Reports & journeys

See repeat contact and the paths between queues.

Connect distinct calls from the same identifiable number with observed queue passages, so repeated attempts and service journeys become easier to examine.

Repeated numbers and distinct calls
Observed queue passages
Links to Routing
In practice

Read the signal.
Choose the next step.

Separate a repeat contact from a long journey

A call that enters several queues remains one distinct call when the same call identifier links its entries. A number that calls again creates a repeat contact. Reading these together helps you separate movement within one conversation from the need to contact the service again.

Find a number with several contacts, inspect its first and last entry and open the individual call journeys. Use observed transitions to identify a pattern worth reviewing with the team.

Put it to work

01

Choose period and authorized queues to measure contact repetition using the normalized numbers in the call data.

02

Read chronological entries and passages between consecutive queues, with a direct path to the corresponding Routing call.

03

Export the complete filtered contact and journey results, or print the summaries and rows currently displayed.

What you can do

01

Measure observed contact patterns

Distinct calls, identifiable numbers, repeat contacts, repeat-contact rate and observed transitions.

02

Find returning numbers

Rank repeat contacts with first/last entry and open their individual call journeys.

03

Understand queue transitions

Inspect origins/destinations and transition frequency over the entire filtered result.

04

Open the individual journey

Drill through from chronological queue entries to Routing Log.

05

Export the broader view

Export all filtered repeat contacts or transitions; print current visible rows.

Read the detail with confidence

A number may represent several people, so this is not a unique-customer measure.

A number may represent several people, so this is not a unique-customer measure.

Only selected period and authorized queues are included

Only selected period and authorized queues are included; excluded queues are not bridged artificially.

Observed transition does not prove an explicit transfer.

Observed transition does not prove an explicit transfer.

Uses exact already-normalized stored numbers

Uses exact already-normalized stored numbers; does not analyze outbound callbacks.

Shares Routing permission and routing export/print controls.

Shares Routing permission and routing export/print controls.

Continue exploring

Request your demo

The complete Obelisk experience. Tell us about your contact center.

Loading the request form…