Honestly I cannot find a way to achieve this without having columns that will be equal to null in most of the cases. Also, I need to tell who is sending the message (because our customer service department can send messages to registered/guest users). My problem is: guest users won't have a record in the users table, so I cannot just have a user_id field on the messages tables. ![]() The tables will contain a column created_at. This means I will need to store all first name, last name, email and mobile phone for them (creating redundant data in the case of registered users, because I already have that data for them) But, when we add guest users, the user_id is useless, because they are not registered (so no user id). Everything is fine when there are only registered users and customer service members: I just need to relate each message to a user_id as sender or receiver. I started the design but I'm completely stuck at the moment. Timely web messaging is relevant throughout the customer lifecycle, whether to welcome a newcomer with an onboarding experience or alert a loyal user to a limited-time offer. This means that they can reply to messages but also can "start" the conversation (example: A message asking to confirm/update details). ![]() The customer service department can contact any user (registered or not) at any time.The customer service department needs to able to reply to any message.The messages can come from 1) a contact form available in the Contact page of the website where are asked fist name, last name, email, mobile phone, subject and message and 2) emails sent by users (then the system will receive the emails via webhook and store them properly). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |