ProductWhatsApp

[twilio-jyoung]

Description

we need a whatsapp icon

Link to icon

https://www.streamlinehq.com/icons/legacy-streamline-regular/logos/messaging-video-meetings/messaging-whatsapp

Icon type

• UI icon
• Product icon

[TwilioPasteBot]

Disclaimer: This is a very experimental bot using OpenAI's GPT-4. The answers may not be correct, a human will review the answer and update it if necessary.

---

Sorry, I don't know how to help with that.

I did do a search though, and I managed to find these other Discussions that might be similar or related to your question. Give them a read to see if they answer your question. If they do, head back here and update this discussion and mark it as answered, pointing others to the related discussion:

• USSD icon (updated: 12/16/2022, similarity score: 87%)
• Support Center Icon (updated: 02/08/2024, similarity score: 87%)
• OTT Channels icon (updated: 03/15/2023, similarity score: 87%)

[krisantrobus]

Hi @twilio-jyoung,

Is this part of a Flex plugin? We've had similar requests in these discussions:

• WhatsApp Icon required #3944
• More Paste Icons #3544 (comment)

Our previous suggestions were to use our SVG to React plugin: https://paste.twilio.design/core/libraries#svg-to-react to create the asset and maintain it them separately.

[twilio-jyoung]

this is for badging on the twilio marketplace. whatsapp is a product we sell, and many product teams need to reference it (marketplace, flex, conversations, etc...)

https://www.twilio.com/en-us/messaging/channels/whatsapp

[krisantrobus]

For some more context for the team, this is on Twilio Console and is referring to the icons this card?:

We will discuss this internally and get back to you soon.

[twilio-jyoung]

exactly!

[krisantrobus]

Hey @twilio-jyoung, we still agree with our original answers that third party logos should be maintained by the product teams. Our reasons for this are companies might have color guidelines, for example, that we don't have design tokens for. Like, WhatsApp's brand assets use a specific "black" hex code.

Also teams will be dependent on us updating our libraries and publishing in order to reflect and third party changes instead of being able to act and release earlier.

We empower teams to create these logos in any way you see fit. If you want your code to be consistent with how we have built our icon components we suggest using svg-to-react as this is what we use to create the react components.

[twilio-jyoung]

Thanks for the response. There are definitely tradeoffs to be considered on both paths.

To play devil's advocate, we can absolutely just build the icon ourselves, but it seems like proper support from Paste would be beneficial to all Twilions to help enforce consistency and alignments with brand guidelines from our partners. Maintaining this in Paste does create a dependency, but not maintaining this in Paste could result in teams not understanding or correctly applying the guidelines and being out of compliance. Additionally, if the guidelines change, many teams would need to both become aware (which is a tall ask to ensure many product teams stay aligned on partner branding guidelines), and then make the necessary changes rather than just one team making the change, and everyone else consuming the update.

We'll build our own for now.