--- tags: - sentence-transformers - sentence-similarity - feature-extraction - generated_from_trainer - dataset_size:10500 - loss:CosineSimilarityLoss base_model: sentence-transformers/all-MiniLM-L6-v2 widget: - source_sentence: What are the account requirements for a consumer liable account to be eligible for a CLNR under the in-warranty requirements? sentences: - 'Context: POS pulls from multiple databases to determine if a device is eligible for a replacement by Verizon. If the CLNR eligibility flag and out of warranty message is incorrect, check these steps before completing an "Out of Warranty Review" with Tech Support. How to Process an Out of Warranty Review The Tech Support Coordinator researches and offers results, either the message is correct and this device is not eligible for CLNR or is able to process a CLNR for your customer. See Device Forums.See the table below for special handling and exceptions.CLNR eligibility time periods from date of purchase are:Table:
Account Requirements | In-warranty
requirements:
|
---|---|
Equipment Requirements | In-warranty requirements:
Note: Be sure to check the CLNR eligibility on the line before placing a CLNR order. |
Warranty Timeframe Requirements | Warranty timeframe requirements by device type:
|
What Voids a Warranty | A Voided Out-of-Warranty (VOW) device is a device no longer eligible for a free CLNR even within 12 months of purchase or with an extended warranty. VOW devices:
|
Component | Description |
---|---|
Small Cell | Small cells:
|
Packet Core |
|
Optional Storage and Compute |
|
Remote Monitoring | Gain full control with near real-time and virtually 24/7 monitoring of the health of the private network, including:
|
Spectrum |
|
User Management | User management allows for:
|
Deployment | The solution is delivered and deployed as a managed solution, so Verizon:
|
Customer Portal | The Customer Portal provides a dashboard enabling designated users to:
|
Optional Components | Optional Components include:
|
Step | Action |
---|---|
1 | Access the Device ID field in the Device Payment History screen in ACSS. |
2 | Identify the Device ID associated with the device payment agreement. |
3 | Verify the rejected device is the correct device the customer is returning (the device IDs may not match). Note: IDs
not matching is a defect due to situations where the Device ID is not updated
after an authorized replacement (e.g., Certified Like New [CLNR], Asurion replacement,
AppleCare replacement, Indirect Agent insurance, etc.). |
4 | Advise the customer that the device cannot be updated. |
5 | Contact a Supervisor, Coordinator or Sr. Representative to process the Device ID override if the correct device is returned. |
6 | Inform the agent of the appropriate action based on if the correct device is returned.
Note: A tracking email is automatically sent to the Certified Returns Testing Center (CRTC). |
7 | Instruct
the agent employee to advise the customer of the following:
|
Step | Action |
---|---|
1 | Review the customer information dropdown to check for missing information in the required fields. |
2 | Click
the cursor in the ZIP field. |
3 | Press the tab key to automatically generate the application ZIP code or city and state (if the ZIP code is present but the ZIP extension or city and state are missing). |
4 | Remove any special characters from all
customer information fields to troubleshoot the error. |
5 | Select Save. |
6 | Select Resend Known Fraud Bad Debt (KFBD) in the Review
and Resend menu to send the application back through the credit cycle waterfall. |
7 | Refresh the application status. Note: If the application goes back to MR/CP status, continue to Step 8. |
8 | Change the status to HD/OP. |
9 | Remark
the credit application. |
10 | Notify a Supervisor
and/or Porting, Activation & Credit Operations of the issue. |
Contact Numbers for Pennsylvania (PA) | ||||
---|---|---|---|---|
Department | Internal / Agent Number | External / Customer Number | Hours of Operation | Description |
Assignment Provisioning Center (APC) | 800-339-6459 | Mon - Fri, | ||
Buried Service Wire (BSW) | See OCC. (from main prompt, select "cable") | Mon
- Fri, | Buried Drop | |
Business
Digital Solution Center (BDSC) | 844-540-7803 | 24
hours a day x 7 days a week | BDSC is FSC for BDV Repair ONLY | |
Business Sales & Billing Center (BSBC) | 855-790-0453 | 800-VERIZON (800-837-4966) | Mon - Fri, | All |
Consumer Sales and Service
Center (CSSC) | 855-790-0308 | 800-VERIZON (800-837-4966) | Mon - Fri, Fios Retention: | Consumer Fios / HSI / Copper Sales / Service / Retention / Cancel Pending Order |
Enhanced Verizon Resolution Center (EVRC) | 855-757-0760 | 800-VERIZON (800-837-4966) | 24 hours
a day x 7 days a week | |
Multilingual
Business Service Center (MBSC) | 833-433-1325 | 800-VERIZON (800-837-4966) | Mon - Fri, 8:30 AM - 6 PM | All States |
Multilingual
Sales & Service Center (MSSC) | Spanish: 855-690-3054 Chinese: 877-459-4055 | 800-VERIZON (800-837-4966) | Spanish: | Fiber Capable / Served - Orders and Billing |
Network
Test Center (NTC) | 800-315-5604 800-971-0050 (overflow) | Mon - Fri, 7 AM - 6 PM Sat - Sun, 8 AM -4 PM | ||
Operations
Control Center (OCC) Formerly known as Dispatch Resource Center (DRC) | Optix Chat is the primary
method of contact. 855-468-6271 | 24
hours a day x 7 days a week | ||
Recent
Change Memory Administration Center (RCMAC) | For
use by Manager or Floor Support only. 800-932-2230 | Mon - Fri, | ACs 215, 267, 412, 484, 570, 610, 717, 724, 814, 878 Complete all troubleshooting
first. |
Situation | Action |
---|---|
Immediate
supervisor is available to approve the pending credit. | Supervisors must:
|
Immediate supervisor is not available to approve
the pending credit. | Reach out to available Supervisors to enter their USWIN ID and Supervisor PIN for approval. |
A customer is on a daily or legacy per minute price plan and requires a credit adjustment. | Immediate Supervisor or next level approver processes credit adjustment and routes through Credit Escalation Queue. |
There is a credit restricted account. | Next level approvers (i.e., Ops Manager) are required to process and must enter their USWIN ID and Supervisor PIN for approval. |
No supervisor is available. | Representatives route the credit for approval to their immediate Supervisor''s Credit Escalation Queue by selecting the Sup Review option on the Supervisor Approval Required panel. |
Supervisor advises that more time is required to evaluate the credit. | Route the credit to immediate Supervisor by selecting the Sup Review option. |
Stage | Who | Does What |
---|---|---|
1 | Representative | Uses the Customer Verification Screen (CVS):
|
2 | Customer | Completes
the following steps:
|
If there are ... | Then ... |
---|---|
multiple leads submitted that meet the submission guidelines | Verizon Connect uses the first Verizon submitted lead (based on Lead submission date) as the accepted record. Note:
Any MDN discrepancies between Verizon Representatives are handled solely between
the Verizon Representatives in market. |
multiple leads submitted that all fail to meet
the lead submission guidelines | all leads are rejected. Note: The leads are not merged with
the Verizon Connect account. |
multiple leads submitted and some pass the lead submission
guidelines | Verizon Connect uses the first submitted lead that followed and cleared these guidelines. Note:
Any discrepancies between Verizon Representatives are handled solely between the
Verizon Representatives in Market. |
current Verizon Customers with existing Verizon
Connect service | the
lead expires the same as explained in Lead Expiration. |
Stage | Who | Does What |
---|---|---|
1 | SLED Sales Representative | Confirms the customer''s contract is
amended to include eFax.
|
2 | Contract Management Team | Reviews BuSS request, and if approved forwards the request to the BFO to enable the customer profile for eFAX (based on contract availability). |
3 | BFO | Completes
request, and replies all upon completion. |
4 | SLED Sales Representative | Works with the customer to complete the
license order. |
5 | eFax | Activates the licenses and sends a welcome / get started email to the customer’s email sales entered in POS. |
Discount Plan | SPO | Discount Amount | |
---|---|---|---|
Includes select 5G mobile plans | 5G Home Plus | 2722 | -$25 |
5G Home | 2725 | -$15 | |
LTE Home Plus | 2727 | -$25 | |
LTE Home | 2729 | -$15 |
Stage | Who | Does What |
---|---|---|
1 | SLED Sales\xa0Representative | Confirms the customer\'s contract is amended to include eFax.
|
2 | Contract\xa0Management Team | Reviews BuSS request, and if approved forwards the request to the BFO to enable\xa0the customer profile for eFAX (based on contract availability). |
3 | BFO | Completes request, and replies all upon completion. |
4 | SLED Sales\xa0Representative | Works with the customer to complete the license order. |
5 | eFax | Activates the licenses and sends a welcome / get started email to the customer’s email sales\xa0entered in POS. |
sentence_0
, sentence_1
, and label
* Approximate statistics based on the first 1000 samples:
| | sentence_0 | sentence_1 | label |
|:--------|:-----------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------|:------------------------------------------------|
| type | string | string | int |
| details | What is the internal transfer number for Spanish HSI Tech Support for Consumer HSI?
| Context: CRTC. See Ordering a Return Label (ACSS) for more information.Refer to the return and exchange periods below (by purchase location): Returns Exchanges Note: For any exceptions to the return or exchange period, use the Blind Return flow process and remark the orders with: Original order number Location Reason for the exceptionDevice returns (not exchanges) reset the customer's contract and upgrade dates. Verizon requires a contract correction to: Verify all device returns. Reset the customer's contract and upgrade dates. When the date does not systematically correct, validate the: Device was returned. Customer requested a disconnect and returned to a previous device.Table: Purchase Location Return Period Verizon stores and Indirect locations | 0
|
| What is the time frame within which customers must call and request a return for a Stream TV device to be eligible for a refund from Verizon?
| Review the following guidelines before processing a device payment agreement: Canceling a device payment agreement erases all of the monthly installments the customer has paid towards a device. Example: If the customer has paid 3 payments, the bill is refunded for all 3 payments made. If the customer has made no payments, canceling a device payment agreement makes the agreement act like it never existed and the customer does not see it on the bill. In order to cancel a device payment agreement, verify the following: The status of the device payment agreement prior to requesting an agreement cancellation. Refer to the Loan Status Codes Grid for additional information. Device payment agreements in Paid status cannot be canceled. The device has been returned to a store or warehouse depending upon where the order was processed. If a store processed the order, verbally confirm the store has the device at the store location and attempted a return. If a direct fulfillment order, the customer ...
| 0
|
| Which SKU must be added to the order when placing an order for BuSS solutions?
| Context: multiple licenses, the page limits are aggregated. Faxing to international phone numbers is not available at this time.Ordering All solutions in the BuSS are billed on the Account Level. Customers may purchase BuSS solutions through these Verizon POS systems: B360 ACSS OMNI Retail OMNI Telesales Customers can mix and match licenses. When placing the order, the EFAX_OVERAGE SKU must be added to the order. Only 1 EFAX_OVERAGE SKU is required per account.Customer Payment Methods Retail, Retail SMB and Telesales B2B can only sell through Bill To Account (BTA). B2B and ACSS may sell through BTA and Purchasing Order (PO).Standard PricingTable: Stage Who Does What 1 Click to expand
- `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
### Training Logs
| Epoch | Step | Training Loss |
|:------:|:----:|:-------------:|
| 0.3808 | 500 | 0.1354 |
| 0.7616 | 1000 | 0.1184 |
| 1.1424 | 1500 | 0.1072 |
| 1.5232 | 2000 | 0.0968 |
| 1.9040 | 2500 | 0.095 |
| 2.2848 | 3000 | 0.0871 |
| 2.6657 | 3500 | 0.0832 |
### Framework Versions
- Python: 3.11.11
- 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",
}
```