bcgov / bcgov/entity

UX Review - ways to encourage people to onboard to new system and how their payment methods are changing

Open
#18,473 3 comments 0 reactions 1 assignee Claimed by @ethantspitt View on GitHub
BA Pay UX
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

Modernization is almost complete; Corporate Online and BC Assessment are the last partners to move over to the new system.
They represent a large volume of clients and a majority of them pay via BCOL Deposit Account.

In advance of Limited companies moving over from COLIN, we have two main goals:
1. Encourage clients to set up their account in the new system to avoid a rush at go-live.
2. Warn clients that BCOL deposit accounts are being removed as a payment option in the new system.

To date we have used emails and surveys to try to get clients to take action, but it is human nature to not move until it is absolutely necessary. This task is to capture ideas that can encourage clients to take action on account creation and payment method changes. The following 'levers' should be considered:

- [ ] Legacy BCOL landing page content changes
- [ ] Legacy BCOL payment statement changes
- [ ] COLIN filings - add warning/help text
- [ ] COLIN Annual Report reminder emails - add warning/help text
- [ ] Modernized system - add to 'What's New' section
- [ ] Modernized system - add to 'Notifications' section of header
- [ ] Modernized system - add feedback forms/surveys to Account info section
- [ ] Modernized system - add warnings in the Payment Method section
- [ ] Info sessions
- [ ] Public website updates
- [ ] others as they are discovered...

Ethan, please work with OCM and BAs on our team to review this from a holistic level. Please advise what you feel would be most effective in getting clients to change behaviors as early as possible.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.