When a customer leaves us, we like to set them (and us) up for future success. For example, when a customer leaves us I fill out a single form that automates many of the tasks noted below:
- We add a note and update their tags in our CRM. [AUTOMATED BY ZAPIER]
- We mail them a postcard via Handwrytten with a $5 Starbucks gift card (a little special “goodbye” from us). [AUTOMATED BY ZAPIER]
- We send them an email notifying them that the service has stopped. [AUTOMATED BY GRAVITY FORMS]
- We send our Slack channel a notification letting our internal team know that the customer has left us. [AUTOMATED BY GRAVITY FORMS]
- We update their Mailchimp lists/tags/etc. [COULD BE AUTOMATED BY GRAVITY FORMS]
- We update our “current customers and their services” Google spreadsheets. (one for admin and one for our support team) [COULD BE AUTOMATED BY GRAVITY FORMS]
- If requested, we’ll zip up their WordPress site and share with them. [COULD BE AUTOMATED BY GRAVITY FORMS]
- We delete recurring invoices in our payment system(s).
- We disconnect Jetpack, VaultPress, Gravity Forms, etc. if they are using our connections to those services.
- We delete their account from our hosting servers (if applicable).
In summary, 7 of 10 customer off-boarding steps could be automated, which is pretty cool. We only do 4 of those, because I’m a cheapskate and don’t want to pay the $20/mo for the fancy version of Zapier. 🙂
More posts from themightymo.com
With ACF 5, they shipped a relatively-unknown and awesome feature: The ability to have WordPress automatically-save your ACF fields to a json file in your theme folder every time you save your fields. This has the effect of: All you need to do is add a folder called, “acf-json”, to your theme folder, and it…
How to use $current_user or is_user_logged_in() with FacetWP and WordPress to show different content for logged-in users
I have a membership site where I need to display certain FacetWP results to people who are logged in and other FacetWP results to people who are logged out. Unfortunately, FacetWP forgets WordPress’ global $current_user variable the minute you use one of the facets. Same with WordPress’ is_user_logged_in() function – FacetWP forgets it all once…
I was recently horrified to discover that the “wp_options” table of this site was over 1.3 gigabytes in size. For those of you counting at home – that is ENORMOUS and unnecessary. I was confused, because the table seemed to balloon overnight (and likely did balloon overnight, it turns out!). The issue was caused by…