The setting
supplies cloud software that lets developers and businesses build messaging, voice, and email into their applications. Its gathers these tools, along with identity checks and customer data.
Tonight's source deletion turns an uncertain memory boundary into a permanent loss decision.
A broad purge protects customer separation, while a narrow purge preserves context whose ownership is expensive to prove.
Who you’d be doing this for
“Our agent mentioned someone else's purchase this morning. I've switched memory off, and now every returning shopper starts from scratch.”
Dagny Korhonen · Application Engineer · a character in this brief
Maintains a retailer's conversational agent, which retrieves customer facts before answering questions about previous purchases.
What is at stake
Agents have quoted 11 memories belonging to unrelated customers, and source conversations expire tonight. You must weigh a broader permanent purge against retaining context whose ownership cannot all be checked in time.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer separation vs. preservation of useful context
- independent evidence vs. the deletion deadline
- broad containment vs. unaffected inference health
- aggregate confidence vs. concentrated exposure
Why Twilio
Conversation Memory turns raw conversations into searchable customer facts, so incorrect ownership becomes information served to another customer's agent.
Written with these in mind
Not your kind of problem? 41 more at Twilio, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Twilio. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Staff Machine Learning Engineer (opens in a new tab)
- Machine Learning Engineer 2 (opens in a new tab)
- You'll join the Conversation Memory team, which builds the memory layer behind Twilio's Conversational AI platform: the systems that extract what matters from millions of conversations, resolve it to the right customer, and retrieve it in milliseconds when an agent needs it.
- Diagnose production issues across the ingestion, extraction, and indexing path using logs, metrics, and traces.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about an irreversible change forced by a fixed date.
A customer will delete 60,000 interactions tonight, with consent unresolved for 3,200.
You must weigh permanent evidence loss against irreversible disclosure.
Retailer identifiers and derived features still sit past the retention window in several warehouse and serving copies.
You have to balance privacy risk against deleting records that orders and support still need.
A regional data boundary is committed, but a lot of evaluation records cannot be confidently placed by region or retention rule.
You design the migration datasets, lineage, and evidence that will hold up after cutover.
The same setting, from another role
Each is set around Twilio’s Twilio Customer Engagement Platform, written for a different role. They’re separate briefs, not the same scenario.
Sellers found conflicting buyer assumptions in eight of twelve Messaging deals marked ready for proposals.
You decide how a draft handles a country or volume figure when an Outreach email differs from the Salesforce record, and which differences go to the seller first.
Five software providers choose a supplier in eight weeks, but disagree on who should bill their customers.
You weigh partner incentives and customer ownership against the margin and support obligations each agreement creates.
A software partner’s $9 million Messaging renewal expires tomorrow amid disputed forecasts.
You must weigh retaining its full commitment against signing away the ability to recover rising carrier costs.