Add new SentenceTransformer model.

1_Pooling/config.json

@@ -0,0 +1,10 @@
+{
+  "word_embedding_dimension": 384,
+  "pooling_mode_cls_token": false,
+  "pooling_mode_mean_tokens": true,
+  "pooling_mode_max_tokens": false,
+  "pooling_mode_mean_sqrt_len_tokens": false,
+  "pooling_mode_weightedmean_tokens": false,
+  "pooling_mode_lasttoken": false,
+  "include_prompt": true
+}

README.md

@@ -0,0 +1,636 @@
+---
+tags:
+- sentence-transformers
+- sentence-similarity
+- feature-extraction
+- generated_from_trainer
+- dataset_size:7057
+- loss:CosineSimilarityLoss
+base_model: sentence-transformers/all-MiniLM-L6-v2
+widget:
+- source_sentence: What steps are required if a customer initially has a Device Payment
+    Single Recurring Credit (SRC) on Day 1 and then makes a Full Retail Purchase SRC
+    on Day 2-14?
+  sentences:
+  - 'Context: PM ET on Mon - Fri or during the weekend to: [email protected]
+    Note: Directing a customer complaint to the appropriate email generates a case.
+    A representative contacts the customer within 24 hours, but not after 8 PM due
+    to industry regulations. The representative directing the customer complaint receives
+    an email confirming the following: Receipt Case creation Case assignment Standard
+    Complaints Leaders / Coordinators / Specialists must direct all other complaints
+    to [email protected]. Note: The turnaround time
+    for standard complaints is 48 hours or 2 business days.Account types: ME and SL
+    are included with the Employee Phone Program (EPP). CS ConcernTable: <table border="1"
+    cellpadding="5" cellspacing="0" width="100%"><tbody><tr><th style="text-align:
+    center;" valign="top" width="5%">Step</th><th style="text-align: left;" valign="top">Action</th></tr><tr><td
+    style="text-align: center;" valign="top" width="5%">1</td><td style="text-align:
+    left;" valign="top"><p>Assess the post based on the customer inquiry or comment:</p><ul><li>Take
+    the conversation offline.<br/></li><li>Have the customer send a Direct Message
+    (DM) or Private Message (PM) and continue the conversation for account specific
+    feedback.<br/></li></ul></td></tr><tr><td style="text-align: center;" valign="top"
+    width="5%">2</td><td style="text-align: left;" valign="top"><p>Attempt authentication
+    with the customer to capture the MDN to confirm the customer has a specific account
+    type listed above or if access is restricted in ACSS.</p><ul><li>If the customer
+    does not meet the account types listed above or access is not restricted in ACSS,
+    resolve the customer''s concern BAU.<br/></li><li>If the customer meets the account
+    types listed above or access is restricted, confirm all basic troubleshooting
+    steps are complete.<br/><ul><li>Proceed to Step 3.<br/></li></ul></li></ul></td></tr><tr><td
+    style="text-align: center;" valign="top" width="5%">3</td><td style="text-align:
+    left;" valign="top"><p>Advise the customer to call BGCO at 800-922-0204 and r<span
+    style="background-color: transparent;font-family: nhg-text-roman , Arial , sans-serif;">un
+    the </span><span style="background-color: transparent;">VZW CS CM</span><span
+    style="background-color: transparent;font-family: nhg-text-roman , Arial , sans-serif;">
+    </span><span style="background-color: transparent;">Engaged</span><span style="background-color:
+    transparent;font-family: nhg-text-roman , Arial , sans-serif;"> macro.</span></p><p>Sample
+    verbiage: "Thank you for providing your verification information. I see that you
+    have a business account with us. To receive further assistance, call 800-922-0204
+    to speak with a representative immediately."<br/></p></td></tr></tbody></table>'
+  - 'Details of the Mobile Telecommunications Sourcing Act (MTSA): MTSA: Is a federal
+    law that applies to all wireless providers throughout the US. Requires all taxes
+    from the sale of wireless telecommunications service to be sourced to the customer''s
+    Place of Primary Use (PPU). The PPU: Is the street address representative of where
+    the customer''s use of the mobile telecommunications service occurs. Must be either
+    the customer''s residential street address, or the primary business street address.
+    Applies to taxes on roaming charges. Taxes on roaming charges are based on the
+    customer''s PPU address, rather than the market where the call originated. The
+    only exception is if the call is placed from an international location through
+    a carrier not served in the US. These calls originating internationally are taxed
+    based on the location that originates the call. Affects state and local taxes
+    only and does not impact any of the federal taxes that are currently reflected
+    on the customer''s bill.'
+  - 'Context: in various outcomes when customers make their next purchase. Example:
+    Customer is currently in a device payment and does not have promotion or equipment
+    protection. If the customer loses the device and needs a replacement, the customer
+    may get a replacement by using a Full Retail Purchase. The customer is not required
+    to buyout the original device payment loan. The customer continues to pay on the
+    original loan but does not get any promotion associated with the Full Retail Promotion
+    device. Review below to determine the outcome for various upgrades:Review the
+    use cases for recurring Bill Incentive Credit (BIC) promotions:Table: <table border="1"
+    cellpadding="5" cellspacing="0" width="100%"><tbody><tr><th style="text-align:
+    left;" valign="top" width="25%">Day 1</th><th style="text-align: left;" valign="top"
+    width="25%">Day 2 - 14</th><th style="text-align: left;" valign="top" width="50%">Required
+    Steps</th></tr><tr><td style="text-align: left;" valign="top" width="25%">Device
+    Payment Single Recurring Credit (SRC)</td><td style="text-align: left;" valign="top"
+    width="25%">Full Retail Purchase SRC</td><td style="text-align: left;" valign="top"
+    width="50%"><p>Complete the following steps:</p><ol><li>Return the device.</li><li>Disqualify
+    the loan.</li><li>Purchase full retail.</li></ol></td></tr><tr><td style="text-align:
+    left;" valign="top" width="25%">Full Retail Purchase SRC</td><td style="text-align:
+    left;" valign="top" width="25%">Device Payment SRC</td><td style="text-align:
+    left;" valign="top" width="50%"><p>Complete the following steps:</p><ol><li>Return
+    device.</li><li>Accept new loan terms.</li></ol></td></tr></tbody></table>'
+- source_sentence: What is the default selection for non-Account Level Pricing (ALP)
+    multi-line plan changes?
+  sentences:
+  - 'The default for non-Account Level Pricing (ALP) multi-line plan changes is based
+    on the first number selected. Select the primary number first for non-ALP Family
+    SharePlans. Non-Family SharePlan to a New Family SharePlan Note: Single accounts
+    may have multiple family share sets, as long as each set meets Family SharePlan
+    requirements. Process all Family SharePlan transactions in the Multi-Line Change
+    screen. POS users start in the InfoDesk screen for the logic to work properly.
+    All lines must have the same effective date in a multi-line order or be processed
+    separately. The system allows backdating to a lower access amount when the target
+    plan is secondary. Pre-Order/Back-Order Portal Orders If a Family SharePlan customer
+    wants to place a pre-order/back-order, prior to placing the order:'
+  - 'Context: who activate or upgrade to a new Smartphone on a Small Business Plan.
+    Upgrade eligible. $5 line access discount for customers who activate or upgrade
+    to a new Smartphone on a Small Business Plan. Upgrade eligible. Upgrade eligible.
+    Offer Options Code Code Description Discount Final Cost Contract Consumer Business
+    Employees N/AAccess Line $5N/A1 Yr N/AAccess Line $5N/A2 Yr Offer Options Code
+    Code Description Discount Final Cost Contract Consumer Business Employees N/AAccess
+    Line $5N/A1 Yr N/AAccess Line $5N/A2 Yr Offer Options Offer Options Code Code
+    Description Discount Final Cost Contract Consumer Business Employees N/AAccess
+    Line $5N/A1 Yr N/AAccess Line $5N/A2 YrTable: <table class="details-table"> <caption></caption>
+    <colgroup> <col class="code"/> <col class="code-description"/> <col class="discount"/>
+    <col class="final-cost"/> <col class="contract"/> <col class="consumer"/> <col
+    class="business"/> <col class="employees"/> </colgroup> <thead> <tr class="row-other">
+    <th class="code">Code</th> <th class="code-description">Code Description</th>
+    <th class="discount">Discount</th> <th class="final-cost">Final Cost</th> <th
+    class="contract">Contract</th> <th class="consumer">Consumer</th> <th class="business">Business</th>
+    <th class="employees">Employees</th> </tr> </thead> <tfoot></tfoot> <tbody> <tr
+    class="row-other odd first"><td class="code">N/A</td><td class="code-description">Access
+    Line </td><td class="discount">$5</td><td class="final-cost">N/A</td><td class="contract">1
+    Yr</td> <td class="consumer"><span class=""></span></td> <td class="business"><span
+    class="check"></span></td> <td class="employees"><span class=""></span></td> </tr>
+    <tr class="row-other even"><td class="code">N/A</td><td class="code-description">Access
+    Line </td><td class="discount">$5</td><td class="final-cost">N/A</td><td class="contract">2
+    Yr</td> <td class="consumer"><span class=""></span></td> <td class="business"><span
+    class="check"></span></td> <td class="employees"><span class=""></span></td> </tr>
+    </tbody></table>'
+  - 'Context: payments Retail device purchases and exchanges To complete a digital
+    exchange transaction, customers must:Indirect Return and Exchange Customers must
+    contact the Indirect Agent where their service was activated to discuss equipment
+    returns or exchanges. Indirect channel policies may differ from Verizon policies.
+    Verizon recommends Indirect Agents assist customers with returns and exchanges.
+    The final determination is based on the Indirect Agent''s policy. ISPU orders
+    picked up in an Indirect Agent location can be returned at a location operated
+    by the same Agent, either by shipping the device back or in Retail. To return
+    or exchange a device, Indirect Agents must:Table: <table border="1" cellpadding="5"
+    cellspacing="0" width="100%"><tbody><tr><th style="text-align: center;" valign="top"
+    width="5%">Step</th><th style="text-align: left;" valign="top">Action</th></tr><tr><td
+    style="text-align: center;" valign="top" width="5%">1</td><td style="text-align:
+    left;" valign="top">Offer the customer the option to select a different device
+    or return the device originally purchased.<br/></td></tr><tr><td style="text-align:
+    center;" valign="top" width="5%">2</td><td style="text-align: left;" valign="top">Remove
+    the SIM card from the old 4G device and insert into the new 4G device.<br/></td></tr><tr><td
+    style="text-align: center;" valign="top" width="5%">3</td><td style="text-align:
+    left;" valign="top">Return the SIM card to the customer if the customer wishes
+    to return the device and not purchase a new device.<br/></td></tr><tr><td style="text-align:
+    center;" valign="top" width="5%">4</td><td><p>Return the customer''s SIM card
+    in the next Return Materials Authorization (RMA) box back to Verizon if the customer
+    does not want to keep the SIM.</p><p>Note:</p><ul><li>Indirect Agents must not
+    use the SIM card in another device that does not belong to the customer.<br/></li><li>SIM
+    cards must remain with the original device when returned or be placed in a plastic
+    bag in the next RMA box back to Verizon.</li><li>When exchanging equipment that
+    originally required a deposit to purchase to a type that does not require a deposit,
+    the system does not automatically credit the security deposit back to the original
+    MDN.<ul><li>The Indirect Agent must complete a manual refund request through Payment
+    Hub to return the deposit.</li></ul></li></ul></td></tr></tbody></table>'
+- source_sentence: What must a customer do to receive reactive assistance from any
+    of the business channels mentioned in the context?
+  sentences:
+  - 'Verizon Mobile Device Management (MDM) is designed to help customers manage corporate-owned
+    devices and remain compliant with company policies. The Verizon MDM solution suite
+    consists of the following services: Unified Endpoint Management (UEM) for mobile
+    devices including smartphones, tablets, Macs, Windows machines, et al Broadband
+    Hotspot Management (BBHS) for Jetpacks, MiFis, USB devices and routers, ie BPC-100
+    (Business Phone Connect) Verizon MDM Implementation Services is also available
+    as a companion product to Verizon MDM. Purchasing this service makes available
+    to the customer a dedicated Verizon Solutions Engineer to set up and configure
+    their Verizon MDM implementation for them, saving time and customer resources.'
+  - 'Reactive Customer Assistance All new business prospects and existing business
+    customers can reactively assist the customer, regardless of whether the account
+    is currently managed by: Retail SMB (R2B) Virtual to Business (V2B) Business to
+    Business (B2B) Indirect to Business (I2B) Business Agent The customer must initiate
+    contact with the reacting channel and express a need requiring assistance. Note:
+    Processed transactions on a current fraud hold do not roll to the original processing
+    representative once the hold is lifted, regardless if the fraud team directed
+    to another channel. Processed transactions that fail activation and need to be
+    reprocessed reside in the original channel with the originating representative.
+    If a transaction is reprocessed by another Verizon employee, the original representative
+    can submit a discrepancy for the activations. If a B2B Representative is engaged
+    in an account or is the primary DUNS owner and the customer wants to purchase
+    in store: Service the customer''s immediate needs by the end of the business day.
+    Account ownership stays with the B2B channel. The B2B Representative or COE must
+    complete any account maintenance or plan changes. Retail representatives can process
+    customers in store BAU regardless of DUNS ownership.'
+  - 'Customers who choose Professional Setup: It is a one-time $99 charge + taxes
+    & surcharges. Will appear on their next bill after installation is successful.
+    This charge is non-refundable and not included in the 30-Day Money-Back Guarantee
+    and not ACP discount eligible. Technician will setup 5G Home and connect up to
+    1 additional device to the router. For customers who want more devices connected
+    or set up in the home, offer Verizon Home Device Protect (VHDP). Note: Self Setup
+    customers who wish to switch to Pro Setup can only do so if they are high band
+    customers. Mid band customers are not elgible for Self to Pro Setup. Self Setup
+    high band customer will not be charged the $99 Professional Setup charge to move
+    to Pro Setup. Repair customers with high band equipment will not be charged. Pro
+    Setup Overview One Pager'
+- source_sentence: What are some common reasons for extending the Contract End Date
+    (CED) and Equipment Eligibility Upgrade (EEU) dates?
+  sentences:
+  - 'Contract End Date (CED): Represents when a mobile number is eligible to terminate
+    service without incurring an ETF. Equipment Eligibility Upgrade (EEU): Represent
+    when a mobile number is eligible to receive an upgrade. Both dates are systematically
+    calculated when a new device is activated. CED and EEU dates are generally the
+    same, but can differ in certain circumstances. Manual adjustments to dates are
+    rare and only approved to correct a billing, system or human error or in combination
+    with Finance approved programs. Common CED and EEU Date Extensions: Device activations
+    and upgrades. Loyalty offers and promotions (May extend the CED date without extending
+    the EEU date) Suspending without billing or with reduced rate billing. Automatically
+    extends the CED and EEU dates for a time period equal to the number of days that
+    the line was suspended. 2-year to device payment alternate upgrades The eligible
+    line''s CED and EEU dates are extended by the number of days remaining on the
+    ineligible line''s dates at the time of the transaction. An equipment return does
+    not revert the CED and EEU dates once the alternate upgrade is complete.'
+  - 'Context: not allowed. Consolidating accounts is not allowed. Eligibility may
+    not be applied retroactively. Data usage is not permitted. Data plans or data
+    add-on packages are not allowed. Lifeline applies to standard monthly customers
+    only. Business customers are not eligible. Cannot add features such as Roadside
+    Assistance and device insurance. Roaming is not allowed outside of the Lifeline
+    coverage area. Customers cannot enroll in My Verizon or make any account changes
+    online. Link Up cannot be applied to: Customer facilities equipment Cost of the
+    device or accessories Previous activation chargesCustomers may inquire about Lifeline
+    over the phone or online through verizonwireless.com/lifeline.Table: <table border="1"
+    cellpadding="5" width="100%"><tbody><tr><th style="text-align: left;" valign="top"
+    width="25%">New Customer</th><td style="text-align: left;" valign="top" width="75%"><p>If
+    a customer asks if they qualify for Lifeline:</p><ul><li>Enter their home billing
+    address in <a target="_blank">VZWMap</a><a href="http://" target="_blank"></a>.</li><li>VZWMap
+    indicates if their home billing address is within a VZW ETC area.</li></ul></td></tr><tr><th
+    style="text-align: left;" valign="top" width="25%">Existing Lifeline Customer</th><td
+    style="text-align: left;" valign="top" width="75%"><p>If an existing Lifeline
+    customer inquires about Lifeline over the phone, check account in ACSS:</p><ul><li>If
+    the customer''s MTN does not appear in ACSS with the designation <b>LL</b>, they
+    are not a VZW Lifeline customer. Refer them to the paperwork that came with their
+    phone.</li><li>If the customer''s MTN appears in ACSS, and shows them to be a
+    VZW Lifeline customer:<ul><li>Customers must speak directly to <a href="/content/km/contacts.html?c#11773"
+    target="_blank">Lifeline Support</a>.</li><li>Transfer the customer or provide
+    customer with the number so they can contact <a href="/content/km/contacts.html?c#11773"
+    target="_blank">Lifeline Support</a> directly.</li></ul></li></ul></td></tr></tbody></table>'
+  - 'State Privacy Rights California enacted the California Consumer Privacy Act (CCPA)
+    in 2020. Since the CCPA came into effect, more states have passed privacy laws.
+    Today there are multiple states across the country with comprehensive privacy
+    laws that govern how personal information is collected, used and shared. Verizon
+    allows consumers nationwide to exercise use the privacy controls. This means Verizon
+    has made state specific laws uniform across the nation for simplified handling.
+    Most states with comprehensive privacy laws provide individuals with specific
+    rights, including the right to: Know, access and delete information not required
+    for business purposes. Receive equal pricing and quality of product or service
+    if someone invokes these rights. Correct inaccurate information maintained by
+    the business. Limit the use and disclosure of sensitive personal information.
+    Right to say no to the sale of personal information of sharing personal information
+    for purposes of cross context behavioral advertising and right to opt out of targeted
+    advertising. Appeal (only applicable in Colorado, Connecticut and Virginia). See
+    the Detailed Rights > Right to Appeal section for exceptions to the nationwide
+    handling. State Privacy Rights and Gizmo Customers can take advantage of privacy
+    controls in the GizmoHub app on the customer''s phone. Customers are entitled
+    to the following rights: Access personal information that is being collected and
+    stored in the app. Delete devices associated with an account as well as delete
+    an account. Correct the data associated with the customer''s account (some data
+    elements are unable to be corrected, such as the email address or phone number
+    associated with the account). Right to Access Users can request and download personal
+    information through the following steps: Right to Delete Follow the below steps
+    to delete an account: Follow the below steps to delete a Gizmo watch: Right to
+    Correct Some data elements can be corrected such as the email address or phone
+    number associated with the account. If the user wants to change either the email
+    or the phone number, the user must first delete all the devices from the account
+    and then delete the account itself. Refer to the Right to Delete table above.
+    The user can then re-create the account with the new email or phone number. Follow
+    the below steps: Right to Appeal (applicable in Colorado, Connecticut or Virginia
+    only) Follow these steps to appeal a denied privacy request: Nevada State Rights
+    Nevada law allows customers to opt out of the sale of personally identifiable
+    information by online service providers such as website operators. Verizon does
+    not sell personally identifiable information. If Verizon ever starts selling personal
+    information, current Verizon customers will be opted out. If customers have additional
+    questions, direct the customer to the Privacy Inquiry Form. If the customer has
+    additional questions regarding State Privacy Rights or Gizmo Privacy Policies:'
+- source_sentence: What steps should the Fulfillment SPC Leadership take when an Internal
+    Partner forwards an escalation request?
+  sentences:
+  - 'Context: team (a selected group of offline individuals) completes all escalated
+    requests. Escalations from a previous representative will not be reassigned to
+    that representative rather assigned and handled through the Escalation team. The
+    representative''s supervisor receives real-time feedback to provide the representative
+    immediate coaching and corrective action. Do not assign escalated requests to
+    the Outbound team. The Escalations team owns all escalated requests. If a call
+    to PACT is needed for credit approval, the Outbound team can assist but will not
+    own the request. If more information is needed to complete the request, follow
+    the AIR guidelines.Ways to Receive Escalated RequestsTable: <table border="1"
+    cellpadding="5" cellspacing="0" width="100%"><tbody><tr><th style="text-align:
+    left;" valign="top">If ...</th><th style="text-align: left;" valign="top">Then
+    ...</th></tr><tr><td style="text-align: left;" valign="top">the reason for the
+    escalation is due to a mistake on the original COE-processed application</td><td
+    style="text-align: left;" valign="top"><p>do not reassign to the original coordinator.<br/><br/>Note: <span
+    style="background-color: transparent;">The Escalation Representative assigned
+    the request makes the necessary changes/corrections and completes the request.</span></p></td></tr><tr><td
+    style="text-align: left;" valign="top">the reason for the escalation is a Missed
+    SLA / Revenue Impacting Order<br/></td><td style="text-align: left;" valign="top"><ul><li>Do
+    not reassign the escalation email request to the coordinator who has the related
+    email if the related WFM is with a coordinator who does not belong to the Escalation
+    team and is in <b>Wait</b> status.<br/></li><li>Own the escalated WFM and monitor
+    the progress of the original request until completion.</li><li>Create a case to
+    track completion of the request.</li><li>Be responsible for providing the updates
+    to the Sales partner by sending an email with the status and timelines as possible.</li><li>Complete
+    WFM as (Request Type) Correspondence.</li></ul></td></tr><tr><td style="text-align:
+    left;" valign="top">the related WFM is with another Center/Team<br/></td><td style="text-align:
+    left;" valign="top"><p>reassign any follow-up emails related to that request in
+    order for that team to continue to own it.<br/></p><ul><li>Do not respond to provide
+    an update. </li><li>Submit a reassignment request if needed.</li></ul></td></tr><tr><td
+    style="text-align: left;" valign="top">Internal Partners forward the escalation
+    request<br/></td><td style="text-align: left;" valign="top"><p>the Fulfillment
+    SPC Leadership does the following:<br/></p><ol><li>Acknowledges the email.</li><li>Provides
+    an update within 1 hour after acknowledgement.</li><li>Tracks completion until
+    closure and provides updates as needed.<ul><li>If the assigned lead is out of
+    the office or unavailable, another leader will cover on their behalf.</li></ul></li></ol></td></tr></tbody></table>'
+  - 'Restrict Direct Carrier Billing Customers can add restrictions for Slacker Streaming
+    Radio Carrier Billing. To block Slacker Streaming Radio billing: Receive request
+    to block Slacker Streaming Radio. Block Feature Name - Purchase and Gifting Block
+    (formerly Web Purchases block). Add SFO 75440 (Purchase and Gifting Block) to
+    customer''s MDN. What''s Blocked - Slacker Streaming Radio bills being applied
+    to the Verizon bill. Blocking Methods - My Verizon (vzw.com/safeguards) and CS.
+    Note: The Purchase and Gifting Block cannot be added to Corporate or Government
+    accounts. To remove the Slacker subscription, the subscription charge must be
+    cancelled in ACSS. The subscription expires at the next subscription renewal date.
+    Once the subscription expires, the Corporate or Government account is not allowed
+    to charge Slacker Radio to the Verizon bill. Customers have the option to pay
+    by credit card. The block is compatible with Verizon devices.'
+  - 'Context: Program provides VZW B2B Data Sales Teams with a selection of key M2M
+    certified devices for use in customer pilots pursuant to a sale. This program
+    is intended to motivate and enable the VZW B2B Data Sales Teams to generate M2M
+    sales. The program is available for Data Sales Teams residing in the 4 VZW B2B
+    Sales Areas and the Enterprise and Government group. It contains a portfolio of
+    key M2M devices that may provide a pilot at no cost to the customer when connected
+    on area-supplied concession lines or test lines.Contact Nishant Shah [email protected]
+    to request these solution-based devices:Table: <table border="1" cellpadding="5"
+    width="100%"><tbody><tr><td style="text-align: left;" valign="top" width="30%"><b>Manufacturer</b></td><td
+    style="text-align: left;" valign="top" width="70%"><b>Model</b></td></tr><tr><td
+    style="text-align: left;" valign="top" width="30%">Cisco</td><td style="text-align:
+    left;" valign="top" width="70%">Demo</td></tr></tbody></table>'
+pipeline_tag: sentence-similarity
+library_name: sentence-transformers
+---
+
+# SentenceTransformer based on sentence-transformers/all-MiniLM-L6-v2
+
+This is a [sentence-transformers](https://www.SBERT.net) model finetuned from [sentence-transformers/all-MiniLM-L6-v2](https://huggingface.co/sentence-transformers/all-MiniLM-L6-v2). It maps sentences & paragraphs to a 384-dimensional dense vector space and can be used for semantic textual similarity, semantic search, paraphrase mining, text classification, clustering, and more.
+
+## Model Details
+
+### Model Description
+- **Model Type:** Sentence Transformer
+- **Base model:** [sentence-transformers/all-MiniLM-L6-v2](https://huggingface.co/sentence-transformers/all-MiniLM-L6-v2) <!-- at revision fa97f6e7cb1a59073dff9e6b13e2715cf7475ac9 -->
+- **Maximum Sequence Length:** 256 tokens
+- **Output Dimensionality:** 384 dimensions
+- **Similarity Function:** Cosine Similarity
+<!-- - **Training Dataset:** Unknown -->
+<!-- - **Language:** Unknown -->
+<!-- - **License:** Unknown -->
+
+### Model Sources
+
+- **Documentation:** [Sentence Transformers Documentation](https://sbert.net)
+- **Repository:** [Sentence Transformers on GitHub](https://github.com/UKPLab/sentence-transformers)
+- **Hugging Face:** [Sentence Transformers on Hugging Face](https://huggingface.co/models?library=sentence-transformers)
+
+### Full Model Architecture
+
+```
+SentenceTransformer(
+  (0): Transformer({'max_seq_length': 256, 'do_lower_case': False}) with Transformer model: BertModel 
+  (1): Pooling({'word_embedding_dimension': 384, 'pooling_mode_cls_token': False, 'pooling_mode_mean_tokens': True, 'pooling_mode_max_tokens': False, 'pooling_mode_mean_sqrt_len_tokens': False, 'pooling_mode_weightedmean_tokens': False, 'pooling_mode_lasttoken': False, 'include_prompt': True})
+  (2): Normalize()
+)
+```
+
+## Usage
+
+### Direct Usage (Sentence Transformers)
+
+First install the Sentence Transformers library:
+
+```bash
+pip install -U sentence-transformers
+```
+
+Then you can load this model and run inference.
+```python
+from sentence_transformers import SentenceTransformer
+
+# Download from the 🤗 Hub
+model = SentenceTransformer("shivamgoel97/finetunesentence")
+# Run inference
+sentences = [
+    'What steps should the Fulfillment SPC Leadership take when an Internal Partner forwards an escalation request?',
+    'Context: team (a selected group of offline individuals) completes all escalated requests. Escalations from a previous representative will not be reassigned to that representative rather assigned and handled through the Escalation team. The representative\'s supervisor receives real-time feedback to provide the representative immediate coaching and corrective action. Do not assign escalated requests to the Outbound team. The Escalations team owns all escalated requests. If a call to PACT is needed for credit approval, the Outbound team can assist but will not own the request. If more information is needed to complete the request, follow the AIR guidelines.Ways to Receive Escalated RequestsTable: <table border="1" cellpadding="5" cellspacing="0" width="100%"><tbody><tr><th style="text-align: left;" valign="top">If ...</th><th style="text-align: left;" valign="top">Then ...</th></tr><tr><td style="text-align: left;" valign="top">the reason for the escalation is due to a mistake on the original COE-processed application</td><td style="text-align: left;" valign="top"><p>do not reassign to the original coordinator.<br/><br/>Note:\xa0<span style="background-color: transparent;">The Escalation Representative assigned the request makes the necessary changes/corrections and completes the request.</span></p></td></tr><tr><td style="text-align: left;" valign="top">the reason for the escalation is a Missed SLA / Revenue Impacting Order<br/></td><td style="text-align: left;" valign="top"><ul><li>Do not reassign the escalation email request to the coordinator who has the related email if the related WFM is with a coordinator who does not belong to the Escalation team and is in\xa0<b>Wait</b>\xa0status.<br/></li><li>Own the escalated WFM and monitor the progress of the original request until completion.</li><li>Create a case to track completion of the request.</li><li>Be responsible for providing the updates to the Sales partner by sending an email with the status and timelines as possible.</li><li>Complete WFM as (Request Type) Correspondence.</li></ul></td></tr><tr><td style="text-align: left;" valign="top">the related WFM is with another Center/Team<br/></td><td style="text-align: left;" valign="top"><p>reassign any follow-up emails related to that request in order for that team to continue to own it.<br/></p><ul><li>Do not respond to provide an update.\xa0</li><li>Submit a reassignment request if needed.</li></ul></td></tr><tr><td style="text-align: left;" valign="top">Internal Partners forward the escalation request<br/></td><td style="text-align: left;" valign="top"><p>the Fulfillment SPC Leadership does the following:<br/></p><ol><li>Acknowledges the email.</li><li>Provides an update within 1 hour after acknowledgement.</li><li>Tracks completion until closure and provides updates as needed.<ul><li>If the assigned lead is out of the office or unavailable, another leader will cover on their behalf.</li></ul></li></ol></td></tr></tbody></table>',
+    'Context: Program provides VZW B2B Data Sales Teams with a selection of key M2M certified devices for use in customer pilots pursuant to a sale. This program is intended to motivate and enable the VZW B2B Data Sales Teams to generate M2M sales. The program is available for Data Sales Teams residing in the 4 VZW B2B Sales Areas and the Enterprise and Government group. It contains a portfolio of key M2M devices that may provide a pilot at no cost to the customer when connected on area-supplied concession lines or test lines.Contact Nishant Shah [email protected] to request these solution-based devices:Table: <table border="1" cellpadding="5" width="100%"><tbody><tr><td style="text-align: left;" valign="top" width="30%"><b>Manufacturer</b></td><td style="text-align: left;" valign="top" width="70%"><b>Model</b></td></tr><tr><td style="text-align: left;" valign="top" width="30%">Cisco</td><td style="text-align: left;" valign="top" width="70%">Demo</td></tr></tbody></table>',
+]
+embeddings = model.encode(sentences)
+print(embeddings.shape)
+# [3, 384]
+
+# Get the similarity scores for the embeddings
+similarities = model.similarity(embeddings, embeddings)
+print(similarities.shape)
+# [3, 3]
+```
+
+<!--
+### Direct Usage (Transformers)
+
+<details><summary>Click to see the direct usage in Transformers</summary>
+
+</details>
+-->
+
+<!--
+### Downstream Usage (Sentence Transformers)
+
+You can finetune this model on your own dataset.
+
+<details><summary>Click to expand</summary>
+
+</details>
+-->
+
+<!--
+### Out-of-Scope Use
+
+*List how the model may foreseeably be misused and address what users ought not to do with the model.*
+-->
+
+<!--
+## Bias, Risks and Limitations
+
+*What are the known or foreseeable issues stemming from this model? You could also flag here known failure cases or weaknesses of the model.*
+-->
+
+<!--
+### Recommendations
+
+*What are recommendations with respect to the foreseeable issues? For example, filtering explicit content.*
+-->
+
+## Training Details
+
+### Training Dataset
+
+#### Unnamed Dataset
+
+
+* Size: 7,057 training samples
+* Columns: <code>sentence_0</code>, <code>sentence_1</code>, and <code>label</code>
+* Approximate statistics based on the first 1000 samples:
+  |         | sentence_0                                                                        | sentence_1                                                                           | label                                           |
+  |:--------|:----------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------|:------------------------------------------------|
+  | type    | string                                                                            | string                                                                               | int                                             |
+  | details | <ul><li>min: 11 tokens</li><li>mean: 24.8 tokens</li><li>max: 49 tokens</li></ul> | <ul><li>min: 91 tokens</li><li>mean: 230.28 tokens</li><li>max: 256 tokens</li></ul> | <ul><li>0: ~29.30%</li><li>1: ~70.70%</li></ul> |
+* Samples:
+  | sentence_0                                                                                                                               | sentence_1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | label          |
+  |:-----------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------|
+  | <code>What steps should be taken if the appropriate ticket is not visible?</code>                                                        | <code>Context: appropriate ticket may not be visible. Click View Ticket Details for more information. Type in Ticket Number and click Search. Scroll to the bottom of the screen to view the Comments Log, which contains all the information about the ticket's creation and resolution. Tickets can also be located by picking a date range (Start Date and End Date), selecting Me as the Assigned To value and clicking Search to pull up all tickets created by the Representative doing the searching.Email the escalations mailbox and request the ticket be closed. Note: Cancel, Fraud Cancel and Address Change tickets cannot be undone.Table: <table border="1" cellpadding="5" cellspacing="0" width="100%"><tbody><tr><th style="text-align: left;" valign="top">Ticket rejection reason</th><th style="text-align: left;" valign="top">Solution</th></tr><tr><td style="text-align: left;" valign="top">Missing or invalid information</td><td style="text-align: left;" valign="top"><p>After utilizing all available resource...</code> | <code>1</code> |
+  | <code>What are the steps to assign an Account Manager in My Verizon when the Account Manager does not have an MDN on the account?</code> | <code>Context: and password The Account Manager: Is listed as an Authorized User in the Billing System and in My Verizon Can transact account business on My Verizon, My Verizon Express, in-store and by calling CS. Assign Account Manager In-Store or CS Access Only: Account Owner follows these steps: Note: This process can be used when the Account Manager does not have an MDN on the account. The Account Manager is listed as Authorized User in the billing system and has access to transact account business in-store or with CS. Adding an Account Manager is not restricted to a Digital Only Transaction.Table: <table border="1" cellpadding="5" cellspacing="0" width="100%"><tbody><tr><th style="text-align: center;" valign="top" width="5%">Step</th><th style="text-align: left;" valign="top">Action</th></tr><tr><td style="text-align: center;" valign="top" width="5%">1</td><td style="text-align: left;" valign="top">Sign in to My Verizon.<br/></td></tr><tr><td style="text-align: center;" valign="top" wid...</code> | <code>1</code> |
+  | <code>What should an agent do if a case is received with an executive handle tagged?</code>                                              | <code>Context: to send the form). W-9 addresses must always be the corporate address of record for the entity servicing the customer. W-9s are issued to claim exemption from withholding (i.e., 1099) and provide the name and address for information reporting. Payment Questions The EPO Support team is unable to answer any questions about payments and applications. For wireless customers, open a Payment Investigation Ticket through ACSS. For further assistance, search for “Accessing Payment Hub in ACSS” through InfoManager. For wireline customers, open a Payment Investigation Ticket through the Payment Hub. For further assistance, search for “Payment Hub Participants Guide” through VZKnowledge.Table: <table border="1" cellpadding="5" cellspacing="0" width="100%"><tbody><tr><th style="text-align: center;" valign="top" width="5%">Step</th><th style="text-align: left;" valign="top">Action</th></tr><tr><td style="text-align: center;" valign="top" width="5%">1</td><td style="text-align: left;" valig...</code> | <code>0</code> |
+* Loss: [<code>CosineSimilarityLoss</code>](https://sbert.net/docs/package_reference/sentence_transformer/losses.html#cosinesimilarityloss) with these parameters:
+  ```json
+  {
+      "loss_fct": "torch.nn.modules.loss.MSELoss"
+  }
+  ```
+
+### Training Hyperparameters
+#### Non-Default Hyperparameters
+
+- `multi_dataset_batch_sampler`: round_robin
+
+#### All Hyperparameters
+<details><summary>Click to expand</summary>
+
+- `overwrite_output_dir`: False
+- `do_predict`: False
+- `eval_strategy`: no
+- `prediction_loss_only`: True
+- `per_device_train_batch_size`: 8
+- `per_device_eval_batch_size`: 8
+- `per_gpu_train_batch_size`: None
+- `per_gpu_eval_batch_size`: None
+- `gradient_accumulation_steps`: 1
+- `eval_accumulation_steps`: None
+- `torch_empty_cache_steps`: None
+- `learning_rate`: 5e-05
+- `weight_decay`: 0.0
+- `adam_beta1`: 0.9
+- `adam_beta2`: 0.999
+- `adam_epsilon`: 1e-08
+- `max_grad_norm`: 1
+- `num_train_epochs`: 3
+- `max_steps`: -1
+- `lr_scheduler_type`: linear
+- `lr_scheduler_kwargs`: {}
+- `warmup_ratio`: 0.0
+- `warmup_steps`: 0
+- `log_level`: passive
+- `log_level_replica`: warning
+- `log_on_each_node`: True
+- `logging_nan_inf_filter`: True
+- `save_safetensors`: True
+- `save_on_each_node`: False
+- `save_only_model`: False
+- `restore_callback_states_from_checkpoint`: False
+- `no_cuda`: False
+- `use_cpu`: False
+- `use_mps_device`: False
+- `seed`: 42
+- `data_seed`: None
+- `jit_mode_eval`: False
+- `use_ipex`: False
+- `bf16`: False
+- `fp16`: False
+- `fp16_opt_level`: O1
+- `half_precision_backend`: auto
+- `bf16_full_eval`: False
+- `fp16_full_eval`: False
+- `tf32`: None
+- `local_rank`: 0
+- `ddp_backend`: None
+- `tpu_num_cores`: None
+- `tpu_metrics_debug`: False
+- `debug`: []
+- `dataloader_drop_last`: False
+- `dataloader_num_workers`: 0
+- `dataloader_prefetch_factor`: None
+- `past_index`: -1
+- `disable_tqdm`: False
+- `remove_unused_columns`: True
+- `label_names`: None
+- `load_best_model_at_end`: False
+- `ignore_data_skip`: False
+- `fsdp`: []
+- `fsdp_min_num_params`: 0
+- `fsdp_config`: {'min_num_params': 0, 'xla': False, 'xla_fsdp_v2': False, 'xla_fsdp_grad_ckpt': False}
+- `fsdp_transformer_layer_cls_to_wrap`: None
+- `accelerator_config`: {'split_batches': False, 'dispatch_batches': None, 'even_batches': True, 'use_seedable_sampler': True, 'non_blocking': False, 'gradient_accumulation_kwargs': None}
+- `deepspeed`: None
+- `label_smoothing_factor`: 0.0
+- `optim`: adamw_torch
+- `optim_args`: None
+- `adafactor`: False
+- `group_by_length`: False
+- `length_column_name`: length
+- `ddp_find_unused_parameters`: None
+- `ddp_bucket_cap_mb`: None
+- `ddp_broadcast_buffers`: False
+- `dataloader_pin_memory`: True
+- `dataloader_persistent_workers`: False
+- `skip_memory_metrics`: True
+- `use_legacy_prediction_loop`: False
+- `push_to_hub`: False
+- `resume_from_checkpoint`: None
+- `hub_model_id`: None
+- `hub_strategy`: every_save
+- `hub_private_repo`: None
+- `hub_always_push`: False
+- `gradient_checkpointing`: False
+- `gradient_checkpointing_kwargs`: None
+- `include_inputs_for_metrics`: False
+- `include_for_metrics`: []
+- `eval_do_concat_batches`: True
+- `fp16_backend`: auto
+- `push_to_hub_model_id`: None
+- `push_to_hub_organization`: None
+- `mp_parameters`: 
+- `auto_find_batch_size`: False
+- `full_determinism`: False
+- `torchdynamo`: None
+- `ray_scope`: last
+- `ddp_timeout`: 1800
+- `torch_compile`: False
+- `torch_compile_backend`: None
+- `torch_compile_mode`: None
+- `dispatch_batches`: None
+- `split_batches`: None
+- `include_tokens_per_second`: False
+- `include_num_input_tokens_seen`: False
+- `neftune_noise_alpha`: None
+- `optim_target_modules`: None
+- `batch_eval_metrics`: False
+- `eval_on_start`: False
+- `use_liger_kernel`: False
+- `eval_use_gather_object`: False
+- `average_tokens_across_devices`: False
+- `prompts`: None
+- `batch_sampler`: batch_sampler
+- `multi_dataset_batch_sampler`: round_robin
+
+</details>
+
+### Training Logs
+| Epoch  | Step | Training Loss |
+|:------:|:----:|:-------------:|
+| 0.5663 | 500  | 0.111         |
+| 1.1325 | 1000 | 0.0838        |
+| 1.6988 | 1500 | 0.0721        |
+| 2.2650 | 2000 | 0.061         |
+| 2.8313 | 2500 | 0.0588        |
+
+
+### Framework Versions
+- Python: 3.10.12
+- Sentence Transformers: 3.3.1
+- Transformers: 4.47.1
+- PyTorch: 2.5.1+cu121
+- Accelerate: 1.2.1
+- Datasets: 3.2.0
+- Tokenizers: 0.21.0
+
+## Citation
+
+### BibTeX
+
+#### Sentence Transformers
+```bibtex
+@inproceedings{reimers-2019-sentence-bert,
+    title = "Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks",
+    author = "Reimers, Nils and Gurevych, Iryna",
+    booktitle = "Proceedings of the 2019 Conference on Empirical Methods in Natural Language Processing",
+    month = "11",
+    year = "2019",
+    publisher = "Association for Computational Linguistics",
+    url = "https://arxiv.org/abs/1908.10084",
+}
+```
+
+<!--
+## Glossary
+
+*Clearly define terms in order to be accessible across audiences.*
+-->
+
+<!--
+## Model Card Authors
+
+*Lists the people who create the model card, providing recognition and accountability for the detailed work that goes into its construction.*
+-->
+
+<!--
+## Model Card Contact
+
+*Provides a way for people who have updates to the Model Card, suggestions, or questions, to contact the Model Card authors.*
+-->

config.json

@@ -0,0 +1,26 @@
+{
+  "_name_or_path": "sentence-transformers/all-MiniLM-L6-v2",
+  "architectures": [
+    "BertModel"
+  ],
+  "attention_probs_dropout_prob": 0.1,
+  "classifier_dropout": null,
+  "gradient_checkpointing": false,
+  "hidden_act": "gelu",
+  "hidden_dropout_prob": 0.1,
+  "hidden_size": 384,
+  "initializer_range": 0.02,
+  "intermediate_size": 1536,
+  "layer_norm_eps": 1e-12,
+  "max_position_embeddings": 512,
+  "model_type": "bert",
+  "num_attention_heads": 12,
+  "num_hidden_layers": 6,
+  "pad_token_id": 0,
+  "position_embedding_type": "absolute",
+  "torch_dtype": "float32",
+  "transformers_version": "4.47.1",
+  "type_vocab_size": 2,
+  "use_cache": true,
+  "vocab_size": 30522
+}

config_sentence_transformers.json

@@ -0,0 +1,10 @@
+{
+  "__version__": {
+    "sentence_transformers": "3.3.1",
+    "transformers": "4.47.1",
+    "pytorch": "2.5.1+cu121"
+  },
+  "prompts": {},
+  "default_prompt_name": null,
+  "similarity_fn_name": "cosine"
+}

model.safetensors

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b2507fa556566ed0bee8fb5b27510cdb7c00a5dd086f315c38a0615a1349a634
+size 90864192

modules.json

@@ -0,0 +1,20 @@
+[
+  {
+    "idx": 0,
+    "name": "0",
+    "path": "",
+    "type": "sentence_transformers.models.Transformer"
+  },
+  {
+    "idx": 1,
+    "name": "1",
+    "path": "1_Pooling",
+    "type": "sentence_transformers.models.Pooling"
+  },
+  {
+    "idx": 2,
+    "name": "2",
+    "path": "2_Normalize",
+    "type": "sentence_transformers.models.Normalize"
+  }
+]

sentence_bert_config.json

@@ -0,0 +1,4 @@
+{
+  "max_seq_length": 256,
+  "do_lower_case": false
+}

special_tokens_map.json

@@ -0,0 +1,37 @@
+{
+  "cls_token": {
+    "content": "[CLS]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  },
+  "mask_token": {
+    "content": "[MASK]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  },
+  "pad_token": {
+    "content": "[PAD]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  },
+  "sep_token": {
+    "content": "[SEP]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  },
+  "unk_token": {
+    "content": "[UNK]",
+    "lstrip": false,
+    "normalized": false,
+    "rstrip": false,
+    "single_word": false
+  }
+}

tokenizer_config.json

@@ -0,0 +1,65 @@
+{
+  "added_tokens_decoder": {
+    "0": {
+      "content": "[PAD]",
+      "lstrip": false,
+      "normalized": false,
+      "rstrip": false,
+      "single_word": false,
+      "special": true
+    },
+    "100": {
+      "content": "[UNK]",
+      "lstrip": false,
+      "normalized": false,
+      "rstrip": false,
+      "single_word": false,
+      "special": true
+    },
+    "101": {
+      "content": "[CLS]",
+      "lstrip": false,
+      "normalized": false,
+      "rstrip": false,
+      "single_word": false,
+      "special": true
+    },
+    "102": {
+      "content": "[SEP]",
+      "lstrip": false,
+      "normalized": false,
+      "rstrip": false,
+      "single_word": false,
+      "special": true
+    },
+    "103": {
+      "content": "[MASK]",
+      "lstrip": false,
+      "normalized": false,
+      "rstrip": false,
+      "single_word": false,
+      "special": true
+    }
+  },
+  "clean_up_tokenization_spaces": false,
+  "cls_token": "[CLS]",
+  "do_basic_tokenize": true,
+  "do_lower_case": true,
+  "extra_special_tokens": {},
+  "mask_token": "[MASK]",
+  "max_length": 128,
+  "model_max_length": 256,
+  "never_split": null,
+  "pad_to_multiple_of": null,
+  "pad_token": "[PAD]",
+  "pad_token_type_id": 0,
+  "padding_side": "right",
+  "sep_token": "[SEP]",
+  "stride": 0,
+  "strip_accents": null,
+  "tokenize_chinese_chars": true,
+  "tokenizer_class": "BertTokenizer",
+  "truncation_side": "right",
+  "truncation_strategy": "longest_first",
+  "unk_token": "[UNK]"
+}