You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The contact created for a phone number would normally provide additional information on who the number belongs to, why the contact was created etc. However, since Launch Chat allows messaging people without first creating a contact, there's nowhere to store additional information/context on the interaction with the phone number.
Solution
Add a new "note" option on a history entry
Acceptance criteria
In the recent activity section on the home screen that shows the two most recent activities and in the history screen accessible by clicking "View all" on the home screen, add a "Add note" button on all history entries.
When the button is clicked, show a dialog with an alphanumeric input field, allowing users to enter arbitrary note to themselves on the interaction with that phone number: Example "This is the restaurant (name)'s business WhatsApp number you contacted to see if they would deliver at (location)"
If a note already exists on a history entry, replace the "Add note" button with "Update note", i.e., there can only be at most one note on a history entry.
If the user enters blank text in the input field, or edits an existing note to have blank text, clear the note (reset it to empty/null, the default).
Show notes in the history entries on the home screen and history screen.
The text was updated successfully, but these errors were encountered:
Context
The contact created for a phone number would normally provide additional information on who the number belongs to, why the contact was created etc. However, since Launch Chat allows messaging people without first creating a contact, there's nowhere to store additional information/context on the interaction with the phone number.
Solution
Add a new "note" option on a history entry
Acceptance criteria
The text was updated successfully, but these errors were encountered: