Clarify an initiative: handover from sales to customer service
Fictional practice case: a request, an error log and the IT partner’s feedback become a project profile for clarification.
Situation
A fictional building services SME with around 60 employees sells maintenance contracts. Once signed, customer service takes over. Customer details are partly in the CRM, partly in sales e-mails. Information is regularly missing at handover; an external IT partner looks after the CRM.
Source material
«With new maintenance contracts we often lack the on-site contact, access arrangements and agreed start date. We then have to call the customer. Please suggest how we can improve the handover. Ideally we would start from spring.»
«23 new contracts. 9 without an on-site contact, 5 without a start date. The details were mostly in sales e-mails, not in the CRM.»
«Mandatory fields in the CRM form are possible. Automatically transferring details from e-mails is not part of the current support contract and would have to be quoted separately.»
Task for the AI
Create a project profile for clarification from the three sources. Separate documented facts from assumptions and cite the source for each statement. Do not invent costs, dates or responsibilities; mark anything missing as open.
Result: project profile for clarification (draft)
Reason and problem
- In four weeks, 9 of 23 new contracts lacked the on-site contact and 5 the start date (source 2).
- The details are mostly in sales e-mails rather than the CRM; customer service has to follow up (sources 1, 2).
Draft goal
- Every new maintenance contract is handed over to customer service in the CRM with on-site contact, access arrangements and start date.
- Measure: share of complete handovers. Target value open.
Stakeholders
- Sales records the details, customer service takes over the contract, the IT partner adapts the CRM, management issues the mandate and resources.
Scope and boundaries
- In scope: define mandatory details, adapt the CRM form, describe the handover process.
- Out of scope until decided: automatic transfer from e-mails (to be quoted separately, source 3).
Risks and dependencies
- Mandatory fields only help if sales knows the details at signing; otherwise placeholders appear.
- Depends on the IT partner’s capacity and quote.
Open decisions
- Which details are mandatory? Who owns the initiative? What budget is available? Is «from spring» a fixed date?
Next clarification steps
- Short alignment between sales and customer service on the list of mandatory details.
- Request effort estimate and quote from the IT partner.
- Discuss the profile with management and assign ownership.
Sources, assumptions and open information
- Sources
- E-mail from the head of customer service, error log of the last four weeks, feedback from the IT partner.
- Assumptions
- The four weeks are typical of the usual situation. Sales knows the missing details at signing.
- Still open
- Target value, budget, project ownership, binding start date, IT partner’s effort.
What people review and decide
Management and the head of customer service review the profile, assign ownership and decide on scope and resources. The AI has decided none of this.
Benefit in this situation
A vague request becomes a basis for discussion: the problem is backed by figures, the scope is defined and the open decisions are named.
