Welcome To The X2Workflow In-Depth User Manual


menu accompaniment image - 01.02

TABLE OF CONTENTS


 

Triggers

Triggers mark the start of your flow. These are the events that signal to your X2CRM system to begin some type of automated behavior. Triggers can be limited by attribute filters, limited to what type of module the flow trigger is based on. For example, the Action Completed flow trigger will allow you to filter based on Action relatedattributes, like Due Date. Standard trigger types include a wide variety of events in X2CRM, and can be further specified and filtered to include almost every type of event that X2CRM can produce.          

flow triggers - action completed


Action Completed

This flow triggers whenever an action is completed by a member of your X2CRM system (i.e. a user). Attribute fields related to the action module in X2CRM are valid as attribute filters. Choose the attribute fields from the dropdown menu, then add them and set your specific parameter requirements. In addition, you can set additional filters based on general variables (e.g. current month or day of week, which user is logged in, et cetera).

flow triggers - action overdue


Action Overdue

This flow triggers whenever an action becomes overdue. Specify the amount of time an action must be overdue in order to set off this trigger. Attribute fields related to the action module in X2CRM are valid as attribute filters. Choose the attribute fields from the dropdown menu, then add them and set your specific parameter requirements. In addition, you can set additional filters based on general variables (e.g. current month or day of week, which user is logged in, et cetera).

flow triggers - action marked incomplete


Action Marked Incomplete

This flow triggers whenever an action is marked as incomplete by a member of your X2CRM system (i.e. a user). Attribute fields related to the action module in X2CRM are valid as attribute filters. Choose the attribute fields from the dropdown menu, then add them and set your specific parameter requirements. In addition, you can set additional filters based on general variables (e.g. current month or day of week, which user is logged in, et cetera).

flow triggers - campaign email clicked


Campaign Email Clicked

This trigger goes off whenever an email recipient clicks on a tracking link in a campaign email. Contact record attributes are not applicable as filterable attributes for this trigger.

Specify the campaign newsletter you want to set off the flow. Specify the URL of the tracking link in the email. You can add a single specific web address or a list of them. You can also set a "contains X" filter, where X is part of the URL. For example, you could set X to "http://www.x2crm.com/marketing", so that whether your contact clicks on and visits "http://www.x2crm.com/marketing/x2flow/" or "http://www.x2crm.com/marketing/#newsletters", they will be tracked.

flow triggers - campaign email opened


Campaign Email Opened

This trigger goes off whenever a contact opens any campaign email at all. Contact record attributes are not applicable as filterable attributes for this trigger.

Specify the campaign newsletter you want to set off the flow. You may set additional filters unrelated to a contact record (i.e. general variables like current month or day of week, which user is logged in, et cetera). Contact record attributes are not applicable as filterable attributes for this trigger.

flow triggers - unsubscribed from campaign


Unsubscribed From Campaign

Set up a flow triggered whenever someone unsubscribes from a campaign. Identify which of your campaigns you want to trigger the flow. You may set additional filters unrelated to a contact record (i.e. general variables like current month or day of week, which user is logged in, et cetera). Contact record attributes are not applicable as filterable attributes for this trigger.

 


 flow triggers - campaign web activity


Campaign Web Activity

The Campaign Web Activity trigger is similar to the Contact Web Activity Trigger, except this flow is triggered whenever a contact visits your webpage by clicking a link in a campaign email. Specify the campaign newsletter you want to set off the flow. Specify the URL of the tracking link in the email. You can add a single specific web address or a list of them. You can also set a "contains X" filter, where X is part of the URL. For example, you could set X to "http://www.x2crm.com/marketing", so that whether your contact clicks on and visits "http://www.x2crm.com/marketing/x2flow/" or "http://www.x2crm.com/marketing/#newsletters", they will be tracked.

Set additional filters based on general variables (e.g. current month or day of week, which user is logged in, et cetera) or contact record specific variables (e.g. lead score, date of last activity, et cetera).

flow triggers - newsletter email clicked


Newsletter Email Clicked

This trigger goes off whenever an email recipient clicks on a tracking link in a newsletter email. Contact record attributes are not applicable as filterable attributes for this trigger.

Specify the campaign newsletter you want to set off the flow. Specify the URL of the tracking link in the email. You can add a single specific web address or a list of them. You can also set a "contains X" filter, where X is part of the URL. For example, you could set X to "http://www.x2crm.com/marketing", so that whether your contact clicks on and visits "http://www.x2crm.com/marketing/x2flow/" or "http://www.x2crm.com/marketing/#newsletters", they will be tracked.

flow triggers - newsletter email opened


Newsletter Email Opened

This trigger goes off whenever a contact opens a newsletter email at all. Contact record attributes are not applicable as filterable attributes for this trigger.

Specify the campaign newsletter you want to set off the flow. You may set additional filters unrelated to a contact record (i.e. general variables like current month or day of week, which user is logged in, et cetera). Contact record attributes are not applicable as filterable attributes for this trigger.

flow triggers - unsubscribed from newsletter


Unsubscribed From Newsletter

Set up a flow triggered whenever someone unsubscribes from a newsletter. Identify which of your newsletter campaigns you want to trigger the flow. You may set additional filters unrelated to a contact record (i.e. general variables like current month or day of week, which user is logged in, et cetera). Contact record attributes are not applicable as filterable attributes for this trigger.

flow triggers - web activity


Web Activity

The web activity trigger is set off whenever someone is anywhere on your website or on a specific page of your website. This trigger is suitable for unregistered contacts in your X2CRM system. However, the web surfer will still need to have a web tracking cookie on their computer. They can get this cookie if they click on a tracking link in a marketing email.
 
For this trigger, you can either add a single specific web address or a list of them. You can also set a "contains X" filter, where X is part of the URL. For example, you could set X to "http://www.x2crm.com/marketing," so that whether your contact visits "http://www.x2crm.com/marketing/x2flow/" or "http://www.x2crm.com/marketing/#newsletters," they will be tracked. 

Notice on the available filter settings for this flow that the option to filter contact attributes has been greyed out of the dropdown menu.  This is expected, because - as previously mentioned - there is no contact record available.

trigger example - web activity 01.01


flow triggers - record created


Record Created

You can use any module record type in X2CRM as the basis for this trigger. Select the record type from the dropdown menu. Choose general attributes or module-specific attributes to create filters around. This example flow is triggered whenever an action with a severe priority is created over the weekend. It sends out an email to the relevant X2CRM user so they can decide how best to handle it.

trigger example - record created


flow triggers - record deleted


Record Deleted

You can use any module record type in X2CRM as the basis for this trigger. Select the record type from the dropdown menu. Choose general attributes or module-specific attributes to create filters around. This example flow is triggered whenever a campaign which has not yet been completed is deleted from X2CRM.

trigger example - record deleted


flow triggers - tag added


Tag Added

Set up a trigger to start a flow whenever a record is updated with a specific tag. You can set attribute filters related to the module from the available dropdown menu as well. The flow will only initiate if all conditions are met. The example trigger below is set to start a flow whenver a contact with a lead score greater than 4 is tagged with "#cloudconference".

trigger example - tag added


flow triggers - tag removed


Tag Removed

Sometimes we have to revisit issues that we thought had been resolved. If and when an important tag is removed from a record type, you'll probably want to know about it. You can use any module type to set off this trigger which is sparked whenever a tag is removed from a record. For instance, if a bug report marked "#resolved" has that tag removed, that is cause for some notification. Set up a flow to send out an alert whenever those specifications are met.

trigger example - tag removed


flow triggers - record updated


Record Updated

You can use any module record type in X2CRM as the basis for this trigger. Whenever one of your X2CRM users updates a record type of your stipulation, and the attribute filters you set are satisfied, then the trigger will set off the flow. For instance, if you want to send out a notification whenever a bug report is resolved by a specific user, you can set those attributes in the triggers specifications, as illustrated below.

trigger example - record updated 01.01


flow triggers - record viewed


Record Viewed

You can use any module record type in X2CRM as the basis for this trigger. Whenever one of your X2CRM users views a record type of your stipulation, and the attribute filters you set are satisfied, then the trigger will set off the flow. For instance, if one of your users view a specific media file, you can create a pop up notification letting them know it's a high priority media file.

trigger example - record viewed 02.01


flow triggers - user signed in


User Signed In

Whenever one of your users logs in or out of X2CRM can be an event that can trigger a flow. In the case of a user sign in you can set up a filter that only sets off the flow if a specific user (or a user within a set of specific users) signs in of X2CRM. The particular example below demonstrates a filter that only sets off the trigger if the user is not a specific user. To select multiple users, you must select one of the list options (i.e. "in list" or "not in list") and then hold down the control key as you click. Set additional attribute filters, for instance whether the current day of the week is not Saturday or Sunday.

trigger example - user signed in 01.01


flow triggers - user signed out


User Signed Out

Whenever one your users logs in or out of X2CRM can be an event that can trigger a flow. In the case of a user sign out you can set up a filter that only sets off the flow if a specific user (or a user within a set of specific users) signs out of X2CRM. To select multiple users, you must select one of the list options (i.e. "in list" or "not in list") and then hold down the control key as you click. Set additional attribute filters, for instance whether the current time is before 5pm that day.

trigger example - user signed out 01.01


flow triggers - contact web activity


Contact Web Activity

The Contact Web Activity trigger is similar to the Web Activity Trigger, with one big difference - this time you a contact record is available. This trigger is initiated whenever a contact is on a certain web page, which you specify in the trigger filter settings. The contact must be a registered contact in your X2CRM system, as well as have a web tracking cookie on their computer. The ways in which they can get this cookie are if they click on a tracking link in a marketing email or if they come in through a web lead form. 

You can add a single specific web address or a list of them. You can also set a "contains X" filter, where X is part of the URL. For example, you could set X to "http://www.x2crm.com/marketing", so that whether your contact visits "http://www.x2crm.com/marketing/x2flow/" or "http://www.x2crm.com/marketing/#newsletters", they will be tracked.

 flow triggers - new web lead


New Web Lead

X2CRM helps you capture new web leads with a handy form creator. When you capture a new web lead, you can configure an automated email response from the email configuration section of the administration panel. From that page you can set the default sender address for web lead responses and select an email template (which you can create in Docs). Additionally, you can obviously use the web lead trigger to initiate other kinds of actions with X2Flow. This trigger allows you to set basic attribute filters like current date and time, current users, and so forth. It also allows you to use attributes from the Contacts module as filters, like lead score, deal value, or location details. Select an attribute from the available dropdown menus, click add condition, and then set the relevant values for the filter. Only web leads that meet the attribute requirements that you set here will trigger your flow.

flow triggers - targeted content requested


Targeted Content Requested

The new X2CRM targeted content services are an excellent way to deliver custom content to clients and impress potential new customers. When a specified URL is visited, X2Targeted Content is able to push tailored content to the visiting user based on the attributes of that contact in your X2CRM system.
The web content returned by a flow that has been triggered by a Targeted Content Request will replace the embed code when a visitor comes to the specified page.Saving the flow will generate an embed code. You can (and should) also create web content which gets displayed if the visitor doesn't have an associated contact record or if your flow terminates without pushing web content.

 

 


 

TOP



Flow Actions

Flow triggers tell X2CRM when to do something. Flow actions tell it what to do. Like the flow triggers, the flow actions  in X2CRM are each based on a module type in the broader software. Many of the flow actions allow you to update or filter by certain module-specific attributes.   

flow actions - conditional


Conditional Switch

The conditional switch is a decision point in your flow. It sets an attribute filter that evaluates a specific parameter. It creates a forked path that will be followed based on whether the filter criteria were met or not. The top path is followed if the parameter requirements are met. The bottom path is followed if they are not met. The available attribute filters are dependent on the flow's triggger. That is, the module that the trigger references will determine which attributes you can compare.


flow actions - API call


Remote API Call

This action makes a HTTP request to a URL of your choosing, of type GET, POST, PUT or DELETE. You can also include a request body by using the Add Attribute button to build a flat list of key-value pairs. This list will be sent to the remote URL as form data (mime type "application/x-www-form-urlencoded"). Note, the Value fields support formulas and variable replacement, so you can include dynamic data in the payload.

flow actions - add action


Create Action

With this flow item you can automate the creation of a new action for a user of your X2CRM system. 
Enter the details for the action, i.e. its subject, description, assignment, priority, and visibility, just as in the actions module. For instance, you may want to create a high priority public task to schedule a demo call every time a web lead comes in. You can then assign the task to individual users or to groups like your sales reps, in which case the lead will be assigned based on your lead routing rules.
When creating the content of the action, you may also use dynamic variables based on the module type you're working within - i.e. which module your flow trigger is based on.

flow designer - create action 01.01


flow actions - post to feed


Post to Activity Feed

You can design a flow which will automatically post an item to the X2CRM activity feed. Set the post type (e.g. announcement) and enter the text of the notification. Specify which user's account the activity event will be posted from and whether or not the post will create a notification. When entering the content of the post, you may also use dynamic variables based on the module type you're working within - i.e. which module your flow trigger is based on.


flow actions - notification


Create Popup Notification

This flow item creates a pop up notification on a specific users page. Set who will receive the notification. Enter the message of the notification, highlighted in green. When entering the content of the message, you may use dynamic variables based on the module type you're working within - i.e. which module your flow trigger is based on. When the trigger parameters are met, the notification will pop up on the user's screen, shown in the highlighted red box.

flow designer - popup notification


flow actions - email


Email

This flow item allows you to email a specific address (as opposed to email contact, which emails the record whose action triggered the flow). You can use the "send as" drop down menu to select the account to send the email from. Set up external 3rd party email accounts using the apps manager.

X2Flow email 01.01


flow actions - comment


Add Comment

This flow item updates the record associated with the flow trigger and adds a comment to the page. Comments can be viewed in the interaction history widget on a contact's record page, shown below.

 contact comments 01.01


flow actions - create record


Create Record

Create a new record of any type. Add the attribute fields you'd like to include in the new record's page. Feel free to use dynamic variables associated with the record type and which are consistent with the module of the flow trigger. Be careful, though. Some record types have required fields, and if your flow fails to specify those fields the record won't be able to be made.

flow actions - add action


Create Action for Record

In contrast to the more sparsely titled Create Action, this flow item creates a new action associated with the record that triggered this flow. This means that if your trigger is, for instance, Tag Removed, then Create Action for Record will associate a new action with the contact whose tag has been removed. Enter the relevant details for the action, i.e. its subject and description. When creating the content of the action, you may also use dynamic variables based on the module type you're working within - i.e. which module your flow trigger is based on.

flow actions - delete record


Delete Record

Permanently delete the record associated with the flow trigger. This action cannot be undone so proceed with caution.

flow actions - email


Email Contact

Unlike its cousin, the more sparsely titled Email, the Email Contact flow action includes all email related fields except for the addressee (i.e. the "to" field). This is because this action automatically addresses an email to the record associated with the flow trigger. You can use the "send as" drop down menu to select the account to send the email from. Set up external 3rd party email accounts using the apps manager.

flow actions - list add


Add to List

Lists are lists of contacts that you can use to address marketing email campaigns or send newsletters to. X2CRM can create dynamic lists, which update their rosters automatically based on a set of feature criteria, or it can create static lists, which have stipulated and manually managed rosters. The Add to List function updates a static list by adding the contact associated with the flow trigger to a specified list roster.

flow actions - list remove


Remove from List

Lists are lists of contacts that you can use to address marketing email campaigns or send newsletters to. X2CRM can create dynamic lists, which update their rosters automatically based on a set of feature criteria, or it can create static lists, which have stipulated and manually managed rosters. The Remove from List function updates a static list by checking to see if the contact associated with the flow trigger is on a specified list roster, and if so, removes them.

flow actions - reassign record


Reassign Record

Records in X2CRM are associated with a certain users (i.e. your company staff). At certain times, you may need to change user associations with contact records. Use this flow action to do that. From the dropdown menu you can select specific users, assign it to Anyone (meaning whoever wants to can claim it), or use your lead routing rules to automatically pick a user to associate the record with.

flow actions - tags


Add or Remove Tags

Contacts, Opportunities, Campaigns, and several other modules in X2CRM operate with a tag system. These are words or phrases that are associated with records which then become searchable reference pointers back to those records. The X2Flow designer can automate the addition or subtraction of tags on a record page. Add or Remove specific tags by naming them, or use the Clear All option to remove any and all of a record's tags.

flow actions - update record


Update Record

Add attributes to update and specify their new value for that attribute's content. The available attributes are derived from the module that the flow's trigger is based on. The flow will automatically update the record of the relevant record. For example, the Contact Web Activity trigger will allow you to use the Update Record flow action to change the Lead Score attribute for that record. But the Action Overdue trigger would allow you to use the Update Record flow action to change the Due Date attribute.

flow actions - wait


Wait

Specify an amount of time for the system to wait before moving on to the next flow action. Enter an integer and specify the units of measure.

flow action examples - wait

 


flow actions - push content


Push Web Content

The web content returned by this flow will replace the embed code when a visitor comes to your page. The content you put in this message can contain {attributes} based on the visiting contact's record. The attributes can be things as varied as the contact's first name {firstName}, the contact's assigned sales rep {assignedTo}, or even their city {city}. See the attributes section of this guide for more information on module attributes.

TOP



How To

Start a Flow

How To - Marketing Menu

How To - Flow Menu

The First thing to do in starting a new flow is to get to the flow editor. X2Flow is a feature of the Marketing module in X2CRM. Once you’ve navigated to that module, select X2Flow from the left hand side panel.

Once you’ve clicked that option you are now in the X2Flow campaign overview screen. From there you can click on Create Flow and begin the process of creating your own new customized marketing automation.

Select a Flow Trigger

How To - Trigger Menu2

An X2Flow is triggered by a certain event in X2CRM. These things can be as varied as a new web lead coming in, a contact tag being added or removed, or a contact clicking on a marketing campaign email. The full list of X2Flow triggers is located here within this document.

The types of flow actions that are available to you are dependent on the flow trigger you select. For example, you may only select the Push Web Content flow action if you have selected the Targeted Content Requested trigger.

Additionally, the types of dynamic variable attributes that you can select are dependent on the type of flow trigger you select. Each flow trigger is associated with a certain module type. X2Modules are discussed at length in the X2CRM User Reference Guide. For example, if you select the Contact Web Activity trigger, the attributes you will be referencing will be associated with the Contacts module. If you select the Action Overdue trigger, the attributes you will referencing will be associated with the Actions module.

A full list of dynamic variable attributes is located here within this document.

Combine Flow Actions

How To - Add ActionThe most interesting part of X2Flow is the ability to create customized sequences of marketing automation. This is where combining your flow actions comes in. Each flow action allows you to introduce some type of automated behavior in X2CRM. For example, the Add Tag flow allows you to automatically add a tag of a certain type to the record page.

To add a flow action to your current flow simply drag and drop it into the flow editor window. Nearly all of the actions have data fields and attributes that can be modified to tailor the flow even further.

The conditional Switch allows you to create a decision fork in the flow if a certain attribute value has been met.

The full list of X2Flow actions is contained here in this document.

Use Formulas in X2Flow

formulas

X2Flow offers an enormous degree of automation power and allows creative uses of the attribute fields in X2CRM. A certain points, you may want to include an equation which can operate over data fields, modifying them incrementally or via some mathematical function. In X2Flow, you can use formulaic equations to achieve this.

In X2CRM, formulas are introduced with an equals sign (=) at the start of the equation. You can use the attributes in various modules as variables in your equation. The formulaic equation feature is a powerful tool in X2Flow, however, we advise that it be used only with numerical data fields. Thus, we recommend that if you wish to use formulas to update a lead score, for instance, then we recommend that you first convert the field to a numerical field type first, in the X2Studio field manager. Then, you can use the formula like the following: ={leadscore} + 1

 

menu accompaniment image - 01.02

View Example Flows

 

 

There are a few example flows illustrated on the X2Flow overview page which can be found here.

 

 

 

TOP



 

Miscellany

Attributes

For a video on using and chaining attributes, click here. Attributes are ubiquitous throughout X2CRM and particularly X2Flow. They appear as filter parameter settings in triggers, certain flow actions, and conditionals.

Note that there are multiple attributes with the same dynamic variable (e.g. ID numbers). However the dynamic variable is also bound by the module you are working within. Thus when working within the contacts module, {phone} only refers to the phone number of a contact, never to the phone number of another record type, like an account record, for instance. Another thing to note is that although you may be working within a certain module, the module you are referring to might be different. For example, although email texts can be drafted within the Docs module, using the dynamic variable {name} in an email body will refer to the name of the addressee of the email. This is because emails refer to the Contacts module for their dynamic variables. The module that the dynamic variables will refer to is usually denoted.

 

Attribute Module Description Dynamic variable
Address Accounts The street address of the account company. {address}
Revenue Accounts The amount of money the account is bringing in to your business. {annualRevenue}
Assigned To Accounts The X2CRM user that the account is associated with. This is the user(s) or the user group(s) that interface with the account and represent your company. {assignedTo}
City Accounts The city of record for the account. {city}
Country Accounts The country of record for the account. {country}
Create Date Accounts The date that account was created in your X2CRM system. {createDate}
Description Accounts This is a short description of the account company and their business (e.g. Samosa company. They make samosas. Chicken Tikka is their best seller). {description}
Employees Accounts The numerical amount of employees that the account company has (e.g. 42). {employees}
ID Accounts The account's unique ID number. This attribute exists more for the system's benefit than for the user's. This is not listed by default on an account's page. To find it, you can either go into your accounts list and set "ID" as one of the sortable columns, or you can go into the X2Studio and utilize the form editor. The form editor allows you to include or exclude fields from displaying by default. {id}
Last Activity Accounts The date (and time) of the last activity on the account record. This can include updating the record, adding a new primary contact, etc. {lastActivity}
Last Updated Accounts The date (and time) of the last update on the account record. This only includes modifying the data fields of the record. {lastUpdated}
Name Accounts The name of the company that are the account holders (e.g. Example co. or X2CRM). {name}
Parent Accounts This option is here in the event that an account is a subaccount of a larger account. For example, if you're selling produce to a hotel restaurant, the hotel's account might be the parent of the restaurant's account. {parentAccount}
Phone Accounts The phone number for the primary contact on an account. {phone}
Primary Contact Accounts A contact in your X2CRM system that represents the company account. The go-to contact when you want to interface with an account. {primaryContact}
State Accounts An account’s address state of record. {state}
Symbol Accounts An acronym or initialism or other type character string that represents the account holders' name, much like a NYSE stock symbol (e.g. GOOG for Google). {tickerSymbol}
Type Accounts This is the nature of the account holders' business (e.g. RestaurantFinanceManufacturing, or software). {type}
Updated By Accounts The X2CRM user who last modified the account record. {updatedBy}
Visibility Accounts An account can either be publicly viewable or set to private. If it is a public record, all your X2CRM users will be able to look upon it. {visibility}
Website Accounts The url of record for the account. {website}
Postal Code Accounts The postal code of record for the account address. {zipcode}
ID Actions An action's unique ID number. This attribute exists more for the system's benefit than for the user's. This is not listed by default on an action's page. To find it, you can either go into your actions list and set "ID" as one of the sortable columns, or you can go into the X2Studio and utilize the form editor. The form editor allows you to include or exclude fields from displaying by default. {id}
Assigned To Actions An assignment field that identifies the X2CRM user who is associated with a particular record. Action assignment can be done by anyone. Action assigners can choose to assign actions to specific users or groups of users. {assignedTo}
Subject Actions The title of your action. {subject}
Visibility Actions This is the public visibility of the action (i.e. who can see it). The options are either public, meaning that all your users can see it, or private, meaning that only administrators and the action's assigned user can view the action. {visibility}
Association Type Actions The association type is the X2CRM module that the action's association is based in. For example, an action might be associated with a specific individual customer, which would fall under the contacts module. Or, it might be associated with a service record (e.g. a product repair), which would of course fall under the service module. The options include all the X2CRM modules and any created modules. {associationType}
Association Actions The record entry in your X2CRM system that you want to link with a specific action. This is also based upon the module type specified in Association Type. {associationName}
Due Date Actions The date (and time) that the assigned action will be due. {dueDate}
Create Date Actions The date (and time) that the assigned action was created. {createDate}
Complete Actions A Boolean check that denotes whether or not the action has been completed yet. {complete}
Reminder Actions A Boolean check that denotes whether or not there has been a reminder set for the action. {reminder}
Completed By Actions The X2CRM user who marked the action as being complete. {completedBy}
Date Completed Actions The date (and time) that the action was marked "complete". {completeDate}
Last Updated Actions The date (and time) that the action was last modified (i.e. reassigned, completed, etc.) {lastUpdated}
Updated By Actions The X2CRM who last updated the action. {updatedBy}
All Day Actions If an action event's due date is set not to a specific time, but is instead set {allDay}
Color Actions X2CRM features a color coding system for ease of use. The color coding system is not assigned a specific value. Each color is yours to interpret. {color}
Description Actions A short summary of the action and what it entails (e.g. take the auto into the shop for an oil change. Make sure you get one of those evergreen air fresheners). {actionDescription}
Contact Actions A lookup-type field that finds the X2CRM contact who is associated with a particular record, usually either Quotes or Service. {associationId}
Assigned To Bug Reports An assignment field that identifies the X2CRM user who is associated with a particular record. Bug reports can be created by anyone.  The assigned user can be set when the report is created, and it can also be updated afterwards at any time. Bug report assigners can choose to assign actions to specific users or groups of users. {assignedTo}
Blocks Bug Reports If a bug cannot be fixed until a second, separate bug has been fixed, the second bug is considered a block to the the first. The value of this attribute will be the id number of the blocking bug. {blocks}
Create Date Bug Reports The date that the bug report was created in your X2CRM system. Bug reports can be backdated, meaning the create date can be manually updated. {createDate}
Description Bug Reports Use this field to explain the nature of the bug, e.g. When the client attempts to open the software UI, they receive an error message. {description}
Duplicate Of Bug Reports If the bug has been submitted previously by someone else (or the same person), then it can be noted that the new bug report is a duplicate of a previous bug. {duplicate}
Error Code Bug Reports This is a string field, so you can put any text in here you like. You can use this field to implement any code naming system for bug reports your company might have. {errorCode}
File Bug Reports The specific file (typically a PHP file) that the bug is creating problems for. {file}
ID Bug Reports An bug report’s unique ID number. This attribute exists more for the system’s benefit than for the user’s. This is not listed by default on a bug report’s page. To find it, you can either go into your bug report list and set “ID” as one of the sortable columns, or you can go into the X2Studio and utilize the form editor. The form editor allows you to include or exclude fields from displaying by default. {id}
Last Activity Bug Reports The date (and time) that any activity took place on the bug report record, including updates. {lastActivity}
Last Updated Bug Reports The date (and time) that a field in the bug report was last modified. {lastUpdated}
Line Bug Reports The specific line that the bug is on (or starts on) within the specific file that the bug is in. {line}
Name Bug Reports This name refers to the ID number for the big report. That is, by default this name is the same as the bug report's ID number. {name}
PHP Version Bug Reports This is the point release of the PHP code that is relevant to the bug report. {phpVersion}
Severity Bug Reports This is a rating scale for the level of severity this bug problem poses to the bug submitter. Perhaps it is a trivial problem (e.g. a simple feature request), or it could be a major issue that demands attention right away (e.g. an admin account's security has been compromised). Either way, this field is here so you can more efficiently handle your bug report work load. {severity}
Status Bug Reports This is the current state of affairs with respect to the bug report. This field has a dropdown menu that you can choose a value from, which has the following default options: unconfirmed, confirmed, in progress, closed (resolved internally), closed (unable to reproduce), closed (duplicate), {status}
Subject Bug Reports A short title for your bug report. The subject includes a brief, one-line summary of the issue. A more in-depth description of the bug can go in the description field. {subject}
Type Bug Reports The nature of the bug, e.g. PHP warning, or CException. {type}
Updated By Bug Reports The X2CRM user who last updated any of the fields in the bug report record. {updatedBy}
Visibility Bug Reports This setting allows you to decide who is privy to this bug. A public setting will allow any of your X2CRM users to view the bug. Use the private setting to only allow admins and the associated users to {visibility}
X2 Version Bug Reports This is the version of X2CRM that you are using when you enter the bug report. {x2Version}
Active Campaigns A Boolean check box that denotes the active status of the campaign. A check means "active", no check means "inactive". Note that "inactive" does not mean "complete". {active}
Assigned To Campaigns The X2CRM user to whom the campaign record is assigned. The assigned user can be set during the creation of the campaign, and it can be updated at any time afterwards. {assignedTo}
Complete Campaigns This is a Boolean check that denotes whether the campaign is complete or not. A check means "complete", no check means "incomplete". A complete campaign will also be inactive. {complete}
Content Campaigns This is the actual body content of the text that gets sent out to your contact list if the campaign includes any kind of mailing component. This may be your newsletter or your marketing email, for example. {content}
Cost Campaigns The dollar amount that the campaign will incur as a cost to your company. {cost}
Create Date Campaigns The date (and time) that the campaign was created. {createDate}
Description Campaigns A short description of the campaign {description}
ID Campaigns An campaign’s unique ID number. This attribute exists more for the system’s benefit than for the user’s. This is not listed by default on a campaign’s page. To find it, you can either go into your campaign list in the marketing module and set “ID” as one of the sortable columns, or you can go into the X2Studio and utilize the form editor. The form editor allows you to include or exclude fields from displaying by default. {id}
Last Activity Campaigns The date (and time) of the last activity on the campaign record. This can include updating the record, associating a new contact list, logging a related call, etc.. {lastActivity}
Last Updated Campaigns The date (and time) that the campaign was last modified (i.e. reassigned, completed, etc.). {lastUpdated}
Launch Date Campaigns The date (and time) that the campaign was first set to "active" status. {launchDate}
Contact List Campaigns The X2CRM contacts to which the campaign is directed. These lists are quick, powerful, and highly customizable. You can create static lists which you manually update, or dynamic lists which auto-populate based on certain criteria (which you can specify). For much, much more information on lists, check out our user reference guide. {listId}
Master Campaign ID Campaigns If you are creating a sub-campaign (e.g. a newsletter to high value account clients within the larger newsletter recipient base), then you can associate the sub-campaign with the parent campaign. Use this field to connect the two associated campaigns and embed the smaller in the larger. {masterId}
Name Campaigns This is a text field that represents the name of your campaign (e.g. version 6.1 release newsletter). {name}
Send As Campaigns The X2CRM user email address that the campaign (if it is a mailing campaign, that is) will be sent from. You can read all about setting up default email accounts for various mailing tasks, as well as connecting external mailing accounts, on our user reference guide. {sendAs}
Subject Campaigns A more in-depth description of the campaign than the campaign name. {subject}
Template Campaigns X2CRM allows for the creation and usage of campaign templates. Learn more about creating general email and marketing email templates on our user reference guide. This field is a dropdown menu that contains all the previously created templates in X2CRM. {template}
Type Campaigns This is the type of marketing this campaign is running. Most campaigns are likely to be email campaigns. However, other default campaign types include "physical mail" and "call list". This field is a dropdown menu, and thus you can of course edit that dropdown menu in the X2Studio dropdown menu editor. {type}
Updated By Campaigns The X2CRM user who last modified the campaign record. {updatedBy}
Visibility Campaigns A campaign can have public or private visibility. If the record is private, only the creator, the assigned user(s), and the administrators will be able to view the record. {visibility}
Assigned To Contacts An assignment field that identifies the X2CRM user who is associated with a particular record. Contact and lead assignment is done by administrators. Administrators may choose to manually or automatically assign contacts, or to allow X2CRM users to assign themselves to contacts. {assignedTo}
Lead Score Contacts The lead score is a number assigned to a contact by an X2CRM user that represents the quality of the lead (i.e. a combined rating of the likelihood of closing the deal with the lead (Confidence) as well as the potential worth of the lead's deal (Deal Value)). The lead score is based on a 1-5 point scale, represented in nice gold stars. Mmm, gold. {leadscore}
Deal Status Contacts The state of the current dealings with a contact. Default options include Won, Lost, or Working. However, like everything in X2CRM, these are customizable. Set additional or alternative sources from the X2Studio dropdown editor found in the administration module. Check the user reference guide for a how to guide. {dealstatus}
ID Contacts A contact's unique ID number. This attribute exists more for the System's benefit than for the User's. This is not listed by default on a contact's page. To find it, you can either go into your contact list and set "ID" as one of the sortable columns, or you can go into the X2Studio and utilize the form editor. The form editor allows you to include or exclude fields from displaying by default. {id}
Full Name Contacts A concatenated combination of the first and last name fields. Does not include title. {name}
First Name Contacts A contact's first name (e.g. Michael). {firstName}
Last Name Contacts A contact's surname (e.g. Bolton). {lastName}
Title Contacts A contact's title (e.g. Sir, Doctor, The one and only – or – Assistant, VP of North American Sales, VP of International Sales). {title}
Account Contacts The X2CRM account that the contact is associated with. This field auto-completes, so start typing in the name of an account and X2CRM will pop up a list of account names that match your input. If not manually set, this field is automatically set to the name of an account whenever that contact becomes associated with that account {company}
Phone Contacts A contact's primary contact phone number. {phone}
Email Contacts A contact's primary contact email address. {email}
Website Contacts A url associated with a contact (e.g. http://yourcontactssmallbusiness.com/product.html). {website}
Linkedin Contacts A contact's Linkedin account url. {linkedin}
Skype Contacts A contact's Skype account url. {skype}
Googleplus Contacts A contact's Googleplus account url. {googleplus}
Address Contacts A record's street address. {address}
Address 2 Contacts A record's street address continued (i.e. additional address information, e.g. apt or ste #). {address2}
City Contacts A contact's address city of record. {city}
State Contacts A contact's address state of record. {state}
Postal Code Contacts A contact's postal code (e.g. zip code) of record. {zipcode}
Country Contacts A record's address country of record. {country}
Visibility Contacts This is the public visibility of the contact on your X2CRM system. If the contact record is public, every X2CRM user will be able to view the contact. If the contact is private, only the contact's users and administrators will be able to view the contact. {visibility}
Background Info Contacts The information about a record supplied either by an X2CRM user or by the contact themselves, when coming as a web lead {backgroundInfo}
Last Updated Contacts The date the record's data fields were last altered by a user of your X2CRM system. {lastUpdated}
Last Activity Contacts The date of the last activity of any sort related to the the contact record (e.g. record saved, record shared, contact emailed, etc). {lastActivity}
Updated By Contacts The X2CRM user who last updated the record {updatedBy}
Lead Source Contacts The origin of a contact lead. Default options include Google, Facebook, Walk-in, or None. However, like everything in X2CRM, these are customizable. Set additional or alternative sources from the X2Studio dropdown editor found in the administration module. Check the user reference guide for a how to guide. {leadSource}
Lead Date Contacts The date that a lead came in, whether it be a web lead, in person, or any other sort. {leadDate}
Priority Contacts The importance of a contact's deal. This is a text field and as such can be filled in however you like, using whichever metric you fancy. We recommend a tripartite system of low, medium, and high. {priority}
Confidence Contacts Confidence is a 5-point scale – represented in gold stars – that represents the likelihood of closing the deal with the lead. The confidence rating is assigned by the user associated with a contact record. {rating}
Create Date Contacts This is the date that the contact was entered into your X2CRM system. Ah, memories. {createDate}
Facebook Contacts The contact's Facebook page url {facebook}
Other Contacts This field can be anything you like. Perhaps "favorite food? "hobbies or interests?"" {otherUrl}
Lead Type Contacts The type of origin of a contact lead. Default options include web, phone, in person, or email. However, like everything in X2CRM, these are customizable. Set additional or alternative sources from the X2Studio dropdown editor found in the administration module. Check the user reference guide for a how to guide. {leadtype}
Close Date Contacts This the date a sale was confirmed with a contact. This date, in conjunction with the lead date, can help you analyze your sales efficiency. {closedate}
Interest Contacts This is a string data field. You can enter whatever interest the client had in doing business with you, typically whatever product you offer, like Data Migration, or Pro Edition software. However, this could be any type of information you want to store in here. Just be aware that in order for it to be useful for sorting or attribute filtering, it has to be consistent. {interest}
Deal Value Contacts This is the worth of the deal with the contact, represented in your designated currency (as specified in your general settings from the administration panel). Learn more from our user reference guide." {dealvalue}
Lead Status Contacts This is the status of a sales lead once they come in. This is a dropdown menu with the options Unassigned, Assigned, Accepted, Working, Dead, or Rejected. Learn more about lead routing in the user reference guide. {leadstatus}
Do Not Call Contacts This is a boolean (i.e. true or false) setting that tells you whether the customer has requested to not be called or not. If the box is checked, the customer does not want to be called. {doNotCall}
Timezone Contacts This is the php time zone code designation typically denoted as "CONTINENT/CITY" where "continent" is the continent your contact lives on, and "CITY" is a major city in that timezone. For example, Central time would be "America/Chicago". For a list of designations visit this site. {timezone}
Duplicate Check Contacts This is a boolean checkbox that indicates if a contact record has been evaluated for potential matching duplicate records in X2CRM. This attribute exists more for the System's benefit than for the User's. If this box is unchecked, whenever the contact record is viewed in X2CRM\ the system will search for other records with similar entries in the data fields. If there is a match, X2 will warn you and ask whether to keep the old record, the new record, or both. As of yet there is no "combine" function. Once the record has been checked for a duplicate, the checkbox will return to being ticked. {dupeCheck}
Do Not Email Contacts This is a boolean (i.e. true or false) setting that tells you whether the customer has requested to not be emailed or not. If the box is checked, the customer does not want to be emailed. {doNotEmail}
Web Tracking Key Contacts This is the contact's web tracking key. Anytime a contact fills out a web lead form, or if they click a tracking link in an email, a cookie is installed on the contact's computer. This lets you know whenever the contact visits your website. This is a great event to use as a trigger (i.e. contact web activity) so that you can offer information to that contact, giving you a better chance of closing the deal. {trackingKey}
Opportunity Contacts The opportunities tab in X2CRM is a fully-articulated module with robust management abilities. Use this field to associate a contact with a sales opportunity. This field auto-completes, so start typing in the name of an account and X2CRM will pop up a list of account names that match your input. {opportunity}
Created Docs The date (and time) that the doc was created. {createDate}
Created By Docs The X2CRM user who created the document. {createdBy}
Edit Permissions Docs The edit permissions field is a list of your X2CRM users who can update the document in question. Go to the Docs module and enter edit mode to update the doc permissions. To select multiple users from the list, simply hold down the control key as you click. {editPermissions}
ID Docs A document's unique ID number. This attribute exists more for the system's benefit than for the user's. This is not listed by default on a doc's page. To find it, you can either go into your document list in the docs module and set "ID" as one of the sortable columns, or you can go into the X2Studio and utilize the form editor. The form editor allows you to include or exclude fields from displaying by default. {id}
Last Updated Docs The date (and time) that the document was last updated by one of your X2CRM users. {lastUpdated}
Name Docs The document's title. {name}
Subject Docs A description of the document's content, i.e. the subject of the writing within the document. {subject}
Body Docs This is the actual content of the document. {text}
Type Docs Document types are designated when the document is created. The options for creation are located in the left hand menu of the documents module. {type}
Updated By Docs The X2CRM user that most recently modified the document. {updatedBy}
Visibility Docs Like other records and entries in X2CRM, documents can be made public or private. Public documents are viewable by anyone. Private documents are viewable only by their associated users, and administrators. {visibility}
ID Groups The unique ID number of a user group is a useful tag that uniquely identifies the particular group. This attribute exists more for the system's benefit than for the user's. {id}
Name Groups The identifying name of the group (e.g. Sales Reps) {name}
Association ID Media The ID number of the record associated with the media. This can be a contact, an opportunity, account, or a background. This association can be set in the media module, as outlined in the user reference guide here. {asssociationID}
Association Type Media The record type of the record associated with the media. This can be a contact, an opportunity, account, or a background. This association can be set in the media module, as outlined in the user reference guide here. {associationType}
Create Date Media The date (and time) that the media was uploaded {createDate}
Description Media A short description of the media (e.g. worksite progress) {description}
Dimensions Media This trait only applies to images. This is a text field with a format like 1000 x 650, for example {dimensions}
Google Drive Media A boolean true/false check on whether the media file is stored in the user's google drive or not. Google drive integration is discussed in depth here {drive}
File Name Media The name of the file (e.g. me_saying_stuff.mp3), not the title of the media (e.g. An Impassioned Treatise on European Union Agricultural Subsidies) {fileName}
File Size Media The amount of bytes (KB or MB) that the file takes up in memory. There is an 8 MB upper limit on files. The {filesize}
ID Media The unique ID number of the media file. Like other ID numbers in X2CRM, this ID exists more for the system's benefit than for the user's. {id}
Last Updated Media The date (and time) that the record was last updated. This includes modifying the data fields of the media record {lastUpdated}
MIME Info Media The MIME data contains information about what type of file the media is (i.e. audio, video, image, etc.). It can be a more reliable indication of the filetype than the file extension (e.g. .mp3 or .wav). {mimetype}
Private Media A boolean true/false check on whether the media file is private {private}
Title Media The name of the media content (e.g. Fall Product Line), not the name of the file (e.g. fall_product_descriptions.txt) {title}
Uploaded By Media The X2CRM user who uploaded the content to your X2CRM system. This will also be noted in the media widget along the right side panel. More information on the media widget is contained in the user reference guide here {uploadedBy}
Account Opportunity The X2CRM account that the opportunity record is associated with. This field auto-completes, so start typing in the name of an account and X2CRM will pop up a list of account names that match your input. The account name will typically be the same as the opportunity name, since opportunities are typically associated with companies {account}
Assigned To Opportunity The X2CRM user who the opportunity is assigned to. This is the user who is responsible for following up on the sales lead that the opportunity represents. {assignedTo}
Create Date Opportunity The date (and time) that the opportunity was entered into your X2CRM system {createDate}
Description Opportunity A short description of the opportunity (e.g. this car wash company is interested in securing a soap supply deal with us). {description}
Expected Close Date Opportunity The date by which the opportunity is expected to be converted to a sale {expectedCloseDate}
ID Opportunity The unique ID number of the opportunity record page. Like other ID numbers in X2CRM, this ID exists more for the system’s benefit than for the user’s. {id}
Last Activity Opportunity The date (and time) of the last activity on the opportunity page. This includes updating data fields but also completing sales stages, logging a call, adding a comment or associated action, and etc. {lastActivity}
Last Updated Opportunity The date (and time) that the data fields of the opportunity record were last modified. {lastUpdated}
Lead Source Opportunity The avenue through which the opportunity came in to your sales team {leadSource}
Name Opportunity The name of the opportunity. Typically this is the name of the company you will potentially be doing business with {name}
Probability Opportunity The odds of closing the deal with the opportunity company. This is a manually set attribute, probably by your sales team for instance. {probability}
Quote Amount Opportunity The dollar amount that has been quoted to the potential client for the deal {quoteAmount}
Sales Stage Opportunity Every opportunity in X2CRM has a sales stage option. This is a dropdown menu containing the deal status status options – working, won, and lost. Of course, since this is a dropdown menu, it can be modified in the X2Studio dropdown menu editor, located within the administration panel in X2CRM. From there, you can modify the sales stages to include or exclude any option you like. {salesStage}
Updated By Opportunity The X2CRM user who last updated the opportunity. {updatedBy}
Visibility Opportunity This is the public visibility of the opportunity on your X2CRM system. If the opportunity record is public, every v user will be able to view it. If the opportunity record is private, only the opportunity’s associated users or your X2CRM administrators will be able to view the opportunity record page. {visibility}
Adjustment Products If a price adjustment has been offered in a quote (e.g. 10% discount for bulk purchase), then it will be noted on the product here {adjustment}
Create Date Products The date (and time) that the product was first entered in your v system. {createDate}
Currency Products The currency unit for transactions related to the product (e.g. USD, GBP, JPY, etc.). Especially useful for international companies. {currency}
Description Products A short description of the product (e.g. limited release 2008 Santa Cruz mountains X2Merlot) {description}
ID Products The unique ID number of the product record page. Like other ID numbers in X2CRM, this ID exists more for the system’s benefit than for the user’s. {id}
Inventory Products The amount of products still left in inventory {inventory}
Last Activity Products The date (and time) of the last activity on the product page. This includes updating the record but also things like logging a call or adding a tag. {lastActivity}
Last Updated Products The date (and time) that the data fields on the product record page were last modified {lastUpdated}
Name Products The name of the product (e.g. Data migration (hourly rate)). {name}
Price Products The product price per unit {price}
Status Products Product status can be set to either active (meaning the product is still in stock and is for sale) or inactive (meaning the product is either out of stock and/or discontinued). Of course, since this is a dropdown menu, it can be modified in the X2Studio dropdown menu editor, located within the administration panel in X2CRM. From there you can add any kind of status setting you would like. {status}X2CRM
Type Products The nature of the product (e.g. service, ticket, or pneumatic robot arm) {type}
Updated By Products The X2CRM user who last modified the product page {updatedBy}
Account Quotes The account associated with the quote. That is, the account that the quote was sent to {accountName}
Assigned To Quotes The X2CRM user that the relevant account is assigned to. Also the user who created the quote. {assignedTo}
Contact Quotes The contact that is associated with the account that is associated with the quote. {associatedContacts}
Create Date Quotes The date (and time) that the quote was created in your X2CRM system. {createDate}
Notes Quotes Any comments or descriptions relevant to the quote {description}
Expected Close Date Quotes The date by which the deal is expected to have been finalized. {expectedCloseDate}
Expiration Date Quotes You might have certain offers which you extend to clients on a limited time basis. For these deals, you may want to have an expiration date. This is saved in the attribute field as a standard date format. {expirationDate}
ID Quotes The unique ID number of the quote. Like other ID numbers in X2CRM, this ID exists more for the system’s benefit than for the user’s. {id}
Invoice Created Quotes The date (and time) that the invoice of the accepted quote was created in X2CRM. {invoiceCreateDate}
Invoice Issued Quotes The date (and time) that the invoice of the accepted quote was sent to the client {invoiceIssuedDate}
Invoice Payed Quotes The date (and time) that the invoice was paid by the client {invoicePayedDate}
Invoice Status Quotes The current status of an invoice. Default statuses include pending, issued, paid, open, cancelled, and other. As with other dropdown menus in X2CRM, this is completely customizable in the X2Studio Dropdown Editor, found in the administration panel of X2CRM. {invoiceStatus}
Last Activity Quotes The date (and time) of the last activity on the quote page. This includes updating the record but also things like logging a call or adding a tag. {lastActivity}
Last Updated Quotes The date (and time) that the data fields on the quote record page were last modified {lastUpdated}
Lead Source Quotes The avenue through which the opportunity or account which is associated with the quote came in to your sales team {leadSource}
Locked Quotes {locked}
Name Quotes The name of the deal that the quote was made for (e.g. Campbell's cloud computing – X2CRM data migration). This can use whatever naming convention you like. {name}
Probability Quotes The odds of closing the deal with the opportunity company. This is a manually set attribute, probably by your sales team for instance. {probability}
Opportunity Stage Quotes A quote in X2CRM can have an associated opportunity. Every opportunity in X2CRM has a sales stage option. This is a dropdown menu containing the deal status status options – working, won, and lost. Of course, since this is a dropdown menu, it can be modified in the X2Studio dropdown menu editor, located within the administration panel in X2CRM. From there, you can modify the sales stages to include or exclude any option you like. {salesStage}
Status Quotes The current status of an quote. Default statuses include draft, presented, open, issued, and won. As with other dropdown menus in X2CRM, this is completely customizable in the X2Studio Dropdown Editor, found in the administration panel of X2CRM. {status}
Subtotal Quotes This is the cost amount of the deal with a client before any post-calculation price adjustments {subtotal}
Quote Template Quotes You can create quote templates in the docs module in X2CRM. The template is simply the email body that can be sent to clients informing them of their quote details {template}
Total Quotes This is the cost amount of the deal with a client after all price adjustments {total}
Updated By Quotes The X2CRM user who last updated the quote record page. {updatedBy}
Assigned To Services The X2CRM user, users, or user group who have been associated with the service record {assignedTo}
Contact Services The client contact in your X2CRM system who is associated with the service record {contactId}
Create Date Services The date (and time) that the service record page was created in your X2CRM system {createDate}
Description Services A full description of the service being done. The issue, the relevant info, and what's being done {description}
Email Services The email address of the person who submitted the service request. {email}
Escalated To Services The user who the case was escalated to {escalatedTo}
Case Services The case number of a service record is actually its ID number. Case numbers increase incrementally. {id}
Impact Services The description of the main issue comes with a default sliding scale of severity – 1. Severe, 2. Critical, 3. Moderate, and 4. Minor. Of course, since these options are selected from a dropdown menu, they can be modified in the X2Studio dropdown menu editor, located within the administration panel in X2CRM. From there you modify and the severity scale to suit your individual needs. {impact}
Last Activity Services The date (and time) of the last activity on the service page. This includes updating the record but also things like logging a call or adding a tag. {lastActivity}
Last Updated Services The date (and time) that the data fields on the service record page were last modified {lastUpdated}
Main Issue Services The description of the main issue comes with a few default options – Hardware, Software, Internet Connection, LMS, and General Request. Of course, since this is a dropdown menu, it can be modified in the X2Studio dropdown menu editor, located within the administration panel in X2CRM. From there you can add the best sorts of default issue description categories to suit your individual business needs. {mainIssue}
Next Action Services A short description of any follow up actions for the service case. {nextAction}
Case Origin Services The origin of the case is the source through which the case was reported. X2CRM comes with a few default options for this attribute –Email, Web, and Phone. Of course, since this is a dropdown menu, it can be modified in the X2Studio dropdown menu editor, located within the administration panel in X2CRM. From there you can add the best sorts of default issue description categories to suit your individual business needs. {origin}
Parent Case Services If the service being provided is a continuation or an extension of a previous service case, then the previous case is the parent case. The parent case attribute is simply the ID number of the parent case. This field auto-completes, so start typing in the name of an account and X2CRM will pop up a list of account names that match your input. The ID number of a service case is not listed by default on its page. To find it, you can either go into your services list and set "ID" as one of the sortable columns, or you can go into the X2Studio and utilize the form editor. The form editor allows you to include or exclude fields from displaying by default. A parent case's ID number is displayed by default on the sub case's detail view. {parentCase}
Resolution Services A short description of what was done to address the service case. {resolution}
Status Services The current status of the service case comes with a few default options – New, WIP, Waiting for Response, Needs More Info, Escalated, Reopened, Workaround Provided; Waiting for Fix, Program Manager Investigator, Closed – Resolved, and Closed – No Response. Of course, since this is a dropdown menu, it can be modified in the X2Studio dropdown menu editor, located within the administration panel in X2CRM. From there you can add the best sorts of default status description categories to suit your individual business needs. {status}
Sub Issue Services The sub issue of the service case comes with a few default options – Laptop, Desktop, WiFi, Loss Connection, Windows OS, MS Office, Class Access, Lost Password, Download/Upload,and Other. Of course, since this is a dropdown menu, it can be modified in the X2Studio dropdown menu editor, located within the administration panel in X2CRM. From there you can add the best sorts of default sub issue description categories to suit your individual business needs. {subIssue}
Subject Services A short description (or title, if you will) of the service case. {subject}
Updated By Services The X2CRM user who last modified a field on the service record page. {updatedBy}
Address User Profile A User's physical address {address}
Cell Phone Number User Profile A User's cell phone number {cellPhone}
Email Address User Profile A User's email address {emailAddress}
Signature User Profile A User's email signature {emailSignature}
Full Name User Profile A User's first and last name {fullName}
Office Phone Number User Profile A User's office phone number {officePhone}
Extension User Profile A User's phone extension {extension}
Home Phone Number User Profile A User's home phone number {homePhone}
Google ID User Profile A User's Google ID {googleId}
Notes User Profile A User's profile notes {notes}
Tag Line User Profile A User's profile tag line {tagLine}

TOP