Back
eliott

eliott

@eliott

Building crisp.chat + jomo.so + some other stuff elio.tt
768
Joined January 2024

Hello Nicolas, yes 10% is a good conversion rate!!

Improvement idea: put a social proof, above the fold, for example your current AppStore average rating which is pretty good (4.8). See screenshot.

Webinars kinda work for us (#crisp) but only a very small fraction of users will attend.
And yes, users don't read anymore! We shoot a monthly email with new features (ie. changelog).

What we're trying right now is to show a popup (something users cannot ignore) in the app to highlight a specific feature (it may be a new feature or a feature that exists since a long time). Conditions to show this popup can be: user plan, whether they already used this feature or not, whether they use another complimentary feature, etc. The popup is very simple, a title, a small description, a screenshot of the feature (very important) and a CTA to navigate to that feature.

I think the summary of all this is that the best is to share the feature directly in your app / service, this is the best way to get noticed.

Thanks for sharing this! I also thought about in-app sharing, but to be honest I find these annoying. I never pay attention when I come across a popoup and skip all tours 😆 I prefer to figure out myself and read the docs/look for tutorials when I'm having issues.

And for the sitemap it's a custom script to make sure that XML is valid, URLs are valid, etc.

And on #crisp website, we have something that checks:
* dead links (very important)
* sitemap validity (even more important, if you build your own sitemap and don't notice it breaks, then you could loose months of SEO work)

What do you use for that?

And for the sitemap it's a custom script to make sure that XML is valid, URLs are valid, etc.

Auto-clear CDN Cloudflare cache after deployment (both in #crisp and #jomo ), to avoid cache issues

Gotcha. I'm not pessimistic but I always try to think about the worst. In your case the user could gain your trust via this first "gig" and then he could have bad intentions in the future. Like a social engineering scam. But this seems really far-fetched.

Interesting. This is a 50-50 problem in my opinion. Are you able to do a background check maybe?

I can try. GitHub looks real, but still anonymized

Gotcha. I'm not pessimistic but I always try to think about the worst. In your case the user could gain your trust via this first "gig" and then he could have bad intentions in the future. Like a social engineering scam. But this seems really far-fetched.

I have the exact same strategy for #jomo , BCC'ed myself for a few days for all new email templates.
I still BCC myself for emails related to some features like student discounts, this way I know the pipeline for that feature is working from A to Z. This serves more as a "health check" in that situation.

Home
Search
Messages
Notifications
More