Mike Comer
My feedback
126 results found
-
1 voteMike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
-
1 vote
An error occurred while saving the comment Mike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
-
2 votes
An error occurred while saving the comment Mike Comer
commented
The more I use Stratus, the more I am impressed at its capability, and this is a perfect example of where it can really capture all of its potential value created: the details should include deliverability of the job and in so doing will do ~95% of what we were using Mailchimp to do. For those familiar with Mailchimp (MailerLite, Constant Contact, etc. I'm not familiar with but figure they work same way), you make a "campaign," which is really just a batch email to an "audience," which is really just a list of clients. In Stratus terms, a Mailchimp campaign is a Communications Job, likely started from the Communications Wizard. Audience for MC can be any number of things: Client Group, Filter, etc. This is nothing new. But so far as I can tell, there's no way in Stratus to check the performance of what amounts to a Mailchimp campaign wholistically. I.e. Mailchimp tells you not just about individual opens and click throughs of bulk emails in like the client record view but sums them in Mailchimps Campaign history to give deliverability stats for a campaign wholistically; the corollary in S+ would be if a Communications Job history could show what Communications Job was sent and some statistics like % opened and % clicked, the two main KPIs Mailchimp tracks for campaigns. I kept a close eye on my Mailchimp open rate and click through rate to see how my clients are responding and guage if I need to do some more sales impressions to get the results I'm looking for. Metrics like this would also enable A/B testing for emails. All of the components are there... just need the pieces pulled together in meaningful way to really be usable. And it's the quality and number of components that always surprises me with S+... and thereby what's possible given such excellent components to work with.
Mike Comer
supported this idea
·
-
Make it possible to load Session Images in Session Record as text lines rather than thumbs for speed
1 voteMike Comer
shared this idea
·
-
14 votes
An error occurred while saving the comment Mike Comer
commented
I think it'd be helpful to have this info show in Session Images view as well. Had instance just now where I had to manipulate a pending web order (client shopping cart on IBY) and would have benefitted from knowing what images had been by favorited by customer.
FYI Pixieset advertises this as a major functionaily on par with Selling and higher in the page: https://pixieset.com/features/.
Mike Comer
supported this idea
·
-
1 voteMike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
-
9 votes
An error occurred while saving the comment Mike Comer
commented
If you want to put this on roller skates, make it recursive: don't just make it so that you can merge "a" completed product but "all" digital products for a given project. So like trader cards for a baseball league... you can have Custom Variables or maybe a Web form as the data source, set the target in the template, and have it render out not just a player but all player composites.
Mike Comer
supported this idea
·
-
1 voteMike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
-
4 votes
An error occurred while saving the comment Mike Comer
commented
I would add that Session Status selector results should be alphabatized for ease of navigation (this is how it works in Filter Builder) if the change won't be made. That would at least make it easier to search for Lisa. Really, though, leaving the Statuses in the dropdown in the progress order of her defined workflow is better... they just need to be shown in isolation.
An error occurred while saving the comment Mike Comer
commented
My guess is that this is because you are using Session Statuses by Session Type and that you are using the same Session Status name among multiple Session Types. I think the answer here is for Lisa to search instead by Session Type first if this is the case and also for S+ to filter the Session Status results to only those valid for for the selected Session Type in the dropdown. As it stands, when you search by a Session Type that has specified Session Statuses specific to the Session Type, the results show *all* Session Statuses (and therefore duplicates if Session Statuses aren't named according to the suggested workaround of puttling like a "P" at front of status as in "P - Session Complete" for a Portrait Session Type) in the Session Status dropdown picker. If a Session Status isn't applicable to a Session Type, it simply should not be shown as an option regardless of a workaround because it's a false functionality: the software seems as though it will compound filter, but it's leaving the last leg of the relay to you.
Lisa: in case you get notified about comments to your suggestion, here is the relevant KB article with suggested naming convention for Session Statuses: https://secure.studioplussoftware.com/HelpConsole/spectra/default.aspx?pageid=session_statuses&SearchHighlight=Session%20Statuses&condition=exactphrase. Here's the relevant quote: "Description - Enter a short description for the session status. If you're creating statuses by type (see step 2 above), make sure to give each status a unique description. For example, use "P-Session Pending" for a portrait status and "W-Session Pending" for a wedding status. This will come in handy when sorting on the Sessions hub."
Mike Comer
supported this idea
·
-
7 votesMike Comer
supported this idea
·
-
1 voteMike Comer
shared this idea
·
-
1 voteMike Comer
shared this idea
·
I dug deeper to make sure I wasn't just ignorant of expected function. Also, there may be some configuration in my enterprise account throwing of Control Center. But it does seem that the Control Center used to allow Triggers to be run based on this KB section, which I think needs to be updated: https://secure.studioplussoftware.com/HelpConsole/Spectra/default.aspx?pageid=control_center&SearchHighlight=stratus%20drive%20image%20upload&condition=exactphrase#Process%20Triggers. It does note that for letters triggers, you still need to deal process them when set to auto because they require human intervention. IDK how letters when set to auto are now handled since Triggers aren't showing in Control Center when set to Auto (though, again, maybe that's just happening to me).