I use Gravity forms automations for all sorts of things.
One way these automations save me all sorts of hours and headaches is for on-boarding & off-boarding customers.
Plus, these Gravity Forms automations help my biz to deliver a professional message from the outset of our working relationship. i.e. We appear more organized & trustworthy to the buyer.
Gravity Forms Automations for New Customer On-boarding
Whenever a new customer pays for one of our products for the first time, a number of things happen automatically:
- Their contact info is added to my CRM (Contactually) & Mailchimp.
- They are added to “Current [product name] Customers” group in Mailchimp.
- They start receiving my “[product name] On-Boarding Automation” email marketing automations series in Mailchimp.
- They receive an email receipt via Gravity Forms.
- In 3 days, my support team receives an email via Zapier telling them to schedule a kick-off call with the customer. (I use the Gravity Forms Zapier addon for this.)
- They are set up in Stripe with a recurring subscription (if applicable), and their website & contact info is added to their Stripe customer meta.
- Our support channel in Slack gets a notification letting our team know that we on-boarded a new customer.
- I get a DM in Slack letting me know that their payment went through successfully.
And then I take care of some things manually:
- I mail them a personalized “Thank You” card + a Starbucks gift card.
- I add their info to my master accounting Google Docs spreadsheet, which keeps track of all recurring revenue in my biz.
- I update their tags in my CRM to “Current [product name] Customer” and add a comment that says “[product name] purchased on [date]”.
- I add them to our monthly SEO Security Proven Process Gravity Form.
- I get full-page screengrabs from https://gtmetrix.com/, http://tools.pingdom.com/fpt/, and https://www.freeseoreport.com/ as benchmarks and submit them along with the form for future reference.
- I create the install on the server (if applicable).
- Add them to MightyLucy (our custom time-tracking software)
Gravity Forms Automations for Off-boarding Customers
How customers leave you is almost as important as how they found you.
So I try to help them feel appreciated every step of the way out the door. Who knows? Maybe I’ll work with them again in the future!
I have a Gravity Form that handles my customer off-boarding as well. This helps ensure a helpful & professional experience as they leave.
When I submit the Customer Off-Boarding Gravity Form, a number of things happen automatically:
- They get an email saying that their service was cancelled.
- They are added to the “Former [product name] Customers” and “Former Customers” groups in Mailchimp.
And I do a number of things manually:
- I update my master accounting Google Docs spreadsheet.
- I mail them a card thanking them for their business + a Starbucks gift card.
- I remove them from our monthly SEO Security Proven Process Gravity Form.
- I log into Stripe and cancel their recurring subscription.
- Is this helpful?
- What automations do you have in place for new customer on-boarding & off-boarding?
More posts from themightymo.com
GoDaddy owns ManageWP, and, strangely, they make it very difficult to add GoDaddy-managed WordPress sites to their ManageWP service. Thankfully, there’s a quick workaround: Visit https://yoursite.com/wp-admin/plugins.php?showWorker=1 — This will make the ManageWP “Worker” plugin visible. Copy the connection info from the ManageWP Worker plugin. Add the site per-normal on ManageWP. That’s it! I hope this…
I realized this morning that my TMM Maintenance Mode WordPress plugin had a bug that was causing the wp-login.php page to be inaccessible. The solution was to write a simple function that checks whether or not we’re currently on a login page, and then add a call to that function in my code. Here’s the…
Today I updated a WooCommerce site, and everything worked fine, except for the images on product pages – they were not displaying at all. After a lot of trial & error, I realized that WP Rocket was to blame. I’m not sure exactly what the issue was (though my hunch is that it had to…