Currently the small business I work for has a support email address setup as the following: support#mybusinessdomain.com (changed domain for anonymity).
We need to make it so that multiple people can manage this email address, and the way we have it currently setup is causing some issues.
The way it is currently setup is that all emails are forwarded to myself and three other coworkers that manage the support emails that come in, and each of us have setup the following rule:
"Do this: Skip Inbox, Apply label "BusinessDomain Support", Never send it to Spam"
So we get all of the emails sent to that label, they skip our inbox and we delegate/respond from there. This was causing issues with my coworkers responding to the same emails and has our customers replying to our actual work email addresses rather than the support email.
We setup a process/procedure to make sure my coworkers and I were only answering things once, and to solve the problem of customers responding to the wrong email address we added the support#mybusinessdomain.com email as a "Send mail as" for each of us. However, now we are all sending emails from the same email address and it is a bit confusing as to who responded AND all sent emails are showing in our sent folder.
So, what is the best way to setup this support email so that multiple people can manage it and so that customers that reply to emails sent are always sent to support#mybusinessdomain.com?
Any help would be great!!
You need to use a group as a collaborative inbox.
Collaborative inboxes are especially useful for technical support or
customer service teams. For example, you could create a group with the
address support#your-domain.com. You could then add your
support staff as group members, and allow people outside your
organization to send messages to the group. Your support staff would
then receive customer messages and take any of the following actions:
Assign responsibility for topics to group members
Mark topics as resolved
Edit tags associated with topics
Filter topics according to tag, resolution status, or assignee
Related
Context
The company I work for is just now adopting a ticketing system for their IT help requests. Previously, all of our users have access to a Slack account and would start a message thread in an itsupport labeled channel to begin a "ticket". Now we would like users to send an email to an itsupport#company.com inbox which will then in turn create a ticket within the ticketing system. Since we know our end-users are going to still send Slack messages in the channel, I have been tasked with making an integration between Slack and a Google inbox designated for our help desk requests. The ticketing system is managed by an IT company we are contracted with, thus I am not the one integrating the Google Inbox and the ticketing system. I am only tasked with the integration between Slack and the mailing inbox.
Not sure if this context is needed, but I am currently using Node.js to capture the requests sent from Slack and then using Nodemailer to send the emails into the itsupport#company inbox.
Problem
The problem I have ran into (I found some questions related earlier but am having a hard time finding them now) is figuring out how to send an email on behalf on any user within our Google Workspace. For example, if Joe Schmo sends a message in the correct Slack channel, I would like to be able to send an email to the itsupport#company.com inbox as joe.schmo#company.com rather than my personal Google workspace account or through a generalized IT user account. How would I achieve this goal? I could change the "From" name however it would be preferred if I could send the email from any email address in our workspace.
My client need to send 500 or 1000 e-mails to a list of registered members that subscribe to mailing list, can I marked as spammer and have problems with my shared ip blacklisted on spam lists or spammer in gmail, yahoo, outlook?
What the best way to send these e-mails from my server without risks of being marked as spam or get my ip black listed? Or I recommend them to not do that in any way?
No
You can send an email to 1000 different users. A lot of companies send millions of emails per month !
It first depends on your users
Users can mark the email as spam if you send it without their mutual consent or send 1000 mails to each, obviously !
But in your question you explain that your users have given their consent because they are subscribed to your mailing list, so thats good.
Secondly it depends on your mail content
It depends mainly on your mail content.
There are a plenty of different reasons that your content can be marked as spam.
some word in subject
the ratio text/image of your content (too much images can be consider as spam by mail client)
There are a lot of words which can marked your mail as spam by the mail client.
a non exhaustive words list : https://blog.hubspot.com/blog/tabid/6307/bid/30684/the-ultimate-list-of-email-spam-trigger-words.aspx
In a lot of cases, emailing services can be very useful
You can use service like MailChimp or SendGrid to send huge amount of emails. They have free tier plan to try their service.
e.g with SendGrid
Send up to 40,000 emails for the first 30 days and 100 emails per day free forever
with MailChimp
Forever Free
Up to 2,000 subscribers and 12,000 emails per month
Moreover they have a nicely done dashboard with a lot of information about your sent emails (spam report, devices, clicked mails, opened mails etc..)
Last recommendation
You can use a service different for your marketing mails and your transactional emails. So marketing emails don't impact the reputation of your transactional emails (they are more important than marketing mails)
I would use a third party API (SendGrid, MailChimp etc.) to send out those emails. Using a 3rd party API sends the emails directly to your audience's inbox and not to their junk or spam box.
However, if you are sending mail which is spam and people are marking those emails as spam, your reputation with that mailing service will go down.
There are many "bulk email" service providers out there. You would want to google and research your options as each one of them have their own emailing price plans.
I have signed up with Google Apps, I am using a third party SMTP Server to send the emails from the web app, Emails are reaching inbox for all the email clients (yahoo, gmail, hotmail...)
But Emails sent to my domain (mydomain.com) are reaching SPAM, This is happening only for my domain Which is google apps account domain. The solution to the problem is the sender must be in the contacts of the receiver. So its a overhead involved in adding the sender in the contacts before receiving the mail. This is not automated.
NOTE: Mails sent from <xyz#mydomain.com> to <abc#mydomain.com> are reaching SPAM. It means, Its happening only when the sender and receiver belongs to same domain.
ASSUMPTION: ALL the emails will be sent from mydomain.com .
So, I want to write a script using google apps script So that when a mail arrives from mydomain.com (having FROM address belongs to mydomain.com), The script must execute and add the senders emails address in the contacts. So it will avoid the spam rate.
I am very new to google apps script, Please help me doing this, Or if any better solution is there please feel free to post.
Vinay,
It sounds like you may have an incorrectly configured SPF record. Please see this article:
https://support.google.com/a/bin/answer.py?hl=en&answer=33786&topic=2759192&ctx=topic
Email that has a mydomain.com sender address, needs to come from a mail server listed in your SPF record or risk being sent to spam.
By chance, has Contact Sharing been enabled for your apps domain? I'm just offering this as an hunch that might help rather than a specific solution to your problem.
If this doesn't help, its a straightforward but non-trivial problem to add all your domain accounts to each others contacts list (and keeping it synced over time), but you'll be leaning heavily on a version of the Contacts API rather than plain Apps Script because the Contacts service only operates on the contacts of the user executing your script.
I am using PHPmailer to send emails (newsletters) one by one to around 1000 contacts. The problem is that my web host provider blacklists my account and insists that I use a mailing list (containing all contacts) instead of sending out emails one by one.
AFAIK the problem with mailing lists is that the emails sent is the same for everyone, which prevents you from personalizing each message. Aside from not being able to include personal info such as the contact's name and product preferences, you also cannot include a contact's unique id, which you use for unsubscribing and for tracking responses to links/offers/ads.
So my question is, what is the industry standard/accepted way/pattern of sending bulk emails? Is it by sending out individually, or by using mailing list? If it's the latter, can you customize the email for each person in the mailing list?
Up to this point, I can only run PHPmailer from my web host provider and chose not to use third-party services such as MailChimp.
Thanks
I'm working on a web-based application, and looking to integrate each user's e-mail (gmail, yahoo, etc.) into it. I'd like to do an automatic sync (side detail: selective to specific e-mail addresses) of inbox and sent messages, i.e. any messages sent through the application will appear in the user's e-mail, and vice versa; any messages received in the application will appear in the e-mail, and vice versa.
My question: I realize this will probably involve IMAP. Is there a way to go about this without storing the user's e-mail passwords? I'm open to any language, infrastructure, etc.
If there's really no way around storing the passwords, would MD5 be sufficient? Any other thoughts would be greatly appreciated.
you would need to find an OAuth-based API for accessing the email provider. this would allow the user to authenticate themself, provide you with an access token for later use.
I believe you can do this with Gmail, Yahoo (see links)
A situation where this might arise is a private messaging system on a forum. A user might want PMs forwarded to their main email so that they don't have to remember to check the inbox on your site as well as their main email. Then when users reply to those messages, you want the reply to go as a PM to another forum user.
Forwarding PMs as emails is trivial. In order to allow replies, you need to have the email server on your site parse out some information in the email that indicates which user it should be forwarded to as a PM.
If you really want to allow a user to access their entire GMail inbox from within the interface on your site, rather than just messages that went through your site anyway, then you are facing a much larger task.