For Meeting on 9/13/23
Agenda
- Update on Personal.ai
- Launch, timeline, pricing, etc.
- Requirements gathering questions
- Questions about product, ux, technical architecture, etc.
- Update on Anon
- Use cases and integration timeline.
Update on Personal.ai
We want to align with your timeline and product roadmap, so it’s helpful to hear the latest on everything at Personal.ai.
- How has the new pricing being received?
- Do you still see Anon features as pricing upsells? If so, to which audiences (businesses, consumers, prosumers, etc.)?
- What are the next phases and timeline for product rollouts?
- Also, do you have a beta or something? Would love to try out SMS, mobile, for instance, as soon as they are live and we can test the products.
Requirements gathering questions
Business requirements
- What types of interactions is Personal.ai seeing on the platform today?
- What are the most common use cases?
- Have a lot of users connected Google Drive or Zapier via the memory stack?
- In external chats, how many users use Autopilot vs. Copilot?
- How does the Gmail draft feature work? I don’t see that in my UI.
- How will Personal.ai evaluate whether integrations with Anon were successful?
- What metrics should we optimize for?
- Any other non-quantitative criteria?
Product, design, and ux requirements
- Where will Anon integrations be incorporated into Personal.ai?
- In the my data section?
- Do we want to co-design the look or messaging of this section?
- Are there any specific use cases that users are requesting?
Engineering requirements
- From our prior notes, we have:
- Tech stack:
- All data is stored locally
- Most of the app is built in React, including React Native on Mobile.
- API endpoints
- Messaging endpoint API at a high level
- From backend
- x-sdk-client-id → uuid, ID of SdkClient
- Authorization → string, API key of SdkClient
- From frontend*
- x-sdk-client-id → string
- Authorization → string, JWT of end-user
- Authentication (e.g. sign-in with your Instagram Creator or Business account)
- Browser Extension for Desktop
- iOS SDK for Mobile
- Message storage
- Will Personal.ai store each message as it arrives such that we don’t need to support persistent storage or querying of message history?
POST
https://api.anon.com/messenger/v1/message
Body
{
"conversationId": "uuid",
"text": "string", // e.g. output from `https://api.personal.ai/v1/message`
"platform": "string" // e.g. “instagram”
}
Headers
* Is this use case required? For instance, will calls to Anon’s Messenger API come directly from end-user devices, or will they originate from Personal AI’s servers?
Communication requirements
- ✅ We will continue using the Personal.ai Lounge for day-to-day communication.
- ✅ We can set up standing bi-weekly calls as a general check-in? Or weekly?
Anon Product Timeline and Sequencing
The following represents the progress we’ve made from an engineering and product planning perspective. We want to make sure this is aligned with how Personal.ai plans to roll out future products that include Anon.
Use Cases Based on Integration Availability
Use Case Phase #1 | Use Case Phase #2 | Use Case Phase #3 | |
Description | Users will be able to receive messages from Instagram and Facebook Messenger in Personal.ai and respond either on autopilot or via a draft written by Personal.ai and sent by the user. Limitations presented by Meta’s API apply in this phase (below*). | Users will have the same functionality as in Phase #1, but will gain full functionality to receive, respond to, and to send net new messages on LinkedIn and Twitter DMs. | Users will have the same functionality as in Phases #1 and #2, but will gain additional functionality for Instagram and Facebook messaging. This removes necessary limitations on the services, as well. |
Est. Launch Availability | October 2nd | October 26th | November 13th |
Est. Integration Start | September 25th | October 18th | November 6th |
Instagram Receive | Limited | Limited | Yes |
Instagram Respond (Auto) | Limited | Limited | Yes |
Instagram Respond (from Draft) | Limited | Limited | Yes |
Instagram New Send | No | No | Yes |
Instagram Mobile Auth | No | No | Yes |
Instagram Desktop Auth | Yes | Yes | Yes |
Facebook Receive | Limited | Limited | Yes |
Facebook Respond (Auto) | Limited | Limited | Yes |
Facebook Respond (from Draft) | Limited | Limited | Yes |
Facebook New Send | No | No | Yes |
LinkedIn Receive | No | Yes | Yes |
LinkedIn Respond (Auto) | No | Yes | Yes |
LinkedIn Respond (from Draft) | No | Yes | Yes |
LinkedIn New Send | No | Yes | Yes |
Twitter Receive | No | Yes | Yes |
Twitter Respond (Auto) | No | Yes | Yes |
LinkedIn Respond (from Draft) | No | Yes | Yes |
Twitter New Send | No | Yes | Yes |
Limitations on Meta API-integrated accounts* :
- Accounts be either creator or business accounts.
- This is a simple upgrade for any user, and most creators/businesses have already upgraded to these account types.
- Accounts must have <500k followers.
- The API only enables replies to existing threads, not initiation of new threads.
- Fully-automated replies must be within 24 hours whereas human in-the-loop replies must be within 7 days of receipt.
Initial Integrations and Proposed Availability Date
Service | Est. Launch Date | Est. Integration Start | Integration Type | Service Limitations |
Instagram (limited) | October 2nd | September 25th | API | See below* |
Facebook (limited) | October 2nd | September 25th | API | See below* |
LinkedIn (full) | October 26th | October 18th | Remote Auth | None |
Twitter (full) | October 26th | October 18th | Remote Auth | None |
Instagram (full) | November 13th | November 6th | Remote Auth | None |
Facebook (full) | November 13th | November 6th | Remote Auth | None |
TBA | TBA | TBA | Remote Auth | None |
TBA | TBA | TBA | Remote Auth | None |
Platform | Est. Launch Date | Est. Integration Start |
API Integration | October 2nd | September 25th |
Google Chrome SDK | October 26th | October 18th |
iOS SDK | mid-late November | mid-November |
Other SDKs (Android, other browsers, etc.) | TBA | TBA |