Case study

Contact form redesign

Redesigning ENGIE’s contact form to improve customer assistance and reduce customer support overload.

ENGIE customer support form redesign with guided contact categories.

Role & Tasks

UX Designer: UX Analytics, Heuristic Analysis, UX Design

Timeline & Status

3 months (2025) – Shipped

Team

1 Project Manager, 1 UX Designer, 1 UX Writer, 1 UI Designer, 2 Devs

Project summary

In 2025, ENGIE’s customer support team pinpointed a high reiteration rate of customer help requests generating costs and impacting customer satisfaction.

​

During my apprenticeship, I’ve worked with the Help & Support Team to identify pain points and co-create a new experience for the web contact form.

​

The contact form was shipped in mars 2025 and launched few months after my apprenticeship ends making difficult to see the impact on OKR.

PROBLEM SPACE

Customer support became highly expensive.

We noticed a high reiteration rate following customer requests

1 out of 5

help request are repeated with support.

1/3

customer not satisfied following help request.

Half of the customer requests relates to billing

Technical assistance

Other

Contracts (20%)

ENGIE’s engagement (7%)

Billing & invoicing (54%)

Intervention & troubleshooting

Offers & services (10%)

Consumption reading meter

As a result, we’re seeing...

An increase in customer dissatisfaction.

Higher processing costs per support request.

So what are we trying to solve?

OJBECTIVES

Key challenges & North Star Metrics

Streamline the user experience and improve clarity.

Reduce the rate of help requests reiteration.

Better route requests and optimize response times.

UX ANALYSIS

Whats going wrong as of now.

Contact form relies on an excessively long page

Page height and chunks of text significantly increase cognitive load through the task.

Poor usability lead to higher processing cost to complete the task.

Topics are not relevant anymore and create confusion for end customers.

Customer identifier became a barrier accessing the form

Frequently ignored, this step requires user to look after invoices to get their customer identifier.

Prone to errors, the input field lacks any formatting or validation to prevent mistakes.

Help topics are behind dropdown menus

Dropdown menu makes support themes poorly glanceable despite having poor usability.

Missing topics and imprecise labels can lead to confusion.

Generic and poorly personalized assistance

FAQ content lacks relevance to the selected theme.

Component looks like dropdown menu, leading to unclear affordances.

Legal disclaimer following cross-sell section

Cross-selling appears unexpectedly at the end of the form, potentially triggering user reactance.

Legal disclaimer is long requiring significant cognitive effort to read.

USER FLOW

Starting from what was already built.

Shifting from single page to progressive steps

As the single-page layout generate high cognitive load combining multiple tasks and steps. We’ve broken down the page into successive steps through progressive disclosure.

STEP 1 – CUSTOMER IDENTIFIER

Fixing the access to the form.

Customer identifier isn’t always required

As identifying the customer upfront is not necessary, we’ve introduced a login flow that encourages customers to sign-in while leveraging their customer data.

Designing a dedicated login step

To encourage users sign-in we’ve explored different way through quick prototyping to picture the user journey.

1. Information banner with a hyperlink

Non-blocking for users, who can choose whether or not to sign in.

Low engagement, and therefore likely to be ignored by users.

2. Modal dialog

May be perceived as intrusive and trigger user reactance.

Technically challenging and expensive to build.

3. Dedicated login page

Follows previous step and can be perceived as part of the user journey.

An existing page, requiring no additional development cost.

May be perceived as a constraining step.

How we made our decision...

Finding compromise between tech & user experience

Following team discussions, a dedicated login page was identified as a viable trade-off, limiting development cost while keeping sign-in optional for end users.

STEP 2 – HELP TOPICS

Improving themes legibility.

Help topics more are now glanceable

To replace dropdown menus, we designed cards to improve help topics glanceability while ensuring clarity and quick understand through microcopy and ENGIE’s brand illustrative icons.

STEP 3 – SELFCARE

Leveraging self-care for common issues.

Fixing the frequently asked questions area

Self-care uses different practices like FAQ or action-driven component to help users solve common issues on their own. The FAQ area is first step and the best opportunity to catch user attention on common problem.

Before

Affordance issue could lead to misunderstanding

FAQ collapsed by default raise interaction cost

After

New component fixes misleading affordance

Microcopy clearly adresses the problem

First FAQ open by default reducing interaction cost

Driving towards action through action-oriented component

The self-care step also introduces an action-oriented component redirecting to customer interface allowing them to solve issue by their own for common issues.

CUSTOMER EXPERIENCE

Reduced effort for logged-in customers.

Reducing form filling effort for customers

Once user logged-in, he only needs to review and confirm pre-filled information from fetched data.

Before

After

RESULTS

What we shipped.

LEARNINGS

What I learned from this project.

Data-informed design

Since this flow relies on a big amount of traffic, I took advantage of the data through qual. & quant. analysis to make grounded design decisions.

Embrassing trade-offs

Team discussions and trade-offs are part of the design process. They are often essential to meet both, technical and business requirements.

Cross-functional collaboration

I’ve worked with very different roles from business and technical background which helped to see the bigger picture of how an experience is shaped for millions of customers.

Next project

UX/UI DESIGN

Simplifying contract creation workflows

Designed core product experience allowing training centers to reduce time for contract creation processes.

Read case study

Thank you for your interest!

Back to projects

Case study

Contact form redesign

Redesigning ENGIE’s contact form to improve customer assistance and reduce customer support overload.

ENGIE customer support form redesign with guided contact categories.

Role & Tasks

UX Designer: UX Analytics, Heuristic Analysis, UX Design

Timeline & Status

3 months (2025) – Shipped

Team

1 Project Manager, 1 UX Designer, 1 UX Writer, 1 UI Designer, 2 Devs

Project summary

In 2025, ENGIE’s customer support team pinpointed a high reiteration rate of customer help requests generating costs and impacting customer satisfaction.

​

During my apprenticeship, I’ve worked with the Help & Support Team to identify pain points and co-create a new experience for the web contact form.

​

The contact form was shipped in mars 2025 and launched few months after my apprenticeship ends making difficult to see the impact on OKR.

PROBLEM SPACE

Customer support became highly expensive.

We noticed a high reiteration rate following customer requests

1 out of 5

help request are repeated with support.

1/3

customer not satisfied following help request.

Half of the customer requests relates to billing

Technical assistance

Other

Contracts (20%)

ENGIE’s engagement (7%)

Billing & invoicing (54%)

Intervention & troubleshooting

Offers & services (10%)

Consumption reading meter

As a result, we’re seeing...

An increase in customer dissatisfaction.

Higher processing costs per support request.

So what are we trying to solve?

OJBECTIVES

Key challenges & North Star Metrics

Streamline the user experience and improve clarity.

Reduce the rate of help requests reiteration.

Better route requests and optimize response times.

UX ANALYSIS

Whats going wrong as of now.

Contact form relies on an excessively long page

Page height and chunks of text significantly increase cognitive load through the task.

Poor usability lead to higher processing cost to complete the task.

Topics are not relevant anymore and create confusion for end customers.

Customer identifier became a barrier accessing the form

Frequently ignored, this step requires user to look after invoices to get their customer identifier.

Prone to errors, the input field lacks any formatting or validation to prevent mistakes.

Help topics are behind dropdown menus

Dropdown menu makes support themes poorly glanceable despite having poor usability.

Missing topics and imprecise labels can lead to confusion.

Generic and poorly personalized assistance

FAQ content lacks relevance to the selected theme.

Component looks like dropdown menu, leading to unclear affordances.

Legal disclaimer following cross-sell section

Cross-selling appears unexpectedly at the end of the form, potentially triggering user reactance.

Legal disclaimer is long requiring significant cognitive effort to read.

USER FLOW

Starting from what was already built.

Shifting from single page to progressive steps

As the single-page layout generate high cognitive load combining multiple tasks and steps. We’ve broken down the page into successive steps through progressive disclosure.

STEP 1 – CUSTOMER IDENTIFIER

Fixing the access to the form.

Customer identifier isn’t always required

As identifying the customer upfront is not necessary, we’ve introduced a login flow that encourages customers to sign-in while leveraging their customer data.

Designing a dedicated login step

To encourage users sign-in we’ve explored different way through quick prototyping to picture the user journey.

1. Information banner with a hyperlink

Non-blocking for users, who can choose whether or not to sign in.

Low engagement, and therefore likely to be ignored by users.

2. Modal dialog

May be perceived as intrusive and trigger user reactance.

Technically challenging and expensive to build.

3. Dedicated login page

Follows previous step and can be perceived as part of the user journey.

An existing page, requiring no additional development cost.

May be perceived as a constraining step.

How we made our decision...

Finding compromise between tech & user experience

Following team discussions, a dedicated login page was identified as a viable trade-off, limiting development cost while keeping sign-in optional for end users.

STEP 2 – HELP TOPICS

Improving themes legibility.

Help topics more are now glanceable

To replace dropdown menus, we designed cards to improve help topics glanceability while ensuring clarity and quick understand through microcopy and ENGIE’s brand illustrative icons.

STEP 3 – SELFCARE

Leveraging self-care for common issues.

Fixing the frequently asked questions area

Self-care uses different practices like FAQ or action-driven component to help users solve common issues on their own. The FAQ area is first step and the best opportunity to catch user attention on common problem.

Before

Affordance issue could lead to misunderstanding

FAQ collapsed by default raise interaction cost

After

New component fixes misleading affordance

Microcopy clearly adresses the problem

First FAQ open by default reducing interaction cost

Driving towards action through action-oriented component

The self-care step also introduces an action-oriented component redirecting to customer interface allowing them to solve issue by their own for common issues.

CUSTOMER EXPERIENCE

Reduced effort for logged-in customers.

Reducing form filling effort for customers

Once user logged-in, he only needs to review and confirm pre-filled information from fetched data.

Before

After

RESULTS

What we shipped.

LEARNINGS

What I learned from this project.

Data-informed design

Since this flow relies on a big amount of traffic, I took advantage of the data through qual. & quant. analysis to make grounded design decisions.

Embrassing trade-offs

Team discussions and trade-offs are part of the design process. They are often essential to meet both, technical and business requirements.

Cross-functional collaboration

I’ve worked with very different roles from business and technical background which helped to see the bigger picture of how an experience is shaped for millions of customers.

Next project

UX/UI DESIGN

Simplifying contract creation workflows

Designed core product experience allowing training centers to reduce time for contract creation processes.

Read case study

Thank you for your interest!

Back to projects

Case study

Contact form redesign

Redesigning ENGIE’s contact form to improve customer assistance and reduce customer support overload.

ENGIE customer support form redesign with guided contact categories.

Role & Tasks

UX Designer: UX Analytics, Heuristic Analysis, UX Design

Timeline & Status

3 months (2025) – Shipped

Team

1 Project Manager, 1 UX Designer, 1 UX Writer, 1 UI Designer, 2 Devs

Project summary

In 2025, ENGIE’s customer support team pinpointed a high reiteration rate of customer help requests generating costs and impacting customer satisfaction.

​

During my apprenticeship, I’ve worked with the Help & Support Team to identify pain points and co-create a new experience for the web contact form.

​

The contact form was shipped in mars 2025 and launched few months after my apprenticeship ends making difficult to see the impact on OKR.

PROBLEM SPACE

Customer support became highly expensive.

We noticed a high reiteration rate following customer requests

1 out of 5

help request are repeated with support.

1/3

customer not satisfied following help request.

Half of the customer requests relates to billing

Technical assistance

Other

Contracts (20%)

ENGIE’s engagement (7%)

Billing & invoicing (54%)

Intervention & troubleshooting

Offers & services (10%)

Consumption reading meter

As a result, we’re seeing...

An increase in customer dissatisfaction.

Higher processing costs per support request.

So what are we trying to solve?

OJBECTIVES

Key challenges & North Star Metrics

Streamline the user experience and improve clarity.

Reduce the rate of help requests reiteration.

Better route requests and optimize response times.

UX ANALYSIS

Whats going wrong as of now.

Contact form relies on an excessively long page

Page height and chunks of text significantly increase cognitive load through the task.

Poor usability lead to higher processing cost to complete the task.

Topics are not relevant anymore and create confusion for end customers.

Customer identifier became a barrier accessing the form

Frequently ignored, this step requires user to look after invoices to get their customer identifier.

Prone to errors, the input field lacks any formatting or validation to prevent mistakes.

Help topics are behind dropdown menus

Dropdown menu makes support themes poorly glanceable despite having poor usability.

Missing topics and imprecise labels can lead to confusion.

Generic and poorly personalized assistance

FAQ content lacks relevance to the selected theme.

Component looks like dropdown menu, leading to unclear affordances.

Legal disclaimer following cross-sell section

Cross-selling appears unexpectedly at the end of the form, potentially triggering user reactance.

Legal disclaimer is long requiring significant cognitive effort to read.

USER FLOW

Starting from what was already built.

Shifting from single page to progressive steps

As the single-page layout generate high cognitive load combining multiple tasks and steps. We’ve broken down the page into successive steps through progressive disclosure.

STEP 1 – CUSTOMER IDENTIFIER

Fixing the access to the form.

Customer identifier isn’t always required

As identifying the customer upfront is not necessary, we’ve introduced a login flow that encourages customers to sign-in while leveraging their customer data.

Designing a dedicated login step

To encourage users sign-in we’ve explored different way through quick prototyping to picture the user journey.

1. Information banner with a hyperlink

Non-blocking for users, who can choose whether or not to sign in.

Low engagement, and therefore likely to be ignored by users.

2. Modal dialog

May be perceived as intrusive and trigger user reactance.

Technically challenging and expensive to build.

3. Dedicated login page

Follows previous step and can be perceived as part of the user journey.

An existing page, requiring no additional development cost.

May be perceived as a constraining step.

How we made our decision...

Finding compromise between tech & user experience

Following team discussions, a dedicated login page was identified as a viable trade-off, limiting development cost while keeping sign-in optional for end users.

STEP 2 – HELP TOPICS

Improving themes legibility.

Help topics more are now glanceable

To replace dropdown menus, we designed cards to improve help topics glanceability while ensuring clarity and quick understand through microcopy and ENGIE’s brand illustrative icons.

STEP 3 – SELFCARE

Leveraging self-care for common issues.

Fixing the frequently asked questions area

Self-care uses different practices like FAQ or action-driven component to help users solve common issues on their own. The FAQ area is first step and the best opportunity to catch user attention on common problem.

Before

Affordance issue could lead to misunderstanding

FAQ collapsed by default raise interaction cost

After

New component fixes misleading affordance

Microcopy clearly adresses the problem

First FAQ open by default reducing interaction cost

Driving towards action through action-oriented component

The self-care step also introduces an action-oriented component redirecting to customer interface allowing them to solve issue by their own for common issues.

CUSTOMER EXPERIENCE

Reduced effort for logged-in customers.

Reducing form filling effort for customers

Once user logged-in, he only needs to review and confirm pre-filled information from fetched data.

Before

After

RESULTS

What we shipped.

LEARNINGS

What I learned from this project.

Data-informed design

Since this flow relies on a big amount of traffic, I took advantage of the data through qual. & quant. analysis to make grounded design decisions.

Embrassing trade-offs

I learned that decisions where mostly made through trade-offs where teams gather with their own requirements. In this case, trying to advocate for user is a must.

Cross-functional collaboration

I’ve worked with very different roles from business and technical background which helped to see the bigger picture of how an experience is shaped for millions of customers.

Next project

UX/UI DESIGN

Simplifying contract creation workflows

Designed core product experience allowing training centers to reduce time for contract creation processes.

Read case study

Thank you for your interest!

Back to projects