Dispatch Request Received Message Sample Clauses

Dispatch Request Received Message. This message simply acknowledges that RideIntegrity or one of the Dispatch Services has received a dispatch request message. It says nothing about the final disposition of the dispatch itself, which probably has not yet been decided in any event. If the recipient can’t process the request for some reason, the dispatch request received message specifies an appropriate error code. Message Fields Dispatch request id The reference number (unique id) that was sent by the Online Dispatch Referral Company in the original dispatch request message. Recipient Entity that originally sent the message. This can be either RideIntegrity itself or one of the Dispatch Services. The same message is used to acknowledge receipt of the dispatch request along the entire path. Error code Error, if any, for instance:  Success (that is, “no error”)  The original request was inconsistent or incomplete; request canceled  There was an error trying to forward the request to a Dispatch Service  Dispatch Service reports some other error to be determined
Sample 1
AutoNDA by SimpleDocs

Related to Dispatch Request Received Message

  • Alerts via Text Message To stop alerts via text message, text "STOP" to 27798 at any time. Alerts sent to your primary email address will be unaffected by this action. To restore alerts on your mobile phone, just visit the alerts tab in the Software. For help with SMS text alerts, text “HELP” to 27798. In case of questions please contact customer service at 000-000-0000. Our participating carriers include (but are not limited to) AT&T, T-Mobile®, U.S. Cellular®, Verizon Wireless, MetroPCS.

  • ODUF Message to be Transmitted 6.1.1 The following messages recorded by BellSouth will be transmitted to Quality Telephone: - Message recording for per use/per activation type services (examples: Three Way Calling, Verify, Interrupt, Call Return, etc.) - Measured billable Local - Directory Assistance messages - IntraLATA Toll - WATS and 800 Service - N11 - Information Service Provider Messages - Operator Services Messages - Credit/Cancel Records - Usage for Voice Mail Message Service

  • BONA FIDE REQUEST PROCESS 42.1. Embarq shall promptly consider and analyze CLEC requests for unbundled Network Elements that are not currently developed by Embarq, network information that is reasonably required to determine what unbundled Network Elements it needs to serve a particular customer or development of and changes to Embarq work processes related to ordering, provisioning or installation of unbundled Network Elements with the submission of a Bona Fide Request (“BFR”) hereunder.

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

  • TEXT MESSAGING WHILE DRIVING In accordance with Executive Order (EO) 13513, “Federal Leadership on Reducing Text Messaging While Driving,” any and all text messaging by Federal employees is banned: a) while driving a Government owned vehicle (GOV) or driving a privately owned vehicle (POV) while on official Government business; or b) using any electronic equipment supplied by the Government when driving any vehicle at any time. All cooperators, their employees, volunteers, and contractors are encouraged to adopt and enforce policies that ban text messaging when driving company owned, leased or rented vehicles, POVs or GOVs when driving while on official Government business or when performing any work for or on behalf of the Government.

  • Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process.

  • Reducing Text Messaging While Driving Pursuant to Executive Order 13513, 74 FR 51225 (Oct. 6, 2009), Recipient should encourage its employees, subrecipients, and contractors to adopt and enforce policies that ban text messaging while driving, and Recipient should establish workplace safety policies to decrease accidents caused by distracted drivers.

  • Text Messages ACM allows up to 4 contacts per Supplier to receive daily Milk quality results. Quality Results Zero indicates no result available for a particular test ie: Bacto. Refer to Milk Quality Index 3 for details of testing schedule. Legend

  • Bona Fide Request (BFR) The process described in the UNE Attachment that prescribes the terms and conditions relating to a Party's request that the other Party provides a UNE that it is not otherwise required to provide under the terms of this Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!