ResolveAI Handover Document

1. Introduction

2. Legal and Compliance

• ResolveAI is using Termly.io for privacy policy, terms of service and cookie policy
• ResolveAI app is approved in Google Cloud for Google Calendar sensitive permissions
• read calendars and manage events

3. Marketing

• ResolveAI is using SendGrid for email notifications.
• Backend has a workflow setup for sending welcome email additionally every new user if automatically added to contacts in SendGrid
• Marketing assets are stored in Figma
• Additional marketing assets that were ever used in blog are saved in google drive under ResolveAI marketing assets

4. Payments and Subscriptions

• ResolveAI is using Stripe to handle payments and subscriptions
• Stripe webhooks are already setup for handling subscription creation/updates and cancellations
• Each event is supplied with Slack notification
• Each client can manage their own subscription in Manage subscription section in admin dashboard

5. Blog and content

• ResolveAI blog consists of 2 parts.
• Notion blog database
• Super.so website of that blog

1. Collect lust of updates that were pushed
2. Use ChatGPT to refine short version of the update into a expanded more refined version
3. Create media assets for each section and blog banner
4. Copy generated content into a notion page, add banner and other media
5. Post blog
6. Ask ChatGPT to generate twitter thread based on created blog update
7. Post this on Twitter
8. Go to SendGrid and use Single Send with template to send blog update to email list of contacts

6. Sales and demos

• ResolveAI leads are mostly inbound, they start by talking with landing page chatbot and then reach out to contact@resolveai.co which I later use to schedule a demo. You can use calendly or cal.com to create calendar for meetings and self service bookings.
• During call I would first start with questions on what are they trying to achiever and why they are looking for an AI solution. This usually tells me few things:
• Is ResolveAI a right fit
• Should I continue with a demo or right of the bat tell them that it might not be a good fit
• We are partially solving their problem and might need a few changes/features to be a match
• eg. Custom configuration chatbot was created because client asked to a completely free chatGPT for their website
• After that I proceed with a demo where a quickly explain the chatbot creation workflow and show them chatbot form, how to create documents and what integrations we support
• If client is convinced I always suggest creating an account and using free trial to better understand the product.

6. Customer interactions

1. Users reach out via chatbot on our landing page or inside admin dashboard
1. They can request for live agent to help
2. Their conversations will be sent out to us and we can follow up
2. If chatbot doesn’t know how to answer certain questions it will reply to clients to send email to contact@resolveai.co
1. Email newsletter also leads to contact@resolveai.co

1. Manually cancel subscription
1. go to admin CRM cms.resolveai.co
2. Go to users, find user with email you want to cancel
3. scroll to user subscription, click on subscription
4. inside subscription toggle of is active and click save
2. Add user trial date
1. Similarly find user and it’s subscription from CRM
2. inside subscription indicate active until date, this will indicate when we should stop letting user to the platform until client subscribes, or we manually change that
3. Impersonation Login as a client