martin/doorman
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects Releases Wiki Activity

feature: automated onboarding register buzzer number #57

New Issue
Closed
opened 2025-10-03 19:25:10 -07:00 by martin · 5 comments
martin commented 2025-10-03 19:25:10 -07:00
Owner
Copy Link

the problem with onboarding right now is that usually the user will not know their buzzer code.

proposed flow to obtain it:

wizard flow

  1. user sets their buzzer to doorman confirm in form
  2. tell user to go physically to their buzzer
  3. once at buzzer physically they hit next to proceed
  4. this sets a flag on doorman api "onboarding" mode for 15 minutes
    -> in this state doorman will not reject unknown callers
    -> registered numbers will act normal
  5. when unknown number calls while in "onboarding" mode, twilio should answer and do the following:
    a. generate a random 4 digit code and store in ddb and store the caller number (need some TTL on this)
    b. speak intro instructions
    c. speak the random 4 digit code.
    d. repeat b, c again in case it was missed
  6. user types the audible code heard into doorman app
  7. buzzer number is retrieved! onboarding is now able to be completed
the problem with onboarding right now is that usually the user will not know their buzzer code. proposed flow to obtain it: wizard flow 1. user sets their buzzer to doorman confirm in form 2. tell user to go physically to their buzzer 3. once at buzzer physically they hit next to proceed 4. this sets a flag on doorman api "onboarding" mode for 15 minutes -> in this state doorman will not reject unknown callers -> registered numbers will act normal 5. when unknown number calls while in "onboarding" mode, twilio should answer and do the following: a. generate a random 4 digit code and store in ddb and store the caller number (need some TTL on this) b. speak intro instructions c. speak the random 4 digit code. d. repeat b, c again in case it was missed 6. user types the audible code heard into doorman app 7. buzzer number is retrieved! onboarding is now able to be completed
martin commented 2025-10-03 19:25:47 -07:00
Author
Owner
Copy Link

need one more ddb schema, for calls during onboarding mode.

need a schema for onboarding mode toggle (similar to lock / unlock state)

need one more ddb schema, for calls during onboarding mode. need a schema for onboarding mode toggle (similar to lock / unlock state)
martin commented 2025-10-04 12:21:27 -07:00
Author
Owner
Copy Link

implemented the onboarding mode as an internal only door

implemented the onboarding mode as an internal only door
martin commented 2025-10-04 12:21:50 -07:00
Author
Owner
Copy Link

it have a 15 mins timeout, and is hardcoded to not be unlocked after checking status

it have a 15 mins timeout, and is hardcoded to not be unlocked after checking status
martin commented 2025-10-04 13:50:18 -07:00
Author
Owner
Copy Link

API and client components are done. Now an onboardingflag door controls the handling of unknown callers as described above.

tested audio e2e on a real call, the numbers are correctly matching

API and client components are done. Now an onboardingflag door controls the handling of unknown callers as described above. tested audio e2e on a real call, the numbers are correctly matching
martin commented 2025-10-04 13:50:30 -07:00
Author
Owner
Copy Link

now just need to build into the UI form.

now just need to build into the UI form.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: martin/doorman#57
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?