terms_of_subcontractor_service
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| terms_of_subcontractor_service [2025/06/11 11:36] – thesaint | terms_of_subcontractor_service [2025/10/14 01:11] (current) – [16. Local Tech Engagement (REVISED RESTRAINT CLAUSE)] thesaint | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | **'' | + | **//see last modified date at base of all pages//** |
| {{: | {{: | ||
| Line 9: | Line 9: | ||
| SupportCALL (PTY) LTD. (hereafter referred to as **SupportCALL**)\\ | SupportCALL (PTY) LTD. (hereafter referred to as **SupportCALL**)\\ | ||
| - | **Please read the entire page.**\\ | + | **//Please read the entire page.//**\\ |
| **By using this site or the SupportCALL Ticket System, you agree to the terms outlined here and in any official communication from SupportCALL.** | **By using this site or the SupportCALL Ticket System, you agree to the terms outlined here and in any official communication from SupportCALL.** | ||
| Line 16: | Line 16: | ||
| === USE OF THIS SITE, SUPPORTCALL TICKET SYSTEM AND WORK HANDLING === | === USE OF THIS SITE, SUPPORTCALL TICKET SYSTEM AND WORK HANDLING === | ||
| - | * It is your responsibility to regularly check this page for updates. | + | * It is **your responsibility** to regularly |
| - | * By signing in, you act on behalf of your company/employer. | + | * By signing in, you act on behalf of your **company |
| - | * Subcontractor agrees to perform on-site and remote ICT services as instructed by SupportCALL (hardware, software, networking, cabling, PABX, biometrics, etc.). | + | |
| - | * Tasks flagged as " | + | * Tasks flagged as **" |
| - | * Tickets must be responded to ASAP, prioritizing according to user-set Priority Level. | + | |
| - | * Contact the end-user within 24 hours to gather additional info and schedule site visit. | + | |
| - | * Log the agreed visit date/time in the Ticket System. | + | |
| - | * All communication must go through the Ticket System. | + | * All **communication** must go through the **Ticket System**. |
| - | * Update tickets following the [[local_tech_field_report|standard reporting example]]. | + | |
| - | * Tickets must be updated | + | * Tickets must be **updated |
| - | * Use the **[Post Internal Note]** tab for all ticket communication. | + | * Use the **[Post Internal Note]** tab for all **ticket communication**. |
| - | * For physical work (e.g., cabling, moving hardware), always take before/ | + | * For **physical work** (e.g., cabling, moving hardware), always take **before/ |
| - | * Submit quotes for such work **before** | + | * Submit |
| - | * Upload photos to **[Post Internal Note]** tab, clearly labelled. | + | * Upload |
| - | * Photograph serial numbers of equipment at least every 3rd site visit (APs, repeaters, | + | * Photograph |
| + | * **APs** | ||
| + | * **Repeaters** | ||
| + | * **UPS** | ||
| + | * **Switches** | ||
| + | * **Firewalls** | ||
| + | * **etc.** | ||
| * Always set correct **Ticket Status**, **Time Spent**, and **Time Type**. | * Always set correct **Ticket Status**, **Time Spent**, and **Time Type**. | ||
| - | * Indicate whether time is billable or not. | + | * Indicate whether |
| - | * Work is performed at the agreed rate (confirm with SupportCALL if unsure). | + | * Work is performed at the **agreed rate** (**confirm** with **SupportCALL** if unsure). |
| - | * SupportCALL clients remain with SupportCALL—no bypass or independent client dealings. | + | * SupportCALL clients remain with **SupportCALL** — **no bypass** or **independent client dealings**. |
| - | * Only communicate directly with clients if instructed by SupportCALL. | + | * Only **communicate directly** with clients if instructed by **SupportCALL**. |
| - | * Prompt ticket updates allow SupportCALL to report to clients effectively. | + | |
| - | * Invoices must be submitted timely and accurately. Submit by the **25th** of each month. | + | |
| - | * Payment is made within 30 days of SupportCALL receiving client payment. | + | |
| - | * Consolidating tickets onto one invoice without prior approval may cause delays. | + | |
| - | * You may not retain or use any data/ | + | * One Ticket, one invoice. |
| - | * After termination, | + | * You may **not retain or use any data/ |
| - | * ALL jobs must be assigned via the SupportCALL Ticket System. | + | * After **termination**, no contact with **LOCAL TECHs**, **clients**, or **staff** for at least **10 years**, unless formally |
| - | * Delete all client data from your systems upon call completion or within 3 months. | + | |
| - | * Maintain professionalism and quality at all times. | + | |
| - | * Treat end-users respectfully—as SupportCALL representatives. | + | * Maintain |
| - | * All work must follow SupportCALL/ | + | * Treat **end-users respectfully** — as **SupportCALL representatives**. |
| - | * Maintain detailed logs and submit complete reports. | + | * All work must follow |
| - | * Always confirm resolve with client HQ. | + | * Maintain |
| - | * Quotes are required for **all** cabling work—include ticket reference in the quote. | + | * Always |
| - | * Use the field report format as per [[local_tech_field_report|this example]]. | + | |
| - | * Attach BEFORE and AFTER photos to ticket **INTERNAL NOTES**, clearly labelled. | + | * Use the **field report format** as per [[local_tech_field_report|**this example**]]. |
| - | * Invoicing: | + | * Attach |
| - | * One invoice per ticket. | + | |
| - | * Reference ticket number. | + | * One **invoice per ticket**. |
| - | * Mark clearly as " | + | * Reference |
| - | * Ensure tickets are separate per issue/ | + | * Mark clearly as **" |
| + | * Ensure | ||
| === SERVICE LEVELS === | === SERVICE LEVELS === | ||
| Line 64: | Line 71: | ||
| * Low: Contact within 24 hours, onsite within 48 business hours. | * Low: Contact within 24 hours, onsite within 48 business hours. | ||
| * Failure to meet SLAs may result in review or penalties. | * Failure to meet SLAs may result in review or penalties. | ||
| + | * Unless otherwise agreed | ||
| === PRIORITY === | === PRIORITY === | ||
| Line 84: | Line 92: | ||
| * No client data may be kept, shared, or used outside SupportCALL-authorized purposes. | * No client data may be kept, shared, or used outside SupportCALL-authorized purposes. | ||
| - | === LIABILITY AND INDEMNIFICATION | + | ===== 11. Governing Law ===== |
| - | * Subcontractor holds SupportCALL harmless against: | + | **11.1.** These Terms of Use shall be governed by and construed in accordance with the laws of the **SupportCALL entity** that is the contracting |
| - | | + | **11.2.** If the contracting party is **SupportCALL |
| - | | + | **11.3.** If the contracting party is **SupportCALL (Australia) Pty Ltd** (or equivalent Australian entity), the governing law will be the laws of the **State/ |
| - | | + | **11.4.** By entering into this Agreement, you irrevocably submit to the exclusive jurisdiction of the Courts of the applicable Governing Law jurisdiction. |
| - | * Must maintain suitable insurance | + | |
| - | === DISPUTE | + | ===== 12. Liability and Indemnification ===== |
| + | **12.1. Subcontractor Liability: | ||
| + | **12.2. Indemnification: | ||
| + | **12.3. Insurance: | ||
| + | **12.4. Limitation of Liability to Subcontractor: | ||
| + | |||
| + | ===== 13. Dispute ===== | ||
| * Disputes remain between SupportCALL and the subcontractor only. | * Disputes remain between SupportCALL and the subcontractor only. | ||
| * Refer disputes to senior executives first. | * Refer disputes to senior executives first. | ||
| * If unresolved in 7 days, it moves to arbitration. | * If unresolved in 7 days, it moves to arbitration. | ||
| * Arbitration is final, binding, enforceable by High Court. | * Arbitration is final, binding, enforceable by High Court. | ||
| - | * South African law applies. | + | * **The arbitration will be governed by the laws determined under Clause 11.** |
| - | === TERM AND TERMINATION | + | ===== 14. Modification of Terms ===== |
| + | **14.1.** SupportCALL reserves the right to modify these Terms of Service from time to time to reflect changes in our business practices or legal and regulatory requirements.\\ | ||
| + | **14.2. Minor Changes:** For minor, non-material changes (e.g., correcting typos, adding contact information, | ||
| + | **14.3. Material Changes & Notice:** If a change is deemed **Material** (including, but not limited to, changes to payment terms, the scope of the Restrictive Covenant, or the Liability provisions), | ||
| + | * **(a) System Notification: | ||
| + | * **(b) Login Screen Banner:** A non-dismissible notice or banner placed on the Ticket System login page.\\ | ||
| + | **14.4. Acceptance: | ||
| + | |||
| + | ===== 15. Term and Termination ===== | ||
| * Agreement begins upon first login and remains until terminated. | * Agreement begins upon first login and remains until terminated. | ||
| * Either party may terminate with 30 days' written notice. | * Either party may terminate with 30 days' written notice. | ||
| - | * SupportCALL may terminate immediately for serious breaches. | + | * SupportCALL may terminate immediately for serious breaches |
| + | |||
| + | ===== 16. Local Tech Engagement ===== | ||
| + | **16.1. Prohibition on Bypassing SupportCALL: | ||
| + | **16.2. Post-Termination Non-Solicitation (Restrictive Covenant): | ||
| + | **16.3. Duration:** This restriction remains in force for a minimum period of **12 months** following the termination of this Agreement **or any SupportCALL services.**\\ | ||
| + | **16.4. No Poaching:** The Subcontractor agrees not to solicit, entice, or poach any **LOCAL TECHs, subcontractors, | ||
| + | **16.5. Enforcement: | ||
| - | === SEVERABILITY | + | ===== 17. Severability ===== |
| * If any clause is invalid, the rest remain effective. | * If any clause is invalid, the rest remain effective. | ||
| === NOTE === | === NOTE === | ||
| - | * Work must be instructed by SupportCALL or client HQ (visible in ticket). | + | * Work must be instructed by SupportCALL or client HQ (and must be visible in ticket). |
| * End-user requests go through HQ. | * End-user requests go through HQ. | ||
| * Keep end-users happy—this builds lasting client trust. | * Keep end-users happy—this builds lasting client trust. | ||
| Line 120: | Line 148: | ||
| * Always use **[Post Internal Note]** for updates. | * Always use **[Post Internal Note]** for updates. | ||
| * Use XnConvert to resize photos before upload/ | * Use XnConvert to resize photos before upload/ | ||
| - | * Use the correct config — [[http:// | + | * Use the correct config — [[http:// |
| + | * Use the correct config — [[http:// | ||
| + | * If any issues downloading, | ||
| * Be punctual or communicate delays. | * Be punctual or communicate delays. | ||
| * **Always take BEFORE & AFTER photos.** | * **Always take BEFORE & AFTER photos.** | ||
terms_of_subcontractor_service.1749641768.txt.gz · Last modified: by thesaint
