Autotask Toolkit

v 2.13.2 PROD

Global roll-out stage 2 - adding video Implemented

📁 SharePoint-folder

Status
Implemented
Stage
Stage 6 - Handover
Win reason
Klant
Acolad Netherlands B.V. (1181KK121)
Aangemaakt
2024-06-10
Gesloten
2024-06-17

Beschrijving

Uitleveren: 64 uur Software enginering 8 uur Project management Maandelijkse kosten: ACS Applicatie kosten €105 per maand,- Kosten schatting maandelijks verbruik €3000,- Akkoord van Richard om 100% achteraf te doen zie sharepoint Specifications for the new call-flow, based on the meeting yesterday with the TS devs: - TS will be developing the web based video UI for both the vendor and the customer (as I understand it no App based video calls will be used for this iteration) - Since the video call will be on a 'reserved' basis, the process of actually booking the reserved job, confirming both the customer and the vendor will be in the AL platform - We discussed that for this iteraion we will not need to consider the reservation like we do on the Avaya platform (where we actually check the timeslot and allow/disallow the call based on that, etc.). As such it is still very much an ad-hoc job except; • The start of the call needs to be controlled by ACS and not by the customer (as is the case with the ad-hoc flow) • There will be no vendor searching like with the ad-hoc flow, but instead the vendor is already found/decided and available (this will all be handled in the AL platform for now) • Both the customer and the vendor have a differnt UI with only an option to 'join' a video call • This is also where the AL platform will control the allow/disallow of the call based on the reservation • Only when both the customer and the vendor have actually requested to 'join' the call will ACS connect them and start the actual call • There is a need for a new API endpoint to facilitate the 'join' call instead of the current 'start' call • The new API endpoint will also provide additional context for the call: ? which participant actually pressed 'join' so we can monitor the participants correctly ? type of call (voice/video/...) ? type of conference or multiplicty needed (1:1 or 1:n for conference call) - There will be no conference calls in this iteration, but the process/call flow can be expanded to include conference calls as the working principle is the same and we have designed the API with this in mind - There will be no PSTN in this iteration, no incoming or outgoing nor fallback to callcenter (no requirement) Estimated hours needed: - 64 hours for the development of the actual ACS call flow (€7360) - 8 hours project management for meetings etc. (€1000) > Not including additional hours for supporting TS (we assume none or just a minimal amount of support is needed) Hosting fees apply as well: - ACS application costs = €105 MRC - Call costs estimate/example: 1000 video calls per week, 15 minutes each between customer and vendor: 15min * 1000calls * 2participants *4weeks = €2200 MRC

Primary quote

Naam
#1574 — Global roll-out stage 2 - adding video
Effectief vanaf
2024-06-09
Vervaldatum
2024-07-10

Estimated hours needed: - 64 hours for the development of the actual ACS call flow (€7360) - 8 hours project management for meetings etc. (€1000) > Not including additional hours for supporting TS (we assume none or just a minimal amount of support is needed) Hosting fees apply as well: - ACS application costs = €105 MRC - Call costs estimate/example: 1000 video calls per week, 15 minutes each between customer and vendor: 15min * 1000calls * 2participants *4weeks = €2200 MRC

Maandelijkse items (2)

# Artikel of dienst Item type Aantal
1 ACS Application costs
ACS Application costs
Product 7
2 Schatting verbruik per maand
ACS Application costs
Product 7

Eenmalige items (2)

# Artikel of dienst Item type Aantal
1 Software Engineer [project]
Software engineer
Labor 64
2 Project Management
Project management
Labor 8

Notes (9)

Datum Action type Assigned to Onderwerp / inhoud
2024-06-17 Opportunity Update Erik Gunther Opportunity: None, Global roll-out stage 2 - adding video Total Revenue=30095 Probability=100% Sales Stage=Stage 6 - Handover Projected Close Date=17-06-2024 Changed Opportunity Owner from Hammel, David to Gunther, Erik Status=Closed
2024-06-17 General David Hammel Workflow Rule "[TSV-Opp Stage6] Losse opdracht ready for handover - notify support team" fired.
When an opportunity is: Edited And the following conditions are met: Opportunity Category in list "Losse opdracht or TPS Orderbevestiging" Stage changed to "Stage 6 - Handover" Then execute the following actions: Send notification e-mail ([TSV-Opportunity] Losse opdracht - Stage 6 Handover) to akik@tsv-groep.nl; bsyed@tsv-groep.nl; flunstroo@tsv-groep.nl Initiated by Erik Gunther
2024-06-17 General David Hammel Workflow Rule "[TSV-Opp Stage6] Opportunity ready for handover - notify project team" fired.
When an opportunity is: Edited And the following conditions are met: Opportunity Category in list "Losse opdracht or Project or Standaard (projecten)" Stage changed to "Stage 6 - Handover" Then execute the following actions: Send notification e-mail ([TSV-Opportunity] Project - Stage 6 Handover) to akik@tsv-groep.nl; bsyed@tsv-groep.nl; flunstroo@tsv-groep.nl Initiated by Erik Gunther
2024-06-17 Opportunity Update Erik Gunther Opportunity: None, Global roll-out stage 2 - adding video Total Revenue=30095 Probability=100% Changed Status from Stage 5 Closed - WON to Stage 6 - Handover Changed Projected Close Date from 01-07-2024 to 17-06-2024 Opportunity Owner=Hammel, David Changed Status from Active to Closed
2024-06-17 General David Hammel Workflow Rule "[TSV-Opp WON] Opportunity closed & WON - notify RE for KP" fired.
When an opportunity is: Edited And the following conditions are met: Opportunity Category in list "Losse opdracht or Project or Standaard (projecten) or TPS Orderbevestiging" Stage changed to "Stage 5 Closed - WON" Then execute the following actions: Send notification e-mail ([TSV-Opportunity] Opportunity - Stage 5 Closed (WON) aanmaken kostenplaats) to flunstroo@tsv-groep.nl; revers@tsv-groep.nl Initiated by Erik Gunther
2024-06-17 Opportunity Update Erik Gunther Opportunity: None, Global roll-out stage 2 - adding video Total Revenue=8360 Changed Probability from 25% to 100% Changed Status from Stage 3 Proposal Sent to Stage 5 Closed - WON Projected Close Date=01-07-2024 Opportunity Owner=Hammel, David Status=Active
2024-06-14 Opportunity Update Erik Gunther Opportunity: None, Global roll-out stage 2 - adding video Total Revenue=8360 Probability=25% Changed Status from Stage 1 First Contact to Stage 3 Proposal Sent Projected Close Date=01-07-2024 Opportunity Owner=Hammel, David Status=Active
2024-06-10 Opportunity Update David Hammel Opportunity: None, Global roll-out stage 2 - adding video Total Revenue=0 Probability=25% Sales Stage=Stage 1 First Contact Projected Close Date=01-07-2024 Opportunity Owner=Hammel, David Status=Active
2024-06-10 Opportunity Update David Hammel New Opportunity: None, Global roll-out stage 2 - adding video Total Revenue=0 Probability=25% Sales Stage=Stage 1 First Contact Projected Close Date=01-07-2024 Opportunity Owner=Hammel, David Status=Active
Volledige record uit Autotask
{
  "advancedField1": 0.0,
  "advancedField2": 0.0,
  "advancedField3": 0.0,
  "advancedField4": 0.0,
  "advancedField5": 0.0,
  "amount": 30095.0,
  "assessmentScore": null,
  "barriers": "",
  "closedDate": "2024-06-17T00:00:00.000Z",
  "companyID": 923,
  "contactID": 30686055,
  "cost": 4680.0,
  "createDate": "2024-06-10T13:28:52.297Z",
  "creatorResourceID": 29682885,
  "description": "Uitleveren:\n64 uur Software enginering \n8 uur Project management\n\nMaandelijkse kosten:\nACS Applicatie kosten €105 per maand,-\nKosten schatting maandelijks verbruik €3000,-\n\nAkkoord van Richard om 100% achteraf te doen zie sharepoint\n\nSpecifications for the new call-flow, based on the meeting yesterday with the TS devs:\n- TS will be developing the web based video UI for both the vendor and the customer (as I understand it no App based video calls will be used for this iteration)\n- Since the video call will be on a 'reserved' basis, the process of actually booking the reserved job, confirming both the customer and the vendor will be in the AL platform\n- We discussed that for this iteraion we will not need to consider the reservation like we do on the Avaya platform (where we actually check the timeslot and allow/disallow the call based on that, etc.). As such it is still very much an ad-hoc job except;\n  • The start of the call needs to be controlled by ACS and not by the customer (as is the case with the ad-hoc flow)\n  • There will be no vendor searching like with the ad-hoc flow, but instead the vendor is already found/decided and available (this will all be handled in the AL platform for now)\n  • Both the customer and the vendor have a differnt UI with only an option to 'join' a video call\n  • This is also where the AL platform will control the allow/disallow of the call based on the reservation\n  • Only when both the customer and the vendor have actually requested to 'join' the call will ACS connect them and start the actual call\n  • There is a need for a new API endpoint to facilitate the 'join' call instead of the current 'start' call\n  • The new API endpoint will also provide additional context for the call:\n      ? which participant actually pressed 'join' so we can monitor the participants correctly\n      ? type of call (voice/video/...)\n      ? type of conference or multiplicty needed (1:1 or 1:n for conference call)\n- There will be no conference calls in this iteration, but the process/call flow can be expanded to include conference calls as the working principle is the same and we have designed the API with this in mind\n- There will be no PSTN in this iteration, no incoming or outgoing nor fallback to callcenter (no requirement)\n\nEstimated hours needed:\n- 64 hours for the development of the actual ACS call flow (€7360)\n- 8 hours project management for meetings etc. (€1000)\n> Not including additional hours for supporting TS (we assume none or just a minimal amount of support is needed)\n\nHosting fees apply as well:\n- ACS application costs = €105 MRC\n- Call costs estimate/example: 1000 video calls per week, 15 minutes each between customer and vendor: 15min * 1000calls * 2participants *4weeks = €2200 MRC",
  "helpNeeded": "",
  "id": 1811,
  "impersonatorCreatorResourceID": null,
  "lastActivity": "2024-06-17T14:51:33.493Z",
  "leadSource": null,
  "lossReason": null,
  "lossReasonDetail": "",
  "lostDate": null,
  "market": "",
  "monthlyCost": 0.0,
  "monthlyRevenue": 21735.0,
  "nextStep": "",
  "onetimeCost": 4680.0,
  "onetimeRevenue": 8360.0,
  "opportunityCategoryID": 105,
  "organizationalLevelAssociationID": null,
  "ownerResourceID": 29682927,
  "primaryCompetitor": null,
  "probability": 100,
  "productID": 2,
  "projectedCloseDate": "2024-06-17T00:00:00.000Z",
  "promisedFulfillmentDate": null,
  "promotionName": "",
  "quarterlyCost": 0.0,
  "quarterlyRevenue": 0.0,
  "rating": null,
  "relationshipAssessmentScore": null,
  "revenueSpread": 0,
  "revenueSpreadUnit": "",
  "salesOrderID": null,
  "salesProcessPercentComplete": null,
  "semiannualCost": 0.0,
  "semiannualRevenue": 0.0,
  "stage": 29682776,
  "startDate": "2024-06-10T00:00:00.000Z",
  "status": 4,
  "technicalAssessmentScore": null,
  "throughDate": null,
  "title": "Global roll-out stage 2 - adding video",
  "totalAmountMonths": 1,
  "useQuoteTotals": true,
  "userDefinedFields": [],
  "winReason": null,
  "winReasonDetail": "",
  "yearlyCost": 0.0,
  "yearlyRevenue": 0.0
}