<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><p><strong>In this guide we will cover:</strong></p><p><strong>- </strong><strong>View Pane</strong></p><p><strong>- </strong><strong>Areas</strong></p><p><strong>- Opportunity List</strong></p><p><strong>- Raising Opportunities</strong></p><p><strong>- Field List</strong></p><p><strong>- Copying Custom Fields from the Ticket to the New Customer Record</strong></p><p><br></p><p><br></p><p><strong>Admin Guides:</strong></p><ul><li><a href="https://usehalo.com/halopsa/guides/1814/" rel="noopener noreferrer" target="_blank"><strong>Ticket Areas</strong></a></li><li><a href="https://usehalo.com/halopsa/guides/1856/" rel="noopener noreferrer" target="_blank"><strong>Sales Views</strong></a></li></ul><p><strong><br></strong></p><p><strong>Related Guides:</strong></p><ul><li><a href="https://usehalo.com/halopsa/guides/1937/" rel="noopener noreferrer" target="_blank"><strong>Ticket/Client Areas</strong></a></li><li><a href="https://usehalo.com/halopsa/guides/1934/" rel="noopener noreferrer" target="_blank"><strong>Lists</strong></a></li><li><a href="https://usehalo.com/halopsa/guides/1933/" rel="noopener noreferrer" target="_blank"><strong>Views</strong></a></li></ul><p><strong><br></strong></p><p id="isPasted">In this guide we're going to look at raising a new opportunity, while bringing together various different areas of configuration to see how the CRM module can be customised to suit your needs. Heading into our CRM module, were presented with a screen similar to that of the Service Desk module. Let's break this down into two section: the 'View' pane and Opportunity list.</p><p><br></p><p><strong><span style="color: rgb(0, 0, 0); font-size: 14pt;">View Pane</span></strong></p><p>When heading into the CRM module, the view pane is displayed on the left hand side.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjlkNThiMTkyLTA2ZjUtNDExNi1hZjNiLTIxMTE5NjhkMTVmYyJ9.KQg1L4pgfD3IwlLLQOB4x2tWOSy4K1t0o26Z0w5PwJA" class="fr-fic fr-fil fr-dib" width="337" height="509"></p><p><strong><span style="font-size: 10pt;">Fig 1. The View Pane</span></strong></p><p><br></p><p>The default view here is currently set to 'My Lists'. To change the default view, go to Configuration > Sales > Views.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImUwMDVhYzllLTI3NTUtNGI1Yi1hZjMwLTRhZDY5M2IwNmNiMSJ9.Cm-mVXmB9eYAML1ua2VXMz5keD710w9iBkXwQgmbLHk" class="fr-fic fr-fil fr-dib" width="451" height="405"></p><p><strong><span style="font-size: 10pt;">Fig 2. Default viewing options</span></strong></p><p><br></p><p>You'll note in <strong>Fig 2</strong> that these options can be overridden via editing agent preferences (Configuration > Teams & Agents > *Click into an agent* > *Preferences Tab*).</p><p><br></p><p><strong><span style="font-size: 14pt;">Areas</span></strong></p><p><span style="font-size: 11pt;">In</span><strong><span style="font-size: 11pt;"> </span></strong>Configuration > Tickets > Ticket Areas you can configure the areas which are displayed in the navigation bar pinned to the left hand side of the screen. Within the details tab you can set a default view per area. For more information on ticket areas checkout the admin guide and the other guide on ticket areas linked at the top of this article.</p><p><br></p><p><strong>Tip</strong>: While you can set default viewing options for your Service Desk, Projects and CRM areas, you can always change these ad-hoc by simply clicking on the view, where you'll then be prompted to select the view you want to make use of on this occasion:</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY3YWQ3MGI3LTU4YWYtNDVjZS05NDMzLTFmZWE5ZjM1YWUxZiJ9.wnX1f2aqbFeqSp9YvbLDCd86gqiwt2gjPtyYlPRWnMQ" class="fr-fic fr-fil fr-dib" width="253" height="404"></p><p><strong><span style="font-size: 10pt;">Fig 3. Viewing Options</span></strong></p><p><br></p><p><strong><span style="color: rgb(0, 0, 0); font-size: 14pt;">Opportunity List</span></strong></p><p>To the right of the view pane is the opportunity list, note that "Conversion Probability" has been changed to Probability on this column profile:</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImU5ZmE1MTEzLTBjM2UtNDI0NS05NWYwLTgzYjJjY2JmMjg4YiJ9.IS5TWGZg_n5-5jQmlDyQSdaGZfbY7XUuipS3vJuT27k" class="fr-fic fr-fil fr-dib" width="979" style="width: 981px; height: 193.748px;" height="194"></p><p><strong><span style="font-size: 10pt;">Fig 4. The Opportunity List</span></strong></p><p><br></p><p>This will display a list of opportunities based on the relevant view/filter profile, and will present opportunity information based on the respective column profile applied. All of these options can again be defaulted either via heading to Configuration > Sales > Views, or by modifying the relevant agent preferences.</p><p><br></p><p><strong><em>Note: An Additional Way to View Tickets by Status: You'll see in the top right hand side of the screen the option to raise a new Opportunity ('New') & additional viewing options ('...'). Clicking our additional viewing options and selecting Kanban will list our Opportunities based on their status:</em></strong></p><p><br></p><p>If using Kanban view, you may wish to add variables into this in the Configuration > Sales > Views > Configure Column Profile > Kanban Card Layout dropdown. Available variables can be viewed via your instance URL with"/variables" at the end. These can then be added into the formatting/HTML.</p><p><br></p><p>Some useful variables you may want to use are:</p><p><br></p><ul><li>$-OPPCOMPANYNAME - Name of the company.</li><li>$-OPPCONTACTNAME - Contact name from the company.</li><li>$-OPPCONVERSIONPROBABILITY - Conversion probability.</li><li>$-OPPVALUE - Value.</li><li>$-OPPVALUEANNUAL - Annual value.</li><li>$-OPPVALUEMONTHLY - Monthly value.</li><li>$-OPPVALUEONEOFF - One-off value.</li></ul><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjZlNTEyZTMzLWUzNzYtNGQ4NS04NGJhLWQ5NDJhNjdlZWNlNiJ9.XYILaqUKIcpG0AsoFXIPbcU9oN3VGjdORyTQCoKC0ys" class="fr-fic fr-fil fr-dib" width="868" height="567"></p><p><strong><span style="font-size: 10pt;">Fig 5. Opportunities displayed as per Kanban</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Raising Opportunities</span></strong></p><p>Clicking 'New' (top right hand side) of the CRM module will open the new Opportunity screen. This screen can be broken into two sections: Contact details & Opportunity form.</p><p><br></p><p><strong><span style="color: rgb(0, 0, 0); font-size: 12pt;">Contact Details</span></strong></p><p>This is where you input the contact details pertaining to the opportunity. Either select 'Existing Customer' to search your list of End-Users, or 'New Contact' to manually enter details against a company/end-user that does not currently exist.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImJmNjBmZjcwLWQ2NDUtNGQ4OC04ZjYyLWM4ZDdjYjBhODMyMyJ9.k7HLR8btt1b2EHt4AdjmKPGOjtOeI8nj8b8I4lPuUe0" class="fr-fic fr-fil fr-dib" width="380" height="568"></p><p><strong><span style="font-size: 10pt;">Fig 6. Contact details section of the new opportunity screen</span></strong></p><p><br></p><p><strong><span style="color: rgb(0, 0, 0); font-size: 12pt;">Opportunity Form</span></strong></p><p>This is where you fill out the main details of the opportunity and it is composed of the fields with your Field List for the relevant opportunity type. In our example opportunity type, dynamic field visibility has been applied to include additional fields based on the selection of "what kind of opportunity is this?" (<strong>Fig 7</strong>):</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjFlMDliNDdhLWRkYTUtNDA0MC1iOTI5LTEwODlmY2E0MzI5MyJ9.V3JWkbmStar0TcItPHMPb4hGhryIh3ET8-W60XzUAio" class="fr-fic fr-fil fr-dib" width="971" style="width: 973px; height: 572.548px;" height="573"></p><p><strong><span style="font-size: 10pt;">Fig 7. Opportunity Form</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Field List</span></strong></p><p><strong>Fig 7</strong> is a screenshot of the Opportunity form returned when raising our type 'Opportunity' (<strong>Fig 6</strong>), so we will need to head to the configuration of this opportunity type to see our configured field list. Heading to Configuration > Sales > Opportunity Types > Opportunity, and then into the Field List tab, we find the below fields.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY1NGY1ZjExLWQzOGItNGEwMi1iYjczLTE3NGVjODU2NGJiNiJ9.rvYR-yr1Nn180ggSz1wn1G5HLpgludltS7wuJvi3hV8" class="fr-fic fr-fil fr-dib" width="981" style="width: 983px; height: 893.789px;" height="894"></p><p><strong><span style="font-size: 10pt;">Fig 8. Field List for ticket type 'Opportunity'</span></strong></p><p><br></p><p><strong><span style="font-size: 12pt;">Dynamic Field Visibility</span></strong></p><p>Clicking the pencil on 'How many employees?' and scrolling down, we will see Dynamic field visibility has been imposed:</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjFmNTFkMzBmLWY1NzQtNDVkYS04Y2NlLTJiYjEzOGMwOTI2MCJ9.3PCzOf-RNCgRhBBYhaLN1B3cia0ahHC_PVCBs-haTSY" class="fr-fic fr-fil fr-dib" width="565" height="485"></p><p><strong><span style="font-size: 10pt;">Fig 9. Dynamic Field Visibility imposed on our opportunity field</span></strong></p><p><br></p><p>This means that this field will only be displayed if the selection of 'What kind of opportunity is this?' is 'New Managed Service' or 'Training':</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImJkNmE0YTA5LTU1Y2ItNDUyMi04OWU4LTU3Njc5YmMyNjAxNiJ9.-6DF1O-JyRCGsKpjVXu1pQnY50qgG99Z2gFxlifITvU" class="fr-fic fr-fil fr-dib" width="992" style="width: 994px; height: 224.179px;" height="224"></p><p><strong><span style="font-size: 10pt;">Fig 10. Dynamic field visibility (compare with Fig 7.)</span></strong></p><p><br></p><p>There are many types of fields to add to the list, you can also configure different actions with fields on them, to create custom fields, checkout the Custom Objects Section.</p><p><br></p><p>Sales tickets can also be made billable in the same way regular tickets are (Configuration > Billing > Labor & Travel > "Allow time on Sales Opportunities to be Invoiced"). If enabled, the "Charge Type" field can be added to the field list of an action, then the ticket billed from the "Labour" section of Ready for Invoicing.</p><p><br></p><p><strong><span style="font-size: 14pt;">Copying Custom Fields from the Opportunity Ticket of a New Customer, onto the New Customer Record </span></strong></p><p>Copying Custom Fields from the opportunity ticket into the new customers record. In order to copy over the custom fields that exist on the ticket, you must create a custom field of entity ticket, and a custom field of entity customer. The label on both entities must be the same.</p><p><br></p><p>For the customer entity:</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQ3MTc4ODBlLWM2NjEtNGU3Zi04NmE2LTczMTg5YTAyNDA2MSJ9.2jyB5r6Jg_TGMHzF0Ow3JLUWXnb05OgmQ1j1EVfJwSI" class="fr-fic fr-fil fr-dib" width="735" height="271"></p><p><strong><span style="font-size: 10pt;">Fig 11. Custom Field of entity 'Customer'</span></strong></p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjhlNjc3YmI3LTg1ZTUtNGQ2Ny1iYTAxLTg3ZmFhMDlmZGVlNSJ9.C3eO_Rb84JnwGtYphs2IWfjfQzNVVTUktxNY0PmLynY" class="fr-fic fr-fil fr-dib" width="537" height="361"></p><p><span style="font-size: 10pt;"><strong>Fig 12. Field Label in the custom field</strong></span></p><p><br></p><p>Then when you create the field in the ticket entity, you must also use the same label. This is how the system knows to copy over the field to the new customer template:</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQzNDk2NjZlLWE2YTAtNDM5My04YjI5LWM3ZWU4NmJiZmRjMyJ9.JRN9vSgVfMHTElALi1tYewkANFMit1W-O9PpPD6so5c" class="fr-fic fr-fil fr-dib" width="696" height="248"></p><p><strong><span style="font-size: 10pt;">Fig 13. The same Field Label on a different custom field</span></strong></p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQ2MWM5MTlhLTE1ZDEtNDM3NS04OTA5LTg1YmIyYzk1ZjYxNiJ9.oFoNZBmV0p-WGyv0uFR4gxtLWVnfBV2xgqqxwy7mQmY" class="fr-fic fr-fil fr-dib" width="426" height="283"></p><p><strong><span style="font-size: 10pt;">Fig 14. The Field Label on that other field</span></strong></p><p><br></p><p>As long as the data types are compatible ("Type of field" set on the custom field) you will be able to pull the data into the corresponding custom field entity, granted that the custom field on the ticket has been populated. Now when creating a new customer from an opportunity ticket, my ticket entity custom field with field label: "How many employees?" will populate on the custom fields tab of my new customer (To gain an understanding of custom fields, please refer to the<strong> </strong><a href="https://usehalo.com/halopsa/guides/2039" rel="noopener noreferrer" target="_blank"><strong>custom objects course</strong></a>).</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImE3ZmViNWUzLTdmYTUtNGVhMS04MzdmLWZlMDY3YzdhMDkwOSJ9.iUkcXRXLzRMggYLGmWR6NupOxMSuFYFwxj8Wew6fmXo" class="fr-fic fr-fil fr-dib" width="567" height="708"></p><p><strong><span style="font-size: 10pt;">Fig 15. Create a new Customer from this Opportunity</span></strong></p><p><br></p><p>The custom field will now appear.</p><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijc3OTc2ZGY4LTFhODUtNDhlZi04NjdhLWIzZTM0YmY4ZDBjZSJ9.iFgiWD0S-ohSnRz0kSMzSI2sPQhm9i9nKF5r-tBhxPE" class="fr-fic fr-fil fr-dib" width="947" height="409"></p><p><span style="font-size: 10pt;"><strong>Fig 16. The field on the new customer</strong></span></p><p><br></p><p>This can be very useful for categorising customers and copying over sales data that was gathered during the sales process. Some example fields you may want to capture are:</p><p><br></p><ul><li>How were they managing their IT previously? (Single Select Custom Field)</li><li>How many employees do they have? (Text Custom Field)</li><li>What Industry are they in? (Text or Single Select Custom Field)</li><li>What Type of Client are they i.e. Contract, PAYG, etc... (Single Select Custom Field)</li></ul>
