- Partner model additions
- menu changes to allow for partners - partner views and forms now in partner_forms.py and partner_views.py - Introduction of services layer - Allow all configuration to handle partner configurations, and adaptation of caching to allow for this
This commit is contained in:
35
config/tasks/global/EMAIL_LEAD_DRAFTING_TASK/1.0.0.yaml
Normal file
35
config/tasks/global/EMAIL_LEAD_DRAFTING_TASK/1.0.0.yaml
Normal file
@@ -0,0 +1,35 @@
|
||||
version: "1.0.0"
|
||||
name: "Email Lead Draft Creation"
|
||||
task_description: >
|
||||
Craft a highly personalized email using the lead's name, job title, company information, and any relevant personal or
|
||||
company achievements when available. The email should speak directly to the lead's interests and the needs
|
||||
of their company.
|
||||
This mail is the consequence of a first conversation. You have information available from that conversation in the
|
||||
- SPIN-context (in between triple %)
|
||||
- personal and company information (in between triple $)
|
||||
Information might be missing however, as it might not be gathered in that first conversation.
|
||||
Don't use any salutations or closing remarks, nor too complex sentences.
|
||||
|
||||
Our Company and Product:
|
||||
- Company Name: {company}
|
||||
- Products: {products}
|
||||
- Product information: {product_information}
|
||||
|
||||
{customer_role}'s Identification:
|
||||
$$${Identification}$$$
|
||||
|
||||
SPIN context:
|
||||
%%%{SPIN}%%%
|
||||
|
||||
{custom_description}
|
||||
expected_output: >
|
||||
A personalized email draft that:
|
||||
- Addresses the lead by name
|
||||
- Acknowledges their role and company
|
||||
- Highlights how {company} can meet their specific needs or interests
|
||||
{customer_expected_output}
|
||||
metadata:
|
||||
author: "Josako"
|
||||
date_added: "2025-01-08"
|
||||
description: "Email Drafting Task towards a Lead"
|
||||
changes: "Initial version"
|
||||
Reference in New Issue
Block a user