Skip to contentSkip to navigationSkip to topbar
Twilio Docs

Profile endpoints

(information)

Legal information

Conversation Memory, including the APIs, may use artificial intelligence or machine learning technologies and is subject to the terms of the Predictive and Generative AI/ML Features Addendum(link takes you to an external page). For more details on AI usage and data, see the AI Nutrition Facts.

Conversation Memory is not a HIPAA Eligible Service or PCI compliant and should not be enabled in workflows that are subject to HIPAA or PCI.

Conversation Memory is not intended for use with sensitive information about individuals. Twilio does not control what information comes from conversation channels and relies on you to ensure the data in customer profiles aligns with our acceptable use policy. Twilio does have limited guardrails in the form of a prompt exclusion that is designed to provide a minimal screening against inclusion of GDPR special category data(link takes you to an external page). As a reminder our profile technology uses generative artificial intelligence. Because generative artificial intelligence can make mistakes, review all outputs to ensure that the profile is correct.

Conversations products are only available in the new Twilio Console(link takes you to an external page). If your account hasn't been migrated, you'll be redirected to the legacy Console where these products won't appear.

Overview

overview page anchor

Profiles are the canonical customer records in a Memory Store. Each profile holds traits, organized into trait groups, that identify and describe a customer and let Twilio attach future conversation data to the right person. Every profile is scoped to a single Memory Store, so profile resolution, trait updates, and imports all happen within that store.

Conversation Memory passively hydrates profiles from your existing Twilio SMS channels via Conversation Orchestrator. Conversations formed by Conversation Orchestrator create profiles in the store, and automatically enrich profiles with observations and conversation summaries.

The Profiles API gives you two main ways to work with profile data. You can manage profiles one at a time with create, read, update, and delete endpoints, or you can load them at scale with bulk upserts and CSV imports. Which path you choose depends on whether you are handling live application traffic or backfilling data from an existing system.

Endpoints