Delphi / Anon - Onboarding Documentation

Delphi / Anon - Onboarding Documentation

Introductions

From Delphi

  • Dara Ladjevardian, CEO
  • Samuel Spelsberg, Co-Founder
  • Spencer Schoeben, Engineering
  • Matin Amiri, Design

From Anon

  • Daniel Mason, CEO
  • Kai Aichholz, CTO

Background and Context

  • Delphi and Anon are partnering to built messaging interoperability for Delphi agents into the next version of Delphi.
    • ⚙️ Technically, this enables the audience of Delphi’s creators to engage with Delphi directly via the most popular messaging apps (Instagram, Facebook, Twitter, and LinkedIn).
    • 📈 Practically, this enables Delphi to dramatically grow its DAUs/MAUs by tapping into the existing audiences built by its creator partners.
    • ♟️ Strategically, this enables Delphi to become the only creator-focused digital twin platform supporting messaging interoperability.

Product and requirements

Product demos

  • We thought it might be helpful to have Delphi show a product demo to walk through the creator onboarding experience.

Requirements gathering

Business requirements

  • What are the objectives Delphi hopes to achieve with these integrations?
  • Based on initial data, what types of interactions have you seen users having with Delphi’s clones? Does it depend on the type of account? Or the source of traffic?

Product and design requirements

  • Can we get live access (or mockups) of the creator onboarding experience that we can use as we’re envisioning how our product integrates?
    • Any planned changes to this experience beyond adding Anon?
  • For the Chrome extension required for authentication, should this still be an Anon-branded extension? Or a white-labeled Delphi extension?
  • Who should be the point person on the design team to work with day-to-day?

Beta/rollout requirements

  • What size of user cohorts do we want to onboard in the early days of partnership?
    • What criteria is being used to select beta participants (e.g. “friendliness” to Delphi? opt-in? starting with smaller creators? Or larger ones?)
⚙️
We should cover the roadmap (👇) before making decisions here. This will also help us plan for volume estimates and metrics tracking at different integration phases.

Engineering requirements

  • Can you describe your tech stack being used to build Delphi?
  • What specific API endpoints or notifications will Delphi need from Anon?
  • Who should be the point person from engineering to work with day-to-day?
  • Can you talk through how Delphi plans to store message history?
    • Does there need to be any persistence? That Anon needs to support?

Communication requirements

  • How should we communicate on a day-to-day basis (e.g. shared Slack channel)?

  • How often should we do team checkins (weekly, bi-weekly, etc.)?

Anon Product Roadmap Proposal

Overview of Roadmap

⚙️
The following proposal is based on our latest estimates for availability of integrations using Anon. We should discuss if this aligns with Delphi’s current roadmap and can re-prioritize accordingly.
Phase 1
Phase 2
Phase 3
Phase 4+
Est. Launch Date
October 2nd
October 26th
November 13th
TBD
Objective
Get in-market quickly with valuable integrations.
Get in-market with all supported integrations.
Added functionality for all supported integrations.
To be mutually decided based on phases 1-3.
Instagram
Yes (limited)
Yes (limited)
Yes
Yes
Facebook
Yes (limited)
Yes (limited)
Yes
Yes
Twitter
No
Yes
Yes
Yes
LinkedIn
No
Yes
Yes
Yes
Other Services
No
No
No
TBA
Beta Cohort Size
To discuss
To discuss
To discuss
To discuss

Phase 1 — First to market with key integrations

Summary

  • This phase would be a launch to a limited cohort of users for just Instagram and Facebook.
  • This enables us to get to market quickly with immediately-valuable and reliable integrations that have a few limitations initially, which will be removed in future phases.

Proposed Launch Date

  • Available for integration: September 25th
  • Available to launch to users: October 2nd

Platforms supported

  • Instagram (limited)
  • Facebook (limited)

Creator and User Experience

  • For creators, this is a relatively seamless OAuth flow to provide access.
  • For users, interactions with Delphi will be directly available in Instagram and FB messenger.

Limitations

  • Only supports creator and/or business accounts (simple upgrade).
  • Creator accounts must have <500k users to participate (for now).
  • Responses must be sent in <24 hours.
  • In certain jurisdictions (CA, Germany), local regulations dictate that agents must disclose the automated nature of the experience.
⚙️
Based on our research, something like 40-60% of influencer/major IG accounts are creator and/or business accounts.

Phase 2 — Complete offering of messaging services

Summary

  • We launch full-featured integrations with LinkedIn and Twitter as a follow-up to the existing integrations with Instagram and Facebook.

Proposed Launch Date

  • Available for integration: Week of October 16th
  • Available to launch to users: Week of October 23rd

Platforms supported

  • Instagram (limited)
  • Facebook (limited)
  • LinkedIn (full)
  • Twitter (full)

Creator and User Experience

  • For creators, the new integrations (LinkedIn and Twitter) will involve a different onboarding flow that includes the Anon Chrome Extension.
  • For users, the experience will be exactly the same, except extended to LinkedIn and Twitter.

Limitations:

  • Same set of limitations for Instagram and Facebook as previously mentioned.
  • From a technical standpoint, no limitations for Twitter and LinkedIn; however, we will initially want to throttle responses and scale up based on performance benchmarks.

Phase 3 — Robustness for all integrated services

Summary

  • We launch full-featured integrations with LinkedIn and Twitter as a follow-up to the existing integrations with Instagram and Facebook.

Proposed Launch Date

  • Available for integration: Week of November 6th
  • Available to launch to users: Week of November 13th

Platforms supported

  • Instagram (full)
  • Facebook (full)
  • LinkedIn (full)
  • Twitter (full)

Creator and User Experience

  • For creators, the full suite of integrations will be available with robust capabilities. There will still be two paths to integration depending on account type, number of followers, etc.; however, Anon can handle that complexity as part of the onboarding flow.
  • For users, the experience will be indecipherable to users based on integration type.

Limitations:

  • Technically, Anon should have no limitations for any user type. We will continue to monitor performance metrics to adjust throttling / messaging timing accordingly.

Next Steps

Any questions coming out of the meeting today?
Anon to schedule recurring checkins.
Anon to create communication channel for day-to-day checkins.
Anon to share developer docs with anyone who doesn’t have them already.
…Add other next steps determined during the meeting.