Discuss and review GEMS CRM setup, contact form functionality, and platform inquiry process.

Key Takeaways

- Contact form submissions now route to specific inboxes based on user selection, with a shared inbox (groups.google.com) for team collaboration
- Platform inquiry process to be replicated, maintaining existing workflow with minor adjustments
- Prototype development for GEMS is ongoing, with some recent progress and pending discussions

Topics

Contact Form and Email Routing

- Default submissions go to Chris if no option selected
- Specific routing:
- James platform → help@inisai
- Support for existing subscriptions → help@inisai
- Exchange → Chris directly
- James sensing → shared inbox
- Thank you email to be sent to end-user (currently set to Ian for testing)
- Shared inbox (groups.google.com) allows team collaboration:
- Assign conversations to team members
- Label, mark as complete, or take other actions
- Reply from personal or shared email address

Platform Inquiry Process

- Will replicate existing workflow with minor adjustments
- Process overview:
1. User fills initial form (internal/external selection)
2. Automated email sent with process details
3. User books slot with Kevin
4. Internal users can access free version or opt for higher tier
5. External users fill additional form
6. Customer receives confirmation email
7. Kevin (and Robyn) notified of form submissions

GEMS Prototype Update

- Some movement on prototype development
- Laura sent updated link based on recent conversations
- Chris to discuss and provide go-ahead after returning from time off

Next Steps

- Ian to set up automation for platform inquiry process
- Implement and test thank you email for end-users
- Consider improving email template design (potentially assign to Laura)
- Monitor and adjust shared inbox functionality as needed
- Follow up on GEMS prototype progress after Chris retur