Twilio Customer Memory for Codex: Review Scoped Recall
Use Twilio Conversation Memory concepts to check profile-specific recall and distinguish individual context from a shared support policy.
中文Setup for Codex
Codex in a scratch project. Use fictional profile IDs and local result fixtures. Real Conversation Memory integration needs the relevant Twilio account access.
- Use the pinned Twilio checkout linked below. Copy `skills/twilio/twilio-customer-memory/` to the scratch project's `.agents/skills/twilio-customer-memory/` and load the skill from a fresh Codex session.
- Review the source's distinction between profile traits, observations, summaries and Recall. Define the profile scope of the local fixture.
Example task
Create a local table with demo IDs p1 and p2. Give p1 the synthetic trait 'prefers email' and p2 'prefers chat'. Simulate recall for p1 only and ask how to handle a separate shared business-hours fact.Expected result
The fixture returns only p1's email preference. It treats business hours as shared knowledge, and uses a neutral fallback when the requested profile has no matching entry.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Is a business-wide return policy part of Conversation Memory?
Conversation Memory provides context about an individual customer and their interactions. A generally applicable policy belongs in the organization's knowledge sources.