Clarify downsides to email

Author: fungjj92

doc/arch/adr-0004-help-service.md

@@ -52,10 +52,11 @@ Decision
 
 For now, we will proceed with a basic email (e.g. support@temperate.io) for time savings to prefer building other features crucial for the MVP. Additionally, email is universally used and is therefore reliable to all potential Temperate.io clients. It presents hardly any implementation logistics. While the chat services were heavily considered, the Climate project's most limited resource is time right now. If there is time toward the end of the grant (April) to employ a chat service, we should revisit this to test out a chat help service.
 
-Depending on the anticipated product-use, agent #, and funding we will decide between Chat.io and Intercom based on price or functionality, as outlined above. Each product has a 14 day free trial that can be implemented in close collaboration with our ICLEI consultants to test that live chat is a viable workflow for them.
+As for email, we will link out to an email client. It is neither ideal UX nor customer service, but is trivial and still connects the user to the service. From the UX perspective, it would be preferable to write and send the email directly in the Temperate UI, but at that level of time and effort we should go for a chat service instead, whose code seems fairly light to implement.
 
-Additionally, we shouldn't build chat now because we don't want to pay fees for the help service prematurely, especially since we are not sure about the long term financials or usage of Temperate.io.
+Depending on the anticipated product-use, agent #, and funding we will decide between Chat.io and Intercom based on price or functionality, as outlined in the summary table. Each product has a 14 day free trial that can be implemented in close collaboration with our ICLEI consultants to test that live chat is a viable workflow for them.
 
+Additionally, we shouldn't build chat now because we don't want to pay fees for the help service prematurely, especially since we are not sure about the long term financials or usage of Temperate.io.
 
 Consequences
 ------------