Skip to content
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

develop implementation plan for tracking email sends to patients #8167

Open
mirrorstage opened this issue Oct 4, 2024 · 2 comments
Open

Comments

@mirrorstage
Copy link
Collaborator

Description

In Metabase, we currently track Text Message Sent and Text Message Status in their respective tables. We do not, however, track email sent in support of the patient results-available notification.

As a Call to Action (CTA), an email is an important moment in the user journey where the application has nearly completed its value exchange with the user in the overall test/result loop. We also pay to send these. For both reasons, it would be useful to have our own count of emails sent. TBD if "status" is equally useful, as I/@mirrorstage don't know enough about that table's operations or intended use.

Proposed solution

Start tracking email sends, storing the data in Metabase.

Additional context

I believe we also send "Welcome to SimpleReport" emails to admins at new organizations. This could be an interesting secondary use case but needs review.

@DanielSass
Copy link
Collaborator

At first glance, it looks like similar to our sms tooling - sendgrid has webhooks that could theoretically give use similar updates: https://www.twilio.com/docs/sendgrid/for-developers/tracking-events/event

Should try to verify if there are billing implications for this feature.

@mirrorstage
Copy link
Collaborator Author

mirrorstage commented Oct 7, 2024

@DanielSass came here to ask "why do you suppose we track SMS in the first place but not SendGrid?" and discovered the answer is: Alicia wanted it -- #1266 -- in April 2021. but then maybe had forgotten about it by July when SendGrid was applied to this use case -- #2027

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants