-
Notifications
You must be signed in to change notification settings - Fork 527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continue over email #151
Comments
+1, this combined with #165 is crucial as otherwise we have no way of getting back to users when we're not online |
I'm thinking for the first version of this, we just do something like:
(for now, we won't worry about tracking replies via email) @timgl @rosinghal @cheeseblubber let me know if any of that doesn't make sense! |
Yep I think that works for me! |
@reichert621 can we make |
hey @rosinghal! yes, I think we should be able to do that -- would it be ok if that was an account-level setting? (so that no matter which agent sent the message, the reply_to would always be e.g. |
@reichert621 yup makes sense. |
notes from #107
|
@rosinghal @timgl this is almost done -- just testing in staging first! hoping to deploy later today if things look good 👍 |
this should be working now! let me know if you have any questions, but basically it will work like this: #151 (comment) (the only update is that we wait 2 minutes to send the email, to give the customer some buffer to see it before receiving an email, and also to give the agent time to send multiple messages without having multiple emails go out) |
Unable to get this to work anymore.... self-hosting and with the env variable enabled I see the following: "23:51:37.416 info Skipped sending Gmail notification: nil" |
No description provided.
The text was updated successfully, but these errors were encountered: