Skip to content

merchantprotocol/shadowmailer-support

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 

Repository files navigation

Shadow Mailer public support tickets, discussions and roadmap

Resource Link
Sales Homepage www.shadowmailer.com
Application Login app.shadowmailer.com
Documentation app.shadowmailer.com/docs
Support Portal github.com/merchantprotocol/shadowmailer-support/
Support Tickets github.com/merchantprotocol/shadowmailer-support/issues
Support Discussions github.com/merchantprotocol/shadowmailer-support/discussions

Support Tickets

You will find in this repository an "Issues" section where support tickets can be created for Bugs, Feature Requests and other reasons to engage the Community Manager and Development Team. Support tickets are designated for items that might be escalated to the software developers. If you're not sure what kind of problem you're dealing with, it's best to create a support ticket.

Discussions

If you do not have a bug or problem with the software, then it's best to post your needs into the discussions area. We are created categories for all things support.

Feedback Category Documentation
📣 Announcements
🗣️ Open Discussion Forum
🙏 Q&A

These discussions are where you can share suggestions for how the products should be improved and discuss those improvements with the community, including members of the ShadowMailer product team. Check out Making suggestions to learn how to provide feedback.

This repository works in conjunction with the ShadowMailer public roadmap, which is where you can learn about what features we're working on, what stage they're in, and when we expect to bring them to you. Discussion categories have been established for specific features listed above, as well as a general category for other topics. Additional categories may be added in the future. In the meantime, topics outside of the listed categories above, will be transferred into the general category. Please review the CODE OF CONDUCT before participating in discussions.

Making suggestions

We encourage you to open a discussion if you have suggestions for how we can improve our products. You don't need to have a solution to the problem you are facing to kick off a discussion.

Prior to making a new discussion, please take a look at previous discussions to see if someone else has already brought to our attention your suggestions. If you find a similar discussion, reply with additional details or upvote the discussion to signal your support rather than creating a new discussion.

From a suggestion to a shipped feature

Once you kick off a discussion, the ShadowMailer product team will evaluate the feedback but will not be able to respond to every submission. From there, we will work with you, and the entire community, to ensure we understand the current capabilities ShadowMailer doesn’t have and explore the space for potential solutions to your problem statement:

  • If the product team determines that we are going to prioritize a feature to solve the problem you've identified, we may open an issue and track its development in the public roadmap.
  • If the product team determines that we will not be working to solve the problem you have identified, we may comment on the discussion describing our reasoning so our decisions can remain transparent.

The ShadowMailer public roadmap

❇️ View the official ShadowMailer public product roadmap[^1]

Our product roadmap is where you can learn about what features we're working on, what stage they're in, and when we expect to bring them to you. Have any questions or comments about items on the roadmap? Share your feedback via ShadowMailer public feedback discussions.

This repository is for communicating ShadowMailers's roadmap. If you have feedback about this roadmap repository itself, such as how the issues are presented, let us know through general feedback in public feedback discussions.

Guide to the roadmap

Every item on the roadmap is an issue, with a label that indicates each of the following:

  • A release phase that describes the next expected phase of the roadmap item. See below for a guide to release phases.

  • A feature area that indicates the area of the product to which the item belongs. For a list of current product areas, see above.

  • A feature that indicates the feature or product to which the item belongs. For a list of current features, see below.

  • One or more product SKU labels that indicate which product SKUs we expect the feature to be available in. For a list of current product SKUs, see below.

  • Once a feature is delivered, the shipped label will be applied to the roadmap issue and the issue will be closed with a comment linking to the relevant changelog post.

Release phases

Release phases indicate the stages that the product or feature goes through, from early testing to general availability.

  • alpha: Primarily for testing and feedback
    Limited availability, requires pre-release agreement. Features still under heavy development, and subject to change. Not for production use, and no documentation, SLAs or support provided.

  • beta: Publicly available in full or limited capacity
    Features mostly complete and documented. Timeline and requirements for GA usually published. No SLAs or support provided.

  • ga: Generally available to all customers
    Ready for production use with associated SLA and technical support obligations. Approximately 1-2 quarters from Beta.

Some of our features may still be in the exploratory stages, and have no timeframe available. These are included in the roadmap only for early feedback. These are marked as follows:

  • in design:
    Feature in discovery phase. We have decided to build this feature, but are still figuring out how.

  • exploring:
    Feature under consideration. We are considering building this feature, and gathering feedback on it.

Roadmap stages

The roadmap is arranged on a project board to give a sense for how far out each item is on the horizon. Every product or feature is added to a particular project board column according to the quarter in which it is expected to ship next. Be sure to read the disclaimer below since the roadmap is subject to change, especially further out on the timeline. You'll also find an Exploratory column, which is used in conjunction with the in design and exploring release phase labels for when no timeframe is yet available.

ShadowMailer has major releases on a quarterly basis, and minor releases on a weekly basis. Once we know what version we are delivering a feature, we will update the issue to indicate that information.

Feature Areas

The following is a list of our current product areas:

  • devops: DevOps (Server, Databases)
  • sms: Text Messaging
  • email: Cold Email Remarketing (Sending Reputation, ESP, SMTP, Campaigns, etc)
  • leads: Lead Databases
  • prospecting: Chrome Extension
  • other: Other features

Disclaimer

Any statement in this repository that is not purely historical is considered a forward-looking statement. Forward-looking statements included in this repository are based on information available to ShadowMailer as of the date they are made, and ShadowMailer assumes no obligation to update any forward-looking statements. The forward-looking comments in the public feedback discussions do not represent a commitment, guarantee, obligation or promise to deliver any product or feature, or to deliver any product and feature by any particular date, and are intended to outline the general development plans. Customers should not rely on these public feedback discussions to make any purchasing decision.

About

No description, website, or topics provided.

Resources

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published