---
# System prepended metadata

title: Service Client Slack Workflow

---

# Service Client Slack Workflow

## Issue

We consistently get #bt-service-client-sdk inbounds with inaccurate SDK version and SDK type. This makes us waste time clarifying which SDK they're actually using, as well as determining which team is reponsible for triaging it.

A lot of inbounds misuse the "All/Other" options especially for braintree_web/native cross-over questions.

Another consideration is we need to add PPCP repos to this list. 

This proposal is basically to use a single, exhaustive list of all SDKs we offer, instead of a combination of two questions.

## Current Workflow

**Platform**
○ Android (native)
○ iOS (native)
○ Web (desktop and native)
○ All/Other

**SDK Type**
○ Braintree Core SDK
○ Drop-In
○ Both
○ Other

**SDK Version**
`Text Box`

☑ *I have confirmed the SDK platform & version, because I know it's the first thing the SDK team will ask.*

## Proposed Workflow

**SDK**
○ braintree_web
○ braintree-web-drop-in
○ braintree-ios
○ braintree-ios-drop-in
○ braintree_android
○ braintree-android-drop-in
○ popup-bridge-ios
○ popup-bridge-android
○ paypal/ios-sdk (PPCP)
○ paypal/android-sdk (PPCP)
○ braintree-ios-visa-checkout
~~○ braintree-android-visa-checkout
○ braintree-android-samsung-pay
○ braintree-android-google-payment~~

**SDK Version (must not be N/A; find versions in repo's CHANGELOG)**
`Text Box`
