Welcome to the "
Firefly Insurance Claims Status Portal Design Challenge". In this challenge, we are looking for your help to revamp the current claim status portal to allow Firefly customers to check their claim status, complete claim related tasks, schedule services, facilitate communication and set up their method of payment.
Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!
Round 1
Submit your initial designs for checkpoint review.
- Important: As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs.
- Please ask in the Forum for a MarvelApp prototype link.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have the correct flow! Use correct file numbering. (00, 01, 02, 03)
Round 2
Submit your final designs plus checkpoint feedback implemented.
- Important: As part of your final submission, you must update your submission to MarvelApp.
- Use the same MarvelApp prototype you received in the checkpoint.
- Make sure to include a URL/Link to your design within your "notes.txt", Important!
- Make sure all pages have the correct flow! Use correct file numbering. (00, 01, 02, 03
Background Overview
Constant communication happens between Firefly and Customers when filing a claim. Firefly wants to execute the entire flow online. Customers should learn processes, timelines and receive timely updates. Proper expectations of the process should be shared with customers. Customers should receive push notifications, things to consider, ability to get details such as getting an alternate car, status of a claim and the ability to close the claim. Both Firefly agents and Customers already use an existing portal. Agents find it easy to use, but customers face a lot of difficulty, due to lack of intuitiveness. Firefly’s objective is to improve the user experience of the customer using the application. Customers should be able to execute all of their insurance needs, review all actionable items, view claims lifecycle, chat with Agents, see claims progress at each stage, and provide feedback at each milestone. If the feedback at any stage ends up being negative, then there could be an option to involve agents. Collaboration could be text, email or DocuSign documents.
Challenge Goal
The goal of this challenge is to develop UI/UX for a responsive web application to simplify portal for customer use.
Design Consideration
- Simple, Clean, Professional, and Intuitive look and feel
- Simplicity to find any necessary information
- Needs to offer a great focus to the user
- Best Practice for Responsive Web-Based App (Desktop and Mobile)
- Easy to understand the flow from page to page
- Intuitive for the user; should never be left asking "what do I do next?"
- Easy viewing for pages that may be over overcrowded with information (eg. when hovering over an item will enlarge for easy viewing or similar)
Challenge Forum
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
Screen Requirements
For this challenge, we are looking for the below pages to be designed/considered in your concepts. The screen functionality details listed below are suggested functionality for consideration. Do not allow the suggestions below to impact the creativity of design. If there is a better way to accomplish the same goal, then feel free to take creative liberties.
01) Homepage
- Graphical Claim Status (i.e. Progress)
- Pending Action Inbox (Any activity a customer hasn’t completed yet). These could be required or optional.
- Display Basic Claims
- Claims LIst (Claim number is a hyperlink)
- How you are feeling - Allow them to capture their emotional state (i.e. sentiment) with a simple 3 state model (i.e. smile, no emotion, frown)
02) Claims Page
- Collaboration Area for Adjuster and Claimant (e.g. Facebook, Timeline/Slack)
- Display basic claim summary with drill down to the unit
- Closing the Claim
03) Details of Policy
- Policy ID
- Coverages:
- Loss of use - k4
- Collision
- Towing & Road Service
- Medical Coverage
- Uninsured / Underinsured Motorist Property Damage
- Uninsured / Underinsured Motorist Bodily Injury
- Glass Deductible Buyback
- Comprehensive
04) Document Upload
- Users can either upload files through the application or can send files via fax/email/mail
05) Contact Directory
- Contact Preference Management
- Text & Email preferences for the various contacts in the Contact Directory list
06) Services
- 1 Repair Exploration & Schedule
- List of COD (Cash On Delivery) shops and map view
- 2 Rental Exploration & Reservation
- List of rental shops and map view
- 3 Payment System Integrations (Setup payment method)
- Way to pay the customer (currently it is ACH - Automated Clearing House) and a list of payment options
07) Communications / Event / Action Log
- 1 User Tasks/Inbox – This is a set of procedures or actionable items the claimant must perform. It functions like any inbox/task list.
- 2 Collaboration – this is an area where Claimants and Firefly can interact in a persistent way. Think of “Slack” or a forum style interaction.
- 3 Communications/Event/Action Log – This is a historical record of the actions the user took to file a claim. Think of this as a timeline.
08) Notifications
- Show both a notification page and an example of a widget/popup/modal
09) Chat
- Chat will look like a general chat with the Agent
Workflow
- Step 1: Users to login and get authenticated
- Step 2: Have a placeholder to view claims
- Step 3: Need ability to use various services offered in claims
- Step 4: Collaboration
- Step 5: Need to see all communications at one place
- Step 6: Need place holder to upload documents/photos
Important:
- Keep things consistent. This means all graphics styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance
Marvel Prototype
- We need you to upload your screens to Marvel App.
- Please send your marvel app request to contato@luizrrodrigues.com.br (Challenge Copilot)
- You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comments link when you upload).
Branding Guidelines
Documentation
- Branding Guidelines Document
Target Devices
- Responsive Web-Based Application
- Desktop: minimum 1366px Width with Height adjusted accordingly
Target Audiences
- Firefly customers
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness put into solving the problem
- The overall design and user experience
- Cleanliness of screen design and user flow
- Ease of use
Submission & Source Files
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
- Submit JPG/PNG image files based on Challenge submission requirements stated above
- MarvelApp link for review and to provide feedback
Source Files
All source files of all graphics created in either Adobe Photoshop, Illustrator (Might need to convert it to PSD later), XD, or Sketch and saved as an editable layer
Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.