-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Establish metrics to measure the AR filing and goal to transition people to the new platform #134
Comments
Help Desk gets 600-700 calls a month for the AR Reminder. Need to find out what these calls are about today. |
Increase the number of people that need to onboard and transition from the legacy application to the new Business Registry platform. (includes account creation and affiliating a business.) |
@nsmenon8890 - fyi |
Hi @sarahelz19, Let me know if you have any questions. Thanks |
Hi @sarahelz19 , Could you please assist me with the data or connect me with the team that can support me with it? Thank you! |
@vikas-gov I have established call codes with our support centers and will be asking for weekly data during stabilization. If you would like to schedule a meeting with me to discuss, my calendar is up to date and you can let me know if you require anything further |
After reviewing with @sarahelz19 , the plan is to engage and begin collecting data from the support center by the end of September 2024 |
I inquired about the engagement expected to begin in late September, and the feedback received is that we will obtain the data for the wrap codes in a consumable format directly from Maximus/call centers. |
Objective: transition corporations from the legacy to BR to reduce calls and to make it easier for people to login and use the system.
.# of corps to transition / accounts setup - starting with approximately 172K unique accounts that will need to be setup.
.#of AR's filed in the new BizReg - review activity report
.#of people invited to file in the new BR but requested an access code to file in COLIN - need to look at activity report to review invited but did not file. Can also look at hotjar to see who started and dropped off - then look at why.
.# of people who are requesting access codes today - this number should drop over time - and will demonstrate time savings as staff manually process these today. Anecdotally, business has 20 calls/day. (wrap code submitted)
.#of calls related to AR filing (new wrap code submitted)
.# of calls related to officers (new wrap code submitted)
AR Reminder:
advised people to setup bcsc in advance. For UX - sent to 6 and advised them to do this...see how many people actually did. Data will help inform other comms on wording (e.g., stronger wording, formatting, etc.)
in the app, can we count the # of times people click the basic or premium links?
stretch goal
The text was updated successfully, but these errors were encountered: