Skip to content

docs: updates Agency cardholder enrollment documentation to include in-person enrollment#3634

Draft
indexing wants to merge 2 commits intomainfrom
indexing-patch-3
Draft

docs: updates Agency cardholder enrollment documentation to include in-person enrollment#3634
indexing wants to merge 2 commits intomainfrom
indexing-patch-3

Conversation

@indexing
Copy link
Copy Markdown
Member

…scription

@github-actions github-actions bot added the documentation [auto] Improvements or additions to documentation label Mar 29, 2026
@github-actions
Copy link
Copy Markdown

@github-actions
Copy link
Copy Markdown

Coverage report

This PR does not seem to contain any modification to coverable code.

@indexing indexing changed the title docs: revisions to agency card self-service enrollment diagram and de… docs: updates Agency cardholder enrollment documentation to include in-person enrollment Mar 29, 2026
Copy link
Copy Markdown
Member

@jgravois jgravois left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i know this PR is still Draft, so feel free to ignore my drive-by suggestion if its premature or irrelevant.

deactivate Benefits
Note over Benefits: Successfull enrollment
```
1. The transit rider visits the web application at benefits.calitp.org in a browser on their desktop computer.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mobile devices are a common form-factor for self-service too, correct?

Suggested change
1. The transit rider visits the web application at benefits.calitp.org in a browser on their desktop computer.
1. The transit rider visits the web application at benefits.calitp.org in a browser on their desktop computer or mobile phone.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jgravois I'm not necessarily pitching to keep this structure in the doc, but note this line at the top of the Alternative flows section:

Suppose the transit rider does not have a desktop computer. In this case, they open the web application at benefits.calitp.org in a mobile browser on their iOS or Android tablet or mobile device to complete enrollment using the basic flow."

The logic here is that the primary way a person uses our product is on a desktop computer. I'm verifying if that is still the case, but curious about your thoughts regardless.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but note this line at the top of the Alternative flows section:

i see that section in all the other enrollment pathway doc pages. whatever way seems most appropriate to mention mobile phones in the 'agency-cards' page works for me.

The logic here is that the primary way a person uses our product is on a desktop computer. I'm verifying if that is still the case

As long as telemetry is what dictates our primary form-factor and we prioritize accordingly, we're tacking in the right direction imo. ⛵

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just checked out stats for successful enrollments in 2026. 60% of riders used a mobile device, so I'm moving away from this structure as reflected in #3632 . Thanks for the callout!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation [auto] Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants