Connected digital experience services

FyerX builds customer portals, employee applications and mobile journeys that connect to the systems where work happens. We scope what people need to accomplish, what information they may see and how the experience behaves when the system behind it is slow.

Discuss your technology project

When to bring in FyerX

One reason to review customer self-service is a delivery confirmation that reaches the portal after an earlier update. It raises questions about account reference, order identifier, delivery state and event timestamp, the groups affected and the action each can take when something goes wrong. Our starting point is the account order and delivery status. We trace it from customer request to servicing-system reference with the people who own those decisions. The result gives your digital product owner a specific first release, a testable operating outcome and a record of dependencies. For this example, the practical standard is simple: an agent can continue the journey using the reference visible to the customer.

Designing for interrupted journeys

Mobile customers may lose their connection between pressing submit and receiving confirmation. Keep a request reference and provide a way to recover its state. Confirm with operations which actions can be repeated and which require a lookup before retrying.

Customer and employee portals

Define tasks by audience and permission such as viewing an invoice, updating an address or tracking an internal request. Design the route into assisted support when the portal cannot complete the task. Bring the account order and delivery status and its history to the design discussion. Check account reference, order identifier, delivery state and event timestamp against the policy in effect at the time. For a case involving a delivery confirmation that reaches the portal after an earlier update, ask how the team currently recognises that the decision is complete. Agree whether a returning user can distinguish a saved draft from a submitted request.

Web application design

Build accessible forms, clear validation and status views around real user language. Cover interrupted sessions, saved drafts and returning customers who share responsibility for one account. Include customer, delegated account user and support agent in the walkthrough. Each sees a different part of the account order and delivery status. Ask them to trace customer request to servicing-system reference and establish where authority to view transactions for a different account actually sits. Differences between the documented responsibility and the person carrying out the action belong in the scope.

Mobile application delivery

Prioritise tasks performed away from a desk. Check small-screen inputs, intermittent connections and whether retrying a request could create a duplicate submission. Work through a customer losing the mobile connection immediately after submitting a change. Inspect the order confirmation, account context and last confirmed status before and after the event and ask the receiving team to explain the difference. A useful test includes shared accounts and interrupted mobile sessions, especially when the business consequence is an old delivery update displayed as a fresh commitment. Agree which information to keep and who will use it during a seasonal order peak.

Illustrative engagement

A customer starts online and finishes on the phone

  1. Starting point

    The contact centre cannot see the information already captured during an abandoned online application.

  2. Decision

    Agree which fields can follow a signed-in customer, how consent is recorded and when an agent should resume a saved application.

  3. Deliverable

    A cross-channel journey test that covers resume, expiry and a change of contact details.

Back-end system connection

Define which system owns balances, progress and identity. Return a useful status for delayed data and preserve a reference support can use to trace a reported problem. For operational handover, give the digital product owner a worked example from the assisted-contact reason report. Reconcile the result against successful self-service completions per eligible visit. Agree how to show the last confirmed status and provide a support reference when the evidence falls outside the accepted range.

Designing meaningful status updates

A customer who sees “processing” still needs to know whether to wait, supply information or contact someone. Identify the source events that distinguish those states, then agree wording that accurately reflects each one. If the delivery partner has acknowledged collection but has not supplied an arrival date, say precisely that. Test the status view with a user who did not submit the original request and may have less context. Include assisted support in the exercise so an agent sees the same reference and can continue the conversation without restarting the process.

Keep the customer's place when the channel changes

Someone starts a warranty claim on a phone, calls support to ask about proof of purchase and finishes the claim on a laptop. Three successful screens can still add up to one frustrating journey if the customer has to repeat the serial number each time. We map the information collected at each point, what the customer can edit and what the agent has permission to see. A shared case identifier and an explicit resume point give the design and integration teams a common target.

Next, our prototype tests the interruptions that happen outside a demonstration. A device loses connectivity halfway through an upload. A saved link is opened after sign-in expires. An agent corrects a customer detail while the browser still shows an earlier version. We agree on the message, recovery step and authoritative record in each case. The handover includes those states alongside the finished layouts, so developers and testers can reproduce the complete journey. Product owners can then assess completed claims and repeated contacts together when deciding what needs further investment.

What to bring to discovery

Bring an anonymised account order and delivery status, a recent assisted-contact reason report and an example of a delivery confirmation that reaches the portal after an earlier update. Where the inputs contain sensitive information, supply synthetic equivalents that preserve the decision sequence. Ask the digital product owner to identify who may approve view transactions for a different account. Record account reference, order identifier, delivery state and event timestamp with their meanings, including whether an empty value is permissible. Invite the people who use the order confirmation, account context and last confirmed status to describe the hardest discrepancy from the last cycle. The discovery log should capture the source evidence, responsible team and decision required.

Agreeing the first work package

Anchor the first work package in customer and employee portals and choose a deliverable such as a journey map linked to an API contract. Define the boundary from customer request to servicing-system reference so both teams know what a completed item looks like. For planning purposes, list shared accounts and interrupted mobile sessions separately from ordinary cases and record whether each is included in release one. Material scope changes include a second language or account audience, a different owner for account order and delivery status or a dependency that changes a seasonal order peak. Agree the cost and acceptance consequence of each before committing delivery capacity.

An acceptance exercise for your team

Give the operators an account user requesting the status of two separate deliveries. Ask the digital product owner to describe the expected business result before showing them the implementation. Introduce a delivery confirmation that reaches the portal after an earlier update and follow the chain from customer request to servicing-system reference. At each point, record the values of account reference, order identifier, delivery state and event timestamp that matter to the decision. The test succeeds when an agent can continue the journey using the reference visible to the customer. If evidence from the order confirmation, account context and last confirmed status disagrees, stop at the first observable difference and establish who can resolve it. Keep the starting data and explanation with the assisted-contact reason report. This example can be adapted to the rules and responsibilities of your organisation.

Deciding what belongs on mobile

Observe the task in the environment where it is performed. A field employee wearing gloves or switching between poor connections has different needs from a coordinator at a desk. Prioritise the minimum input that lets the next team proceed, then verify the deferred details can be completed later.

Planning around the operating calendar

Build the release around a seasonal order peak. For customer self-service, that means agreeing when the order confirmation, account context and last confirmed status are available, when the digital product owner can decide and what work would be interrupted by a late change. Select test material covering shared accounts and interrupted mobile sessions before reserving a business sign-off slot. Treat authority to view transactions for a different account as a release dependency. If a second language or account audience is introduced at the same time, check whether the original baseline for completed self-service journeys and assisted contacts still supports a meaningful comparison.

Exception ownership and recovery

One credible failure is an old delivery update displayed as a fresh commitment. The first diagnostic step is to inspect the order confirmation, account context and last confirmed status and identify the authoritative version of the account order and delivery status. Next, determine whether a returning user can distinguish a saved draft from a submitted request. For an incident involving a delivery status arriving late, an operator may need to show the last confirmed status and provide a support reference. Agree that authority with the digital product owner ahead of a seasonal order peak. Capture the resolution in a journey map linked to an API contract, including how customer, delegated account user and support agent can confirm recovery from their different perspectives. For repeat occurrences, compare the underlying fields rather than assuming every item in the exception queue has the same cause.

Handover and ongoing ownership

Put a journey map linked to an API contract in the hands of the staff who will own customer self-service. Include a completed example from customer request to servicing-system reference and a walkthrough for a delivery confirmation that reaches the portal after an earlier update. Someone outside the delivery team should be able to locate the order confirmation, account context and last confirmed status, identify authority to view transactions for a different account and act when the assisted-contact reason report shows a discrepancy. After the rehearsal, update ownership for account order and delivery status and document where to propose changes to account reference, order identifier, delivery state and event timestamp.

Planning your engagement

How to measure the outcome

Agree the measurement definition for completed self-service journeys and assisted contacts before changing customer self-service. Start with successful self-service completions per eligible visit, then review shared accounts and interrupted mobile sessions as a separate population if their expected treatment differs. A reliable baseline needs the reporting date, an owner for account order and delivery status and a consistent definition of completion from customer request to servicing-system reference. Test the assisted-contact reason report with a case involving a delivery confirmation that reaches the portal after an earlier update. If a second language or account audience alters the population later, preserve the original baseline alongside the revised one. This gives the digital product owner an explanation for a change in the number and a decision about which improvement to fund next.

Delivery and support responsibilities

For an advisory phase, ask FyerX to focus on the decision behind customer and employee portals. For an implementation, agree the behaviour of account order and delivery status through customer request to servicing-system reference and the evidence required from the order confirmation, account context and last confirmed status. For a team that already owns delivery, a bounded specialist assignment can focus on mobile application delivery. Keep authority to view transactions for a different account with its named business or technology owner unless explicitly delegated.

Sizing a cross-channel journey

Use one journey as the estimating unit, such as resuming an application after speaking to support. List the channels, saved state, authentication changes and data that can travel with the customer. Count exceptional paths separately, especially shared devices, expired sessions and changes made by an agent.

Frequently asked questions

Connected Experiences

What should the portal show when the source is unavailable?

A delivery date from yesterday may still be useful if the time is shown clearly. Decide how long a cached value remains safe to display and when the user should contact support. Offer a reference that lets an agent continue the same enquiry without asking for everything again.

How do we test the experience across accounts?

Use people with ordinary access, delegated authority and access to multiple accounts. Ask them to switch contexts and complete the same task. Check documents, saved drafts and notifications as well as what appears on the main screen. Test access removal after a role change.

What would you need to assess customer self-service?

Bring one account order and delivery status, an example from the assisted-contact reason report and the people responsible for the order confirmation, account context and last confirmed status. A useful discovery exercise follows customer request to servicing-system reference under both ordinary conditions and a delivery confirmation that reaches the portal after an earlier update. The resulting scope should identify the business decision, environment access and operating owner required for the first work package.

Can we begin with customer and employee portals?

Yes. Define the first deliverable in terms of an agent can continue the journey using the reference visible to the customer. Agree with the digital product owner how to test it using the order confirmation, account context and last confirmed status. The first phase can stop after the decision and evidence are delivered, or continue into web application design with scope and responsibilities already documented.

How does web application design fit into delivery?

It addresses the point in customer self-service where the team must understand account reference, order identifier, delivery state and event timestamp. Use a delivery confirmation that reaches the portal after an earlier update to establish how information, permissions and ownership cross that boundary. The resulting acceptance case should demonstrate a returning user can distinguish a saved draft from a submitted request and identify who takes over if the outcome is uncertain.

What happens to cases involving users with several accounts?

Use account order and delivery status as the starting reference and examine the order confirmation, account context and last confirmed status. The key question is whether a returning user can distinguish a saved draft from a submitted request. Agree a treatment with the digital product owner, preserve evidence for the assisted-contact reason report and make the authorised next action visible to the team. Include the case in later release checks, especially after a second language or account audience.

How should a late delivery update appear in the portal?

Retain the delivery event time and the time the update was received. Apply the agreed ordering rule before changing the visible status. A customer should be able to tell when information was last confirmed, particularly when a delayed update would otherwise move a completed order back into transit.

What should we expect at handover?

Expect the agreed delivery evidence and a journey map linked to an API contract. A useful sign-off is for the receiving team to trace customer request to servicing-system reference, read the relevant entry in the assisted-contact reason report and respond to a delivery confirmation that reaches the portal after an earlier update using the material supplied. Document ongoing responsibility for updates to account order and delivery status before closing the engagement.

How will our team decide whether to go ahead?

Ask whether an agent can continue the journey using the reference visible to the customer. Check the order confirmation, account context and last confirmed status with the digital product owner and verify that authority to view transactions for a different account is available during a seasonal order peak. If a critical dependency remains open, identify its effect on successful self-service completions per eligible visit and the owner who can accept, resolve or defer it.

Which measures are useful after release?

Use completed self-service journeys and assisted contacts alongside the assisted-contact reason report. For customer self-service, reconcile a sample against successful self-service completions per eligible visit and review the influence of shared accounts and interrupted mobile sessions. Confirm that a second language or account audience or a new reporting definition has not changed the population before crediting an improvement to the work.

Who can operate the outcome internally?

Agree responsibilities among the customer, delegated account user and support agent. Give the receiving operator an unfamiliar example involving a delivery status arriving late and ask them to investigate it through the order confirmation, account context and last confirmed status. Their ability to explain customer request to servicing-system reference and identify authority to view transactions for a different account is a practical test of the handover.

Can we launch one channel first?

Yes, if the customer can complete the journey and the receiving team understands the interim handoff. Test what customers see when they switch channels before the second release arrives.

Talk to FyerX about Connected Experiences

Contact Technology