Story
Twilio
Daiichi SankyoDaiichi Sankyo Brings Customer Messaging onto Twilio
Daiichi Sankyo, a health care organization in Japan, uses Twilio Segment from Twilio to support product communications for product and growth teams.
Value results
| Category | Value result |
|---|---|
| Capability | Customer messaging can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for customer messaging |
| Capability | Product communications stays visible to adjacent teams through Twilio Segment |
Story
Inside Daiichi Sankyo, product communications used to depend on whoever still had the latest file. That pattern is common in health care groups working out of Japan. Product and growth teams needed a system that would still make sense after the original project team moved on.
Daiichi Sankyo uses Twilio Segment from Twilio as the working layer for customer messaging. Twilio provides customer engagement APIs for messaging, voice, email, and customer data, used to build communications into products. The practical change is simple: product communications has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What Daiichi Sankyo gets from Twilio is a durable place to run product communications and a way for product and growth teams to see the same customer messaging at the same time.
